Use this procedure when a module with the prefix ERB abnormally ends with the system completion code X'0D5'. RMF™ detected an ASID that was not valid.
| Diagnostic Procedure | References |
|---|---|
| 1. Obtain the SYS1.LOGREC error record and format it with EREP to obtain a detail edit report. | EREP User's Guide for EREP formatting
z/OS MVS Diagnosis: Tools and Service Aids to read the SYS1.LOGREC record z/OS MVS Diagnosis: Tools and Service Aids |
| 2. Check the SYS1.LOGREC error record to determine if the
abend occurred in module ERBMFPVS.
If the abend did not occur in module ERBMFPVS, continue with step 4. Otherwise proceed with the next step. |
z/OS MVS Diagnosis: Tools and Service Aids to read the SYS1.LOGREC record |
| 3. Obtain the SVC dump for the abend. | z/OS Problem Management |
| 4. Format the dump with the IPCS VERBEXIT LOGDATA subcommand
to see the system diagnostic work area (SDWA) and the search argument.
In the dump, find the offset of the failing instruction into the 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 VERBEXIT LOGDATA and WHERE subcommands |
5. Determine if the ASID is not valid. Either:
Correct the problem and reinitialize RMF. If you cannot determine why the ASID is not valid, continue with the next step. |
|
6. Develop a search argument consisting of:
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 |
7. Report the problem to IBM®.
Provide the following problem data:
|
Reporting a problem to IBM |