- Record the abend code and messages
Find the abend
code from the heading of the dump and record any pertinent messages.
- Is this a CICS® or a USER abend code?
- If this is a USER abend code, tell the appropriate person.
- For a CICS abend code, continue with 3.
- Look up the abend code
If you need further
advice, continue with 4.
- Is this an AICA abend?
If it is, read Dealing with loops. If not, continue with 5.
- Is this an ASRA abend?
If it is, go
to step 7. If not, continue with 6.
- Is this an ASRD abend?
If it is,
continue with 7. If not, go to 14.
- Record the program areas from the dump.
Find the program names from the Module Index at the end of the formatted dump.
For each program, record the program name, the beginning address, and end
address.
- Record the address of the next instruction from the PSW,
or the offset established by CICS.
- Did the program check occur in one of the program areas
listed above?
If it did, continue with 10. If not,
go to 14.
- Record what type of program check occurred.
You will need to record the
Program Interrupt Code (PIC).
- Find the last statement executed.
See Locating the last command or statement.
- Was the PIC one of the arithmetic interrupts (7,8,9,A,B,C,D,E,F)?
If it was, find the contents of the operands of the last instruction
(see Locating program data), and go to step 15. If not,
continue with 13
- Was the PIC a protection exception?
If it was, read Dealing with protection exceptions.
Go to 15.
- Find the last statement executed
See Locating the last command or statement.
- Analyze the problem and the data gathered.
For most problems you should now have enough information to solve
the problem. If you still cannot find the source, recheck the following:
- Parameters to or from other programs or systems.
- Any needed resource that may not be available.
- The formatted trace, for any unexplained flow.
- The running environment, for any changes in it.