Client daemon stops when CICS task limit is reached

A CPMI transaction or an equivalent mirror transaction task has locked in a CICS server and cannot send data back to CICS Transaction Gateway.

Symptom

The Client daemon appears to stop responding.

Probable cause

The MAXTASKS limit of the CICS server might have been reached. This problem prevents the mirror program from returning data to the Client daemon, which appears to stop responding. The problem typically occurs when CICS has a high number of concurrent transactions.

Action

Put the mirror transaction in a TranClass that has a MAXACTIVE value that is less than the MAXTASKS value of your CICS server. All new requests to the CICS server are queued, and CICS can continue to process current requests. The value that you should specify for MAXACTIVE depends on your installation, and other tasks running in the server.


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/cclaapd.html