Initiating Services

Initiating Services

CA Datacom CICS Services is initiated by the first invocation of the DCCOCPR program. This first invocation may be accomplished in either of the following ways:

• Automatically by execution of the PLT entry when CICS is brought up, or
• Manually by issuing DBOC STARTUP or DBEC PERFORM,STARTUP while in a CICS session.

Initiation Steps

Whether initiation is automatic or manual, it consists of the following steps:

1. Loading of DBCVTPR, which contains a list of all programs and User Requirements Tables (URTs) accessible to CA Datacom CICS Services.
   1. Formatting internal control blocks for Load List, Trace entries, user tables, and MUF system blocks (MSBs).
   2. Verifying that DBCVTPR contains the core mark for the current release.
2. Loading of DBINRPR through a CICS LOAD. CICS System Definition data set (CSD) entries are provided for DBINRPR, DBSIDPR, DBDUMPR, DBSGMPR and DBXCIPR for z/OS and DBINRPR, DBSIDPR, DBDMPPR, and DBSGMPR for z/VSE.

   Note: For z/OS sites, you are required to use this method, because it conserves resources and does not require an authorized library.

3. Loading CA Datacom CICS Services modules.
   1. Verifying that all modules are from a valid release level, and verifying URTs are valid online CA Datacom/DB URTs.
   2. Activating any other CA product which is specified for support.
4. Allocating storage for the number of threads specified by the USERS= parameter of the DBCVTPR assembly.
5. Creating the hashing table for URT search requirements.
6. Connecting to the MUF specified by the DBSIDPR default module or to multiple MUFs specified by SIDNAME= and CONNECT=PLT.
7. Opening of URTs not specified as operands of the DEFER= or AUTO= parameters of the DBCVTPR assembly.
8. Generating one message per MUF to indicate whether CA Datacom CICS Services was able to connect to that MUF.
9. Writing a message to the console stating that the CA Datacom CICS Services is started, in order to identify the operator or PLT.