The occasions when CICS requests a dump

In general, CICS requests a dump when a transaction or CICS system abend occurs. The dumping environment determines whether or not a dump is taken.

CICS does not take a transaction dump if a HANDLE ABEND is active at the current logical level. This is called an implicit HANDLE ABEND and causes the suppression of transaction dumps. To make PL/I work on units, PL/I library routines can issue HANDLE ABEND. The NODUMP option on anEXECS CICS ABEND command, an internal call, or the transaction definition, prevents the taking of a transaction dump.

The following are the occasions when CICS requests a dump:
  • CICS requests a transaction dump, and perhaps a system dump, after a transaction abend occurs. There are two cases:
    • You can include the command EXEC CICS ABEND in one of your applications, causing it to abend when some condition occurs. You must specify a four-character transaction abend code on this command, and this is used as the transaction dump code. It could, for example, be ‘MYAB’.
    • CICS might cause a transaction to abend, for any of the reasons described in CICS messages. In this case, the four-character CICS transaction abend code is used as the transaction dump code. It might, for example, be ASRA.
  • A CICS system dump could be taken following a CICS system abend. In this situation, the system dump code is often equal to the abend message ID, with the leading letters “DFH” stripped off. In the case of message DFHST0001, for example, the system dump code would be “ST0001”. However, in some cases the system dump code cannot be directly related to a CICS message, either because it does not closely resemble the message, or because no message accompanies the event causing the dump to be invoked. For details of these system dump codes, see CICS messages.
  • When a transaction dump or system dump is taken, and the dump code includes the RELATED attribute on the DUMPSCOPE option, system dumps are taken of all CICS regions in the sysplex which are related to the CICS region on which this transaction dump or system dump is taken. A related CICS region is one in which the unit of work identifiers, in the form of APPC tokens, of one or more tasks match those in the CICS region that issued the dump request. Typically, these may be regions in a distributed transaction processing environment.
  • A CICS system dump can be requested from within the Node Error Program (NEP) when a terminal error is processed for a terminal with no task attached. For information about using NEPs to handle terminal errors, read message DFHZC3496 and the the programming information on NEPs in Writing a node error program.
  • A CICS system dump can also be requested from the global trap/trace exit. In this case, the system dump code is TR1003.


dfhs1c00243.html | Timestamp icon Last updated: Monday, 5 June 2017