A symptom dump is a system message, either message IEA995I or a
numberless message, which provides some basic diagnostic information
for diagnosing an abend. Often the symptom dump information can provide
enough information to diagnose a problem.
The example in
Figure 1 shows the
symptom dump for an abend
X'0C4' with reason code
X'4'.
This symptom dump shows the following information:
- Active load module ABENDER is at address X'00006FD8'.
- The failing instruction was at offset X'12' in load module
ABENDER.
- The address space identifier (ASID) for the failing task was X'000C'.
Figure 1. Example: Symptom Dump OutputIEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000004
TIME=16.44.42 SEQ=00057 CPU=0000 ASID=000C
PSW AT TIME OF ERROR 078D0000 00006FEA ILC 4 INTC 04
ACTIVE LOAD MODULE=ABENDER ADDRESS=00006FD8 OFFSET=00000012
DATA AT PSW 00006FE4 - 00105020 30381FFF 58E0D00C
GPR 0-3 FD000008 00005FF8 00000014 00FD6A40
GPR 4-7 00AEC980 00AFF030 00AC4FF8 FD000000
GPR 8-11 00AFF1B0 80AD2050 00000000 00AFF030
GPR 12-15 40006FDE 00005FB0 80FD6A90 00006FD8
END OF SYMPTOM DUMP
Symptom dumps appear in the following places:
- For SYSUDUMP and SYSABEND ABEND dumps: in message IEA995I, which
is routed to the job log.
- For a SYSMDUMP ABEND dump: in message IEA995I in the job log
and in the dump header record.
- For an SVC dump: in the dump header record.
- For any dump in a Time Sharing Option/Extensions (TSO/E) environment:
displayed on the terminal when requested by the TSO/E PROFILE command
with the WTPMSG option.
- In response to a DISPLAY DUMP,ERRDATA operator command, which
displays information from SYS1.DUMPxx data sets on direct access.
If the information in a symptom dump is enough for diagnosis, do
not provide a DD statement for a dump.
For additional information, see one of the following resources: