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


6C7

z/OS MVS System Codes
SA38-0665-00

6C7

Explanation

During processing of a REFPAT macro, the system found a non-environmental error. The macro processing failed. Register 15 contains a hexadecimal reason code.
Code
Explanation
xx0005xx
The INSTALL request failed because the caller does not own the specified data space.
xx0006xx
The INSTALL request failed because the caller specified a data space that does not exist.
xx0102xx
The REMOVE request failed because the caller does not own the specified data space.
xx0103xx
The REMOVE request failed because the caller specified a data space that does not exist.
xxFF01xx
The REFPAT macro request failed because the caller was in cross-memory mode.
xxFF02xx
The REFPAT macro request failed because the caller held one or more locks needed by the system to process the request.
xxFF03xx
The REFPAT macro request failed because a protection exception occurred while referencing the caller's parameter list.
xxFF04xx
The REFPAT macro request failed because reserved fields in the macro parameter list are not zeros.
xxFF05xx
The REFPAT macro request failed because the caller requested an unknown service.
xxFF06xx
The REFPAT macro request failed because the caller must be in 31-bit addressing mode to use any service of the REFPAT macro.
xxFF07xx
The REFPAT macro request failed because the caller cannot be in SRB mode.
xxFF08xx
The REFPAT macro request failed because the virtual storage addresses specified on PSTART and PEND straddle a common area boundary.

System action

The system sends messages about the job to the job log, writes an ABEND dump for the failing job step, and writes the JCL and SYSOUT output for the job.

System programmer response

If the caller was provided by the installation, correct it. Look at accompanying messages in the job log, the JCL and the SYSOUT output.

If the caller was an IBM-supplied program, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the messages, the JCL, the SYSOUT output, and the ABEND dump.

Programmer response

If the caller was an application program, correct the program and run the job again.

Source

Real storage manager (RSM)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014