AKCC
Explanation
The CICS transaction manager has abended the transaction because either of the following situations has occurred:
-
The purge threshold of its TRANCLASS has been reached and the purge action of the TRANCLASS is ABEND.
-
The PURGETHRESH limit has been lowered beyond the current size of the queue, and enough queued tasks were abended to reduce the queue to the new limit.
The purge threshold of the TRANCLASS is specified by the PURGETHRESH parameter, and the purge action is specified by the PURGEACTION parameter. See the Defining resources manual for more details of this parameter.
System action
The transaction is abended and messages DFHAC2004 and DFHAC2036 are issued. The transaction dump is suppressed for this abend code.
User response
Resubmit the transaction. The cause of the abend may be a temporary stress condition in the system.
If the problem persists, determine why the TRANCLASS purge threshold has been reached. Ensure that PURGETHRESH has been specified correctly. Also, ensure that the MAXACTIVE value of the TRANCLASS has not been set too low. Transactions attached after the MAXACTIVE limit has been reached are immediately queued subject to the PURGETHRESH limit.
If PURGETHRESH and MAXACTIVE are set correctly, look for a more general problem which has caused a decrease in the capacity of the system to execute transactions in the TRANCLASS. The decrease might, for example, be caused by a connected CICS region which processes requests for transactions in the TRANCLASS, if this connected region has slowed down.
Examine all resources (files, links, storage, and so on) used by the transactions in the TRANCLASS which is reaching the purge threshold and determine why the capacity of the system is reduced.
In addition, consider setting the purge action of the TRANCLASS to DISCARD, to avoid AKCC abends. When a temporary stress condition occurs in the system, unnecessary abends of tasks might disrupt normal processing of tasks as CICS is busy processing the abends.