DFHDU0001 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, or storage has been overwritten.
The code aaa/bbbb is a three digit hexadecimal MVS code (if applicable), followed by a four digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).
System action
An exception entry is made in the trace table.
For module DFHDUDT, a system dump is taken unless you have specifically suppressed the dumps (by a user exit program at the XDUREQ exit, in the dump table or by global system dump suppression). CICS processing continues unless you have specified in the dump table that CICS should terminate.
For module DFHDUTM, a system dump is taken. This dump cannot be suppressed. CICS processing continues.
For module DFHDUDU, a system dump cannot be taken as doing so could cause CICS to loop. CICS processing continues.
For other modules, a system dump is taken.
CICS processing continues.
Message DFHME0116, which contains the symptom string for this problem, is produced.
User response
Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.
Look up the MVS code, if there is one, in the relevant MVS codes manual which is detailed in the book list in the front of this manual.
Then look up the CICS alphanumeric code in this manual. This tells you, for example, whether the error was a program check, an abend, a runaway or a recovery percolation, and may give you some guidance concerning user response.
If module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.
If you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.
If the abend occurred in modules DFHDUDT or DFHDUTM, the dump table is not available. Therefore, any EXEC API commands relating to dump codes fail and any dumps taken are processed using default information (for example, whether to terminate CICS or not) rather than information you may have put on the dump table for specific dump codes.
If you need further assistance from IBM to resolve this problem, see IBM problem support for guidance on how to proceed.
Module
XMEOUT parameters/Message inserts
- applid
- aaa/bbbb
- X'offset'
- modname
Destination
Console