Actions taken at transaction failure

The CICS® transaction failure program (TFP) is invoked during abnormal transaction termination, unless the transaction is to be restarted, for transactions that:

The principal action of the transaction failure program is to send, if possible, an abend message to the terminal connected to the abending transaction. It also sends a message to the CSMT transient data queue.

Except for transaction failures that occur during syncpoint processing, and before sending the message to the CSMT queue, the transaction failure program links to the user-replaceable program error program (DFHPEP). DFHPEP is given control through a LINK from the CICS transaction failure program. This occurs after all program-level abend exit code has been executed by the task that abnormally terminates, but before dynamic transaction backout (if any) has been performed.

Notes:
  1. DFHPEP is not given control when the task abend is part of the processing done by CICS to avoid a system stall.
  2. DFHPEP is not given control if transaction manager detects that the abended transaction is to be restarted by DFHREST.
  3. DFHPEP processing takes place after a transaction dump has been taken. DFHPEP cannot prevent a dump being taken.
  4. DFHPEP is not given control if the transaction failure occurs during syncpoint processing.
  5. DFHPEP is not given control when the conditions causing the task to be terminated are handled by the CICS abnormal condition program (ACP). The conditions handled by ACP are some kind of attach failure; for instance, when the transaction does not exist, or when a security violation is detected.
  6. DFHPEP is not given control when a task has abended and CICS is short on storage.
  7. The CICS transaction failure program, DFHTFP, links to DFHPEP before transaction backout is performed. This means resources used by the abending transaction may not have been released. DFHPEP needs to be aware of this, and might need logic to handle resources that are still locked.
  8. Start of changeDo not use the restart function for distributed transactions whose principal facilities are APPC links. In some error situations, CICS cannot resolve the APPC conversation states, and your transaction will abend with code AZCP.End of change

The CICS-provided DFHPEP program executes no functions, but you can include in it your own code to carry out installation-level action following a transaction abend (see The CICS-supplied PEP). There is only one program error program for the whole system.

All CICS facilities are available to the DFHPEP program. You can, for example:

[[ Contents Previous Page | Next Page Index ]]