Business overview
This scenario shows you how to assess an application and redefine it so that CICS® can run it on open TCBs, and also how to verify the resulting performance improvements to demonstrate the business benefits. The scenario demonstrates how various CICS Tools Family products can help you move through this process quickly and easily.
If your organization has been using CICS Transaction Server for a while, you might have a number of existing applications that were coded and implemented before the open transaction environment (OTE) was available in CICS. You might also have existing applications that were coded and implemented when the OTE was available, but for some reason it was not appropriate to define the programs to CICS as threadsafe. Some of these applications might now be able to run on open TCBs, with improved performance, in Version 4 of CICS Transaction Server for z/OS®.
It is not always convenient to change the source code of applications after they have been implemented in your CICSplex, especially if the application has been around for a long time. However, you might find that when you assess or reassess an existing application, it can now be made to run on open TCBs without any changes to the source code, just with changes to the CICS resource definitions associated with the application.
When most or all of the processing for an application takes place on open TCBs rather than on the CICS QR TCB, the advantage for the application is that TCB switching is avoided, which could mean that the application runs faster. The advantage for the CICS system is that contention for the QR TCB is reduced, which could mean that throughput improves. If you are not familiar with the OTE threadsafe options and their effects, read through Multithreading: Reentrant, quasi-reentrant, and threadsafe programs for more information.
Version 4 of CICS Transaction Server for z/OS includes a number of threadsafe enhancements that remove earlier obstacles to processing applications on an open TCB. For example, the EXEC CICS VERIFY PASSWORD command was not threadsafe in earlier CICS releases, and so caused a switch to the QR TCB for a program that was running on an open TCB. However, in CICS TS Version 4.2 that command was made threadsafe, so processing can remain on the open TCB when a program issues the command.
If you have never examined your existing applications to see whether they could run on open TCBs, you can follow the scenario to learn the process and see how CICS tools can help you. You can usefully repeat a process like this whenever you upgrade to a new release of CICS, to reassess your applications and see what threadsafe enhancements apply to them.
If you have examined your existing applications in the past, but some of them still do not run on open TCBs, you can follow the scenario to optimize your processes for verifying that a program’s logic is threadsafe, and for assessing or reassessing the CICS commands in programs to see whether they are threadsafe in a new release of CICS. The scenario highlights some specific threadsafe enhancements in CICS TS Version 4.2 that could be relevant for your own applications. You can also learn from the scenario how to analyze and demonstrate the performance improvements that you achieve by running your applications on open TCBs.