Explanation
A program issued the SRBSTAT macro, but this program
either:
- Is in an environment that is not valid
- Specified parameters that are not valid
A hexadecimal reason code in register 15 explains the error:
- Code
- Explanation
- 00
- The program holds a lock.
- 04
- The current functional recovery routine (FRR) stack is not the
normal FRR stack.
- 08
- The program has super bits set.
- 0C
- The program is not in service request block (SRB) mode.
- 10
- The program is disabled.
- 14
- The first level of the recovery termination manager (RTM1), a
service invoked by RTM1, or an FRR used the RESTORE parameter on the
SRBSTAT macro.
- 18
- The PCLINK stack header was not zero on entry to processing for
the RESTORE parameter of the macro.
- 1C
- The program specified RESTORE or MODIFY on the macro, and the
status save area does not contain valid status.
- 20
- Processing for the RESTORE parameter of the macro scheduled an
SRB to obtain correct processor affinity, but the SRB was unable to
run.
- 24
- The program specified MODIFY on the macro, but register 0 contains
a MODIFY identifier code that is not valid.
System action
The system abnormally ends the program that issued
the SRBSTAT macro. The system may write a logrec data set error record.
Operator response
If the system programmer asks for an SVC dump,
set the following SLIP trap:
SLIP SET,COMP=05E,ACTION=SVCD,END
System programmer response
Use the address in register 14 at
the time of error to identify the module that issued the SRBSTAT macro.
- For an installation-provided module, continue diagnosis with the
module.
- For an IBM® module, search
problem reporting data bases for a fix for the problem. If no fix
exists, ask the operator to set a SLIP trap to obtain an SVC dump.
Contact the component group associated with this module at the IBM Support Center. Provide the
SVC dump and, if available, the logrec data set error record.
Source