AD3J


    Explanation
      A commit request to DB2, issued during the second phase of syncpoint, failed. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

    

    System action
      The task is abnormally terminated with a CICS transaction dump. CICS maintains a record that the UOW committed pending a future resynchronization request with DB2.

    

    User response
      Examine the exception trace in the dump to determine why the commit request failed. The CSUB control block is output as part of the exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The commit request contains eyecatcher "COMM" and is followed by the DB2 FRB response and reason codes.

    

    Module
DFHD2D2

Applicable releases in Version 6
  
  
    
      beta

      6.3

      6.2

      6.1