Program check

For a program check, the following processing takes place in the following order:
  1. If this program check occurred while DFHSRP was processing a previous program check, CICS® is terminated with message DFHSR0602 and a system dump. Otherwise, DFHSRP might get caught in a recursive loop.
  2. If this program check occurred while DFHSRP was processing an operating system abend, CICS is terminated with message DFHSR0615 and a system dump. This action traps program checks in global user exit XSRAB.
  3. If DFHEIP or DFHEIG hired gun checking caused the program check, create an abend record for abend code AEYD and return to DFHSR1.
  4. If the program check was an 0C4 protection exception, DFHSRP diagnoses the 0C4 abend further to establish whether it was caused by an attempt to access or overwrite CICS-managed protected storage. Such storage is as follows:
    • The fetch-protected dummy CSA block
    • CDSA
    • RDSA
    • UDSA
    • ECDSA
    • ERDSA
    • ETDSA
    • EUDSA
    • GCDSA
    • GUDSA

    An 0C4 abend on the CDSA, ECDSA, ETDSA, or GCDSA can occur only if storage protection is active. An 0C4 abend on the UDSA, EUDSA, or GUDSA can occur only if transaction isolation is active.

    This diagnosis is accomplished by disassembling the failing instruction, and examining the instruction operands in conjunction with the execution conditions at the time of the 0C4 abend (such as execution key). If the dummy CSA caused the 0C4 abend (that is, an attempt was made to access the CSA or TCA, or an illegal macro call was issued), message DFHSR0618 is issued. If a DSA caused the 0C4 abend, message DFHSR0622 is issued.

  5. If the SRT=NO system initialization parameter was specified, you have disabled recovery, and CICS terminates with message DFHSR0603 and a system dump.
  6. If a CICS system task was in control at the time of the program check, indicated by a non-numeric transaction number, CICS is terminated with message DFHSR0601 and a system dump.
  7. Some special processing is performed that applies only to PL/I programs.
  8. DFHSRLI is called to determine the following information:
    • The program in which the program check occurred
    • The offset in that program
    • The execution key.
  9. The results of the diagnosis (program, offset, execution key, and, for an 0C4 abend, any affected DSA) are output in an exception trace.
  10. Message DFHAP0001 or DFHSR0001 is issued, depending on the execution key at the time of the program check, and a system dump is taken. If the program was running in user key, message DFHSR0001 is issued; otherwise, message DFHAP0001 is issued. (See also System dump suppression.)
  11. Finally, DFHSRP creates an abend record and returns to DFHSR1.


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