Using the ISMF symptom dump

If an abend occurs while executing ISMF, and logging is active, the system places an ISMF symptom dump (mini dump) in the ISPF log. If ISMF is able to capture the name of the failing module, it appears in the symptom dump. The format of the dump is shown in Figure 1.

Figure 1. ISMF—Symptom Dump in the ISPF Log

14:32   *****  ISMF ERROR  ***** - APPLICATION(DGTA - LIBRARY); FUNCTION(DEFINE)
14:32                            - WORK.SCDS
14:32                            - ISMF 1.1.0   FMID JDZ1110   SYSTEM ABEND CODE 0C1
14:32                            - XXXXXX NAME DGTFLCDA   EPA 8260D5F8   PSW 078D2000 8000002A
14:32                            - DATA AT PSW 00000022 - 1000822E 3488078D 20008262 631E0000
14:32                            - R0  00000000   R1  0270A554   R2  026E6618   R3  000535E0
14:32                            - R4  00041698   R5  00000000   R6  000535E0   R7  00056800
14:32                            - R8  0270A56C   R9  026F98E7   R10 026E813C   R11 0270A4CC
14:32                            - R12 8260D5F8   R13 0270A4CC   R14 8260D750   R15 00000000

The name field in the symptom dump identifies the name of the failing module if it is available.

If you can determine the module name from the symptom dump:
1. Use the module name as the module keyword.
  Example: If the module name is DGTFLCDA, specify the module keyword as shown:
```
DGTFLCDA
```
2. See ISMF—modifier keywords.
If you cannot determine the module name from the symptom dump:
1. Continue with the procedures for determining the module name described in Using the abend dump.
2. If you still cannot determine the module name, see ISMF—modifier keywords.