DFHAP0001 applid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.

Explanation

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in CICS code.

Alternatively:

  • Unexpected data has been input,

  • Storage has been overwritten, or

  • There has been a program check within a user program.

The code aaa is, if applicable, a 3-digit hexadecimal MVS system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The 4-digit code bbbb, which follows aaa, is a user abend code produced either by CICS or by another product on the user's system.

If X'offset' contains the value X'FFFF', then module modname was in control at the time of the abend, but the program status word (PSW) was not addressing this module.

System action

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

Either this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.

Or CICS will continue unless you have specified in the dump table that CICS should terminate. Message DFHME0116, which contains the symptom string for this problem, is produced.

User response

Notify the system programmer.

Look up the MVS code aaa, if there is one, in the relevant MVS codes manual which is detailed in the book list in the front of this manual.

If the modname insert contains the value ????, then CICS was unable to determine which module has abnormally terminated. In this case, examine the system dump to determine which area of code has caused the program check.

The user should examine other messages to determine what the module which issued this message was doing at the time the abend occurred. From these messages they can deduce which product has produced the abend code bbbb. If bbbb is identified as a CICS code, it may be either alphameric or numeric.

  • If the CICS code is alphameric (for example AKEA) then it is a CICS transaction abend code.

  • If the CICS code is numeric (for example 1310), it refers to a CICS message (DFHTS1310 in our example).

If the user abend code is from another product (for example, IMS), refer to the appropriate messages and codes manual to determine the cause of the abend.

The entries in the appropriate manuals will give the user guidance regarding the nature of the error, and may also give some guidance concerning the appropriate user response.

Note:

The program check may have occurred in a user program. If this is the case, the program check is usually followed by an ASRA or an ASRB transaction abend and a transaction dump.

If you want to suppress system dumps that precede ASRA and ASRB abends, you must specify this on an entry in the dump table, using either CEMT or an EXEC CICS command. Further guidance on suppressing system dumps can be found in the System definition reference.

You may need further assistance from IBM to resolve this problem. See Working with IBM to solve your problem for guidance on how to proceed.

Module

DFHABAB, DFHAFMT, DFHAPDM, DFHAPDN, DFHAPEX, DFHAPIQ, DFHAPJC, DFHAPNT, DFHAPSM, DFHAPST, DFHAPSI, DFHAPXM, DFHAPXME, DFHDKMR, DFHEDFE, DFHEISR, DFHICXM, DFHMRXM, DFHSAIQ, DFHSIPLT, DFHSRP, DFHSTDT, DFHSTFC, DFHSTLK, DFHSTLS, DFHSTSZ, DFHSTTD, DFHSTTM, DFHSTTR, DFHSTTS, DFHSUEX, DFHTDXM, DFHTMP, DFHTSUT, DFH62XM

XMEOUT parameters/Message inserts

  1. applid
  2. aaa/bbbb
  3. X'offset'
  4. modname

Destination

Console