(z/OS only) Each occurrence of a DBCSID macro defines one connection of CA Datacom CICS Services to a given CA Datacom/DB 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 CA Datacom/DB URT Start macro (DBURSTR). For information on the DBURSTR macro, see the CA Datacom/DB Database and System Administration Guide. For more information about global URTs, see Coding the URT Macros.
Restriction
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 not cause a connection to more than one MUF.
Note: 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/DB DBSYSID macro. For information about DBSYSID, see the CA Datacom/DB Database and System Administration Guide.
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/DB MUFs. If no DBCSID macro is supplied, CA Datacom CICS Services loads 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 must be used for CA Datacom system tables. The system tables include database 1000, the Datadictionary databases (DataDict and DDD), the CA Dataquery database, the FAT-TAT database, and all SQL requests. Therefore:
Note: Actual CA Dataquery (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/DB MUF that must be at CA Datacom/DB Version 12.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/DB 14.0 and 12.0, the 14.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 Services selects the given MUF based upon the current URT selection criteria. Only a global URT with a SIDNAME= specified in the CA Datacom/DB DBURSTR 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.
Note: To support multiple MUFs, CA Datacom CICS Services also supports the use of the DBIDUSER= and DBIDMUF= parameters of the CA Datacom/DB global URT Entry macro (DBURTBL). See the information about DBURTBL in the CA Datacom/DB Database and System Administration Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|