ADCD
Explanation
This abend is issued when a deadlock has been detected by IMS and this transaction has been selected for abnormal termination.
This abend can occur when a transaction is accessing IMS resources via DBCTL or via a remote DLI request to a remote CICS region. The remote CICS region can be accessing IMS via DBCTL, or if it is a CICS 4.1 region or earlier, accessing IMS via local DLI.
System action
Access to IMS resources via DBCTL is withdrawn for this transaction. Further attempts to access IMS will result in an AEY9 abend.
CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.
User response
If ADCD abends occur infrequently in your system, no action is required although you may like to consider setting your system up in such a way that, after an ADCD abend is issued, the transaction is automatically restarted. See the Administering recovery and restart for further information.
If ADCD abends are occurring frequently in your system, you may need to review the design of your applications. Some general techniques for deadlock avoidance are described in the Administering recovery and restart.