The application in Version 3 of CICS TS

In CICS® TS 3.2, the CICS regions in which the application runs are connected by MRO connections. One of the programs in the application is defined as threadsafe, so some processing takes place on an open TCB. However, several elements in the application are not threadsafe, so most processing takes place on the QR TCB.

Figure 1. The application in Version 3.2 of CICS TS
Three CICS regions, a TOR, an AOR, and a DOR, are all at CICS TS 3.2. The TOR and the AOR are connected by an MRO connection, and the AOR and the DOR are connected by an MRO connection. The DOR is connected to DB2. The application that runs in the CICS regions is described in the text following the figure.
Figure 1 shows the processing for the application, and the key features that are or are not threadsafe in CICS TS 3.2:
  1. The user starts transaction TRN1 in the TOR. The transaction is dynamically routed over the MRO connection to the AOR, where it runs as TRN1.
  2. Transaction TRN1 in the AOR starts program STPROG1. The program is defined as CONCURRENCY(QUASIRENT), so CICS runs it on the QR TCB.
  3. STPROG1 issues the EXEC CICS VERIFY PASSWORD command to verify the user’s authority to access the restricted records in DB2®. This command is not threadsafe in CICS TS 3.2.
  4. STPROG1 function ships an EXEC CICS WRITEQ TS command to write an audit record to a temporary storage queue in the DOR. This command is not threadsafe when function shipped to a remote CICS region in CICS TS 3.2.
  5. In the DOR, the mirror transaction CSMI uses the CICS-supplied mirror program DFHMIRS to execute the function-shipped EXEC CICS WRITEQ TS command. DFHMIRS is not threadsafe in CICS TS 3.2.
  6. When the password check has completed successfully and the audit record has been written, STPROG1 issues an EXEC CICS LINK command to run a program in the DOR to retrieve the record. This command is not threadsafe in CICS TS 3.2.
  7. In the DOR, the mirror transaction CSMI uses the CICS-supplied mirror program DFHMIRS to run program STPROG2. DFHMIRS is not threadsafe in CICS TS 3.2.
  8. STPROG2 issues an EXEC SQL SELECT... INTO... command to retrieve the requested records from DB2. Because STPROG2 is defined as CONCURRENCY(THREADSAFE) and is accessing a resource manager, for which CICS uses an open API TRUE, processing moves to an open TCB at this point. Processing can continue on the open TCB until STPROG2 completes. However, this is the only processing for the application that takes place on an open TCB. The remaining processing has all been on the QR TCB.


ins_initialmi.html | Timestamp icon Last updated: Sunday, 4 June 2017