The first step of debugging just about any program check is determining architecturally "why". Even the symptom dump (message IEA995I) will fairly often provide enough information.
The abend code and abend reason code, PSW at time of error, the instruction text, and the GRs/ARs could let you identify such as "The abend was 0C4-4 so resulted from a program interrupt 4 which according to the instruction text came about from a store instruction using register 2 as the operand, so either the target address is store-protected (such as an address of 0) or is not valid in the PSW key at time of error". Finding out how the program managed to get that operand value into register 2 is where the "real" debugging typically starts which often requires access to program listings, as well as a dump. Aside from the presence of a symptom dump in z/OS, the platform doesn't affect the process too much -- you need information about the program and about the time of error. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
