The CICS-supplied PEP

The CICS-supplied PEP performs no processing. Its only effect, when CICS® links to it, is to avoid the DFHAC2259 message that would otherwise be issued.

All CICS facilities are available to the DFHPEP program. You can, for example:
  • Send messages to the terminal
  • Send messages to the master terminal
  • Record information or statistics about the abend
  • Request the disabling of the transaction entry associated with this task
However, the following processing applies to the DFHPEP program:
  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. Do 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.


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