Your own PEP

During the early phases of operation with CICS®, you can put abending transactions into a disabled status while the cause of the abend is being investigated and corrected.

Where a program has to handle this process, or where associated programs or transactions must also be disabled, you might decide to incorporate these actions in your own PEP.

The program error program is a command-level program that can be written in any of the languages that CICS supports. The CICS abnormal condition program passes a communications area (COMMAREA) to the program error program that contains information about the abend.

Functions you might consider including in a program error program include:
  • Disabling a particular transaction identifier (to prevent other users using it) pending diagnostic and corrective actions. You can avoid manual intervention and the risk of several more abends in quick succession.
  • Disabling other transactions or programs that depend on the satisfactory operation of a particular program.
  • Keeping a count of errors by facility type (transaction or file).
  • Abending CICS after a transaction abend. Conditions for this might be:
    • If the abended transaction was working with a critical file
    • If the abended transaction was critical to system operation
    • If the abend was such that continued use of the application would be pointless, or could endanger data integrity
    • If the error count for a particular facility type (transaction or file) reached a predetermined level.
  • Disabling the facility, which keeps the system running longer than if you cause CICS to abend.

If a task terminates abnormally, code in a program-level exit or the PEP can flag the appropriate transaction code entry in the installed transaction definition as disabled. CICS rejects any further attempt by terminals or programs to use that transaction code until it is enabled again. Consequently, the effect of program checks can be minimized, so that every use of the offending transaction code does not result in a program check. Only the first program check is processed. If the PEP indicates that the installed transaction definition is to be disabled, CICS does not accept subsequent uses of that transaction code.

When you have corrected the error, you can re-enable the relevant installed transaction definition to allow terminals to use it. You can also disable transaction identifiers when transactions are not to be accepted for application-dependent reasons, and can enable them again later.

If logic within DFHPEP determines that it is unsafe to continue CICS execution, you can force a CICS abend by issuing an operating system ABEND macro. If DFHPEP abends (transaction abend), CICS produces message DFHAC2263.



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