Diagnosing an abend unexpected by RMF

Use this procedure when a module with the prefix ERB abnormally ends with a system completion code other than the codes listed in the table under Identifying problems.

Table 1. Diagnostic Procedure for an Abend Unexpected by RMF
Diagnostic Procedure	References
1. Look at the explanation for the abend code and any accompanying reason code. Take the recommended actions.	z/OS MVS System Codes for an explanation of the abend code
2. Obtain messages accompanying the abend. Look at their explanations and take any recommended actions.	Please visit the LookAt home page at http://www.ibm.com/systems/z/os/zos/bkserv/lookat/ for getting the fastest message explanation.
3. Obtain the SYS1.LOGREC error record, the dump, or both for the abend (softcopy).	z/OS MVS Diagnosis: Tools and Service Aids
4. Format the dump or SYS1.LOGREC record to see the SDWA and the search argument: Format an SVC dump or SYSMDUMP ABEND dump with the IPCS VERBEXIT LOGDATA subcommand. Format a SYS1.LOGREC record with EREP to obtain a detail edit report. Find the heading VARIABLE RECORDING AREA (SDWAVRA). Note the SDWAVRA keys, lengths, and contents.	z/OS MVS IPCS Commands for the VERBEXIT LOGDATA subcommand EREP User's Guide for EREP formatting z/OS MVS Diagnosis: Tools and Service Aids z/OS MVS Diagnosis: Tools and Service Aids
5. In the dump, find the offset of the failing instruction within the CSECT of the load module. If analyzing the dump at a terminal, use the IPCS WHERE subcommand to locate the failing instruction and to find its offset into the module.	z/OS MVS IPCS Commands for the WHERE subcommand
6. Use the WRITELOG system command to print the system log (keep as softcopy). The system log shows all system messages and commands issued. Make sure you print the log for the time period when the abend occurred.	z/OS MVS System Commands for the WRITELOG command
7. Develop a search argument consisting of: Program identifier: PIDS/566527404 System abend code: AB/S0xx Abend reason code: PRCS/xxxxxxxx Message identifier: MS/cccnnns CSECT: RIDS/cccccccc Load module name: RIDS/cccccccc#L Use the search argument to search problem reporting data bases. If the search finds that the problem has been reported before, request the problem fix. If not, continue with the next step.	Developing a search argument for RMF z/OS Problem Management
8. Report the problem to IBM®. Provide the following problem data: Accompanying messages The dump, SYS1.LOGREC error record, or both (softcopy) SDWAVRA keys, lengths, and contents Hardcopy (or better softcopy) of console log Search argument Offset of the failing instruction into the module Current® RMF™ options for session running RMF version and release Load module name and level CSECT name and level Name and level of the operating system with a list of program temporary fixes (PTF) applied at the time of the problem and all installation modifications, exits, and products with other than Class A service.	Reporting a problem to IBM