If the ISMF profile variable indicates that ISMF is not to recover
from abends, and ISPF is executing in normal mode, the system displays
an ISPF abend panel and places an ISPF symptom dump in the ISPF log.
See ISMF's use of the ISPF log for a description of the
ISPF log. The format of the ISPF symptom dump is shown in Figure 1.
Figure 1. ISPF
Symptom Dump in the ISPF Log14:45 ISP SUBTASK ABEND - VS 03.8 ISP 3.3.0000 ABEND CODE = 00007A PSW FF85000D 00000000
14:45 - NAME EPA 01C8DB00 ISPSUBS EPA 81C01F88 ISPTBLS EPA 000236B0
14:45 REGISTERS AT - R0 80000000 R1 8000007A R2 01CE2668 R3 00000001
14:45 ENTRY TO - R4 00000001 R5 01CC0D28 R6 00027CB8 R7 00030B10
14:45 ABEND - R8 00000000 R9 0002E7A0 R10 01C6A304 R11 01CE3B24
14:45 - R12 80036534 R13 0002E7A0 R14 8003675C 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:
- Use the module name as the keyword.
Example: If the
module name is DGTFLCDA, (this is not the case in the sample ISPF
symptom dump shown in
Figure 1 ), specify
the module keyword as:
DGTFLCDA
- See ISMF—modifier keywords.
- If you cannot determine the module name from the symptom dump:
- Continue with the procedures for determining the module name described
in Using the abend dump. If you still cannot determine
the module name, see ISMF—modifier keywords.