AKCS

Explanation
      A deadlock timeout condition has been detected. This condition may occur within a transaction that specifies DTIMOUT to be nonzero on its installed transaction definition. Deadlock timeout occurs when a transaction has been waiting or has been suspended for longer than the time specified in DTIMOUT.

      The abend may be driven by a variety of internal CICS events, for example:

                A short on storage condition

        
          A temporary storage shortage

        
          ENQUEUE

        
          An ALLOCATE request

        
          A RETRIEVE WAIT request.

        
      The abend can also occur if CICS stops running for a time, for example while an sdump is taken. This is because deadlock timeout is based on total elapsed time, and not just the time CICS is executing.

              Analysis: The transaction receiving the AKCS abend must have been suspended or must be waiting for a reason such as a short on storage, enqueued on a lock, a short on temporary storage, a suspend after RETRIEVE WAIT, a suspend after ALLOCATE, or an implicit ALLOCATE within function shipping or terminal sharing support. If none of these apply, the trace might reveal some event that has caused CICS to stop running for a time.

    
System action
      The transaction is abnormally terminated. A dump is not provided unless the dump table entry for transaction dump code AKCS indicates that one should be taken.

    
User response
      The transaction should be reexecuted, and the situation causing the SUSPEND to occur may clear itself.

      The AKCS abend is to be expected occasionally, unless DTIMOUT is set to zero. No special action is necessary.

    
Module
DFHXCP