Specifying DBCSID Macros
(z/OS only) Each occurrence of a DBCSID macro defines one connection of dcs to a given ddb Multi-User Facility (MUF). This association is established by giving the DBCSID macro parameter SIDNAME= the same load module name as specified in a global User Requirements Table (URT) by the SIDNAME= parameter in the ddb URT Start macro (DBURSTR). For information on the DBURSTR macro, see the CA Datacom® Core documentation. For more information about global URTs, see Coding the URT Macros.
(z/OS only)Each occurrence of a DBCSID macro defines one connection of
CA Datacom® CICS Servicesto a given
CA Datacom®/DBMulti-User Facility (MUF). This association is established by giving the DBCSID macro parameter SIDNAME= the same load module name as specified in a global User Requirements Table (URT) by the SIDNAME= parameter in the
CA Datacom®/DBURT Start macro (DBURSTR). For information on the DBURSTR macro, see the CA Datacom® Core documentation. For more information about global URTs, see Coding the URT Macros.
In general, batch global URTs (multiple MUF interface URTs) have many DBURSTR SIDNAME= parameters, while online global URTs are restricted to one and only one DBURSTR SIDNAME= parameter per URT.
Global URT SIDNAME= parameters can only be defined in a DBURSTR macro
once per URT.A single URT
may notcause a connection to more than one MUF.
Although this is a restriction, it is not a limitation, because online environments use more than one URT.
The sub-identifier ID (SID) load module name, that can now be specified in the DBCSID macro parameter SIDNAME=, was known in prior releases by a single load module named DBSIDPR, assembled by the
CA Datacom®/DBDBSYSID macro. For information about DBSYSID, see the CA Datacom® Core documentation.
Place the DBCSID macros immediately after the DBCVTPR macro with its DBCVTPR parameters (see Specifying Generation Options (DBCVTPR)). In
CA Datacom® CICS Services, you can specify a maximum of 99 DBCSID macros in a single assembly of the DBCVTPR macro, but we recommend you specify only the minimum number of DBCSID macros required. A DBCSID macro is only required if connecting to two or more
CA Datacom®/DBMUFs. If no DBCSID macro is supplied,
CA Datacom® CICS Servicesloads DBSIDPR as the SID module, as in previous releases. Therefore, if you are only connecting to one MUF, no DBCSID macro is needed. However, if you are connecting to two MUFs, two DBCSID macros are required, while three DBCSID macros are required to connect to three MUFs, and so on.
The first DBCSID macro defines the connection to the default MUF. This is important because, except for CA Ideal and CA Datacom VSAM Transparency, the default MUF
mustbe used for
CA Datacom®system tables. The system tables include database 1000, the
CA Datacom® Datadictionary™databases (DataDict and DDD), the
CA Dataquery™ for CA Datacom®database, the FAT-TAT database, and all SQL requests. Therefore:
- All of the followingmustrun on the default MUF identified in the first DBCSID macro:
- CA Datacom®/DBDatadictionary Online (DDOL)
- CA Dataquery™ for CA Datacom®(DQRY)
- CA Datacom DL1 Transparency
- CA Datacom TOTAL Transparency
- All non-converted (non-global) URTs use the default MUF connection.
- AllCA Dataquery™ for CA Datacom®security andCA Datacom® Datadictionary™security is done in the default MUF.ActualCA Dataquery™ for CA Datacom®(DQRY) DQL user data requests can go to other MUFs, based upon URT specifications.
Any SQL executed in CICS must only go against the default MUF.
The use of the multiple MUFs feature requires a default
CA Datacom®/DBMUF that must be at
CA Datacom®/DBVersion 14.0 or later. The MUF with the most recent version must be listed first in the DFHRPL (the load library concatenation for loading modules in CICS). For example, if you are connecting to both
CA Datacom®/DB15.0 and 14.0, the 15.0 libraries must be first in the concatenation. For custom libraries, the default MUF custom libraries must be first in the concatenation.
Only the URTs that need new functions, such as DBID switching or going against a DBCSID MUF that is not the default, need to be reassembled with global URT macros.
CA Datacom® CICS Servicesselects the given MUF based upon the current URT selection criteria. Only a global URT with a SIDNAME= specified in the
CA Datacom®/DBDBURSTR macro can support requests going to the non-default DBCSID MUF. Because of security issues, make certain that you have done careful site planning when deciding what your site requires.
To support multiple MUFs,
CA Datacom® CICS Servicesalso supports the use of the DBIDUSER= and DBIDMUF= parameters of the
CA Datacom®/DBglobal URT Entry macro (DBURTBL). See the information about DBURTBL in the CA Datacom® Core documentation.
DBCSID Macro Parameters
Following are the DBCSID macro parameters you can specify.
CA Datacom® CICS Servicesis to connect to a given MUF. The three choices are as follows:
- PLTSpecifies that a connection to a given MUF be attempted whenCA Datacom® CICS Servicesstarts up.
- AUTOSpecifies that a connection to a given MUF be attempted when the first URT that needs this connection opens.
- DEFERSpecifies that a connection to a given MUF should be delayed until a CONNECT is manually issued for that given MUF.
- Valid Entries:PLT, AUTO, DEFER
- Default Value:(No default)
Optional) Use EOJ_OK=DISCONNECT or IMMEDIATE if you want to participate with CA Datacom Multi-User in support of a request to EOJ MUF.
CA Datacom® CICS Servicesis notified that a MUF EOJ has been requested when EOJ_OK is specified with DISCONNECT or IMMEDIATE and there is activity in the CICS region. Depending on the value specified,
CA Datacom® CICS Servicesissues and performs an orderly DISCONNECT (EOJ_OK=DISCONNECT) or an IMMEDIATE disconnect (EOJ_OK=IMMEDIATE) of the Multi-User. For more information, see Connecting and Disconnecting MUFs.
If you specify other than EOJ_OK=NO, evaluate the
CA Datacom®/DBstartup parameter X_EOJ_OK_S_DELAY for setting the correct time interval for your environment. The
CA Datacom®/DBMUF uses this value to wait before severing the connection with
CA Datacom® CICS Serviceswhen there is no activity. Releases of
CA Datacom®/DBearlier than Version 14.0 do not support this feature.
- Valid EntriesDISCONNECT, IMMEDIATE, or NO
- Default Value:NO
The value specified in the EOJ_OK= parameter of the DBCVTPR becomes the default for any DBCSID macros that are coded with the DBCVTPR macro. When EOJ_OK= is specified in the DBCSID macro, it overrides the default taken or specified in the DBCVTPR macro.
(Required)Specifies the sub-identifier ID (SID) load module name. This load module name is the output from a DBSYSID assembly that contains the needed information (SVC, SUBID, and so on) about the given MUF. For information about DBSYSID and the DBURSTR macro SIDNAME= parameter, see the CA Datacom® Core documentation..
- Valid Entries:Valid load module name (output from a DBSYSID assembly)
- Default Value:(No default)
(Required)Specifies the number of threads or MUF tasks requested by this CICS from the MUF to which it is connected, based upon the sub-identifier ID (SID) load module name specified in the SIDNAME= parameter.
The USERS= parameter of the first DBCSID macro overrides the USERS= parameter specified in the DBCVTPR macro. For more information, see USERS=.
- Valid Entries:2 -- 255
- Default Value:No default
Sample Assembly JCL for DBCVTPR with DBCSID Macros (z/OS)
The following example shows sample z/OS JCL for assembling and linking DBCVTPR that includes DBCSID macros for defining MUF connections. Modify the JCL as required to meet your site standards.
Linking the DBCVTPR module with RENT results in an ABEND during startup if CICS is set up with RDSA (read-only memory) and this storage option is supported by the hardware.
//DBCVTPR JOB (acct info),'job desc',CLASS=X,MSGCLASS=X //PROCLIB DD DSN=SYS1.PROCLIB,DISP=SHR //******************************************************************* //* * //* ASSEMBLE AND LINKEDIT -- DBCVTPR CICS SERVICES OPTIONS * //* * //******************************************************************* //STEP1 EXEC HLASMCL, // PARM.C='OBJECT,NODECK', // PARM.L='MAP,LET,LIST' //C.SYSLIB DD DSN=SYS1.MACLIB,DISP=SHR // DD DSN=CAI.THLQ.CAB1MAC,DISP=SHR // DD DSN=CAI.DHLQ.CABDMAC,DISP=SHR // DD DSN=CICS.SDFHMAC,DISP=SHR //C.SYSPRINT DD SYSOUT=* //C.SYSIN DD * DBCVTPR USERS=6,MULTUSE=YES,MSTOPR=***, X PREFIX=DBURT,MAXURTS=500,SCROLL=MANUAL, X TWOPHASE=NO,AUTO=(001,002,003,010) DBCSID SIDNAME=DBSIDPR,USERS=3,CONNECT=PLT, X EOJ_OK=DISCONNECT DBCSID SIDNAME=PRODMU1,USERS=3,CONNECT=AUTO DBCSID SIDNAME=PRODMUF,USERS=4,CONNECT=DEFER END //L.SYSLMOD DD DSN=CAI.CHLQ.CUSLIB,DISP=SHR //L.SYSPRINT DD SYSOUT=* //L.SYSIN DD * NAME DBCVTPR(R) /* //
- The previous PROC invokes the ASMA90 program.
- With previous reference to SYSLMOD, see the product installation procedures to determine the correct custom load library (CUSLIB) data set to contain DBCVTPR. This data set must also be included in your CICS DFHRPL library concatenation ahead of theCA Datacom® CICS Servicestarget load library.
- When placing the DBCVTPR, carefully place theCA Datacom®/DBcustom load libraries containing the DBCSID DBSIDPR=named modules so that the first of those in the concatenation is the default MUF as specified by the first DBCSID macro.