A CA Datacom CICS transaction is having performance problems.
A CICS trace shows lots of WAIT EXTERNAL commands coming from program DCCTRPR.
Is this a problem?
What can be done to improve CA Datacom CICS Services performance?
z/OS and z/VSE operating systems
A WAIT EXTERNAL in CICS is normal for a CA Datacom CICS program.
It means the program has sent a request to the Datacom MUF and is waiting for a response.
There is a performance enhancement which replaces CICS WAIT EXTERNAL with MVS WAIT/POST API for programs running under OPEN TCBs, it was introduced in PTF RO92668 for DBC15.0 or RO88191 for DBC 14.0.
It is best to also apply the latest PTF which delivers performance enhancements and all their pre-reqs:
RO97469 for DBC 15.1
RO97508 for DBC 15.0
RO97640 for DBC 14.0
For best performance code DBCVTPR with the following options, then assemble and link DBCVTPR and recycle CICS :
The other thing to check is if the application is defined as threadsafe, the CICS program definition should have option CONCURRENCY(THREADSAFE).
For CA Ideal, it is threadsafe only if using load modules. If using VLS object it cannot run threadsafe.
The only programs that need to be defined with CONCURRENCY(THREADSAFE) are the VPE modules that interface with CICS, the VPEHJEnn and VPEHJNnn programs.