AD3K   

Explanation

An abort 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 backed out pending a future resynchronization request with DB2.

User response

Examine the exception trace in the dump to determine why the abort 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 abort request contains eyecatcher "ABRT" and is followed by the DB2 FRB response and reason codes.

Module

DFHD2D2


AD3K.html | Timestamp icon Last updated: Sunday, 4 June 2017