z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


08C

z/OS MVS System Codes
SA38-0665-00

08C

Explanation

A program issued a SCHEDULE macro to schedule a service request block (SRB). The system detected an error while processing the macro. Register 2 contains the SRB address. Register 3 contains the return address of the issuing program. A hexadecimal reason code in register 15 explains the error:
Code
Explanation
04
The address specified in field SRBASCB of the service request block (SRB) does not point to a valid address space control block (ASCB).
08
The ASCB specified in the SRB has the ASCBFAIL flag set on. The flag indicates that the address space is ending.
0C
The specified STOKEN does not represent the same address space as the ASCB specified in the SRB.
10
A feature was requested using the SCHEDULE macro but there are no online processors with the specified feature.
14
An entry point was requested using the SCHEDULE macro but an incorrect feature indicator was specified.
18
A feature was requested using the SCHEDULE macro but an non-valid feature indicator was specified.
1C
An internal error occurred during schedule processing.
20
A program issued a SCHEDULE macro to schedule an SRB with the SPTOKEN option while holding a lock higher than or equal to the DISP lock in the locking hierarchy. You cannot use the SPTOKEN option while holding a lock equal to or higher than the DISP lock.
24
DISABLED was specified on the SCHEDULE macro, but the caller was not disabled.
28
The caller was in AR ASC mode but did not specify this via the SYSSTATE macro.
2C
The SRB was not in common storage.

System action

The system abnormally ends the program that issued the SCHEDULE 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=08C,ACTION=SVCD,END

System programmer response

For reason code 10, resubmit the job on a processor complex that has the feature installed. For reason code 24, you must obtain the CPU lock before using the SCHEDULE macro. For reason code 28, specify SYSSTATE ASCENV=AR prior to issuing the SCHEDULE macro in order to ensure the macro expansion will be correct. For reason code 2C, ensure the SCHEDULE macro is being used with an SRB that is in common storage. For all other reason codes, do the following:
  1. Ask the operator to set a SLIP trap to obtain an SVC dump.
  2. In the system trace, find the system service event (SSRV) entry for abend X'08C'. Diagnostic data in this entry is as follows:
    • The return address for the issuer of the SCHEDULE macro is in the ADDR column.
    • The input SRB address is in the UNIQUE-1 column.
    • The target address space ASCB address is in the UNIQUE-2 column.
    • The STOKEN representing the target address space is in the UNIQUE-3 column.
  3. Use the address in the ADDR column of the SSRV entry to identify the module that issued the SCHEDULE 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, contact the component group associated with this module at the IBM Support Center. Provide all problem data collected and, if available, the logrec data set error record.

Source

Supervisor control

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014