The application after migration to Version 4.2 of CICS TS
All the CICS® regions have now been migrated to CICS TS 4.2, and some of the threadsafe enhancements in that release have removed obstacles to running the application on an open TCB. However, no changes have yet been made to the resource definitions relating to the application, so the application spends no more time running on an open TCB than it did in CICS TS 3.2.
Figure 1. The application after migration
to Version 4.2 of CICS TS

Figure 1 shows the features
that have changed after migration to Version 4.2:
- The EXEC CICS VERIFY PASSWORD command in program STPROG1 is now threadsafe. However, STPROG1 is still defined as CONCURRENCY(QUASIRENT), so processing for this program still takes place on the QR TCB. Analyzing this program would reveal whether its program logic is threadsafe. If that is the case, the program could be redefined so that CICS runs it on an open TCB, and the EXEC CICS VERIFY PASSWORD will not now cause a TCB switch back to the QR TCB.
- The EXEC CICS WRITEQ TS command is now threadsafe when function shipped to a remote CICS region. The EXEC CICS LINK command to link to program STPROG2 in the DOR, and the CICS-supplied mirror program DFHMIRS in the DOR, are also now threadsafe. However, all these items are only threadsafe over an IPIC connection, and the CICS regions are still connected by MRO connections. Replacing the MRO connection between the AOR and the DOR with an IPIC connection would enable CICS to carry out this processing on an open TCB.
With the current set of CICS resource definitions, processing for this application can still only move to an open TCB at the point where STPROG2 accesses DB2®, as in CICS TS 3.2. However, because of the changes in CICS TS 4.2, the application now only needs some changes to the resource definitions to make most of the processing take place on an open TCB.