Throughput Issues In CICS TOR and AOR With Top Secret
Article ID: 201567
Updated On:
Products
Issue/Introduction
CICS 5.3. The TOR and AOR regions had to be recycled several times in the past few days due to a buildup of transactions in one of the CICS transaction classes in the TOR. Most of these transactions use the EXEC CICS SIGNON and SIGNOFF transactions and run in the TOR; these then go to the AOR. An analysis of one of those programs shows 18% CPU time spent in module CAS9C70. The last IPL was months ago and part of that involved installing CA Common Services 15.0. It's possible that the signon programs are being delayed and this causes an issue with getting work to the AOR.
The following fixes are applied: SO08150, SO07478, SO07479, SO05586 and SO05587.
OPTIONS(38) is not set.
Environment
Release : 16.0
Component : CA Top Secret for z/OS
Resolution
The TOR dump shows a number of tasks where EIBFN is 0404 (SEND) where the last command issued message:
TSS7199A Enter Password To Unlock; CESF Or Clearkey To Signoff
Because PCLOCK=NO is currently on facility CICSPROD, locktime is conversational and unless the user responds to the TSS7199A message, the task is in a wait state.
It is recommend to use PCLOCK=YES to make locktime psuedo-conversational. To do this, set the following in the Top Secret parameter file:
FACILITY(CICSPROD=PCLOCK=YES)
The CICS region needs to be recycled and ensure the transaction TSLK and associated program are defined.
Feedback
