01D

Explanation

During processing of a DSPSERV or HSPSERV macro, the system found a non-environmental error. The macro processing failed. Register 15 contains a hexadecimal reason code.

For the reason codes presented with format xxzzNNxx, zz must be one of:
  • 07 for CREAD
  • 08 for CWRITE
  • 09 for SREAD
  • 0A for SWRITE
  • FE if the service that is requested cannot be determined
When zz is not one of those values, such as 00, those reason codes do not apply.
Code
Explanation
xxzz07xx
The CREAD or CWRITE request failed because the caller was unauthorized.
xxzz08xx
The indicated address space does not exist or cannot be accessed by the caller.
xxzz09xx
The indicated Hiperspace does not exist or cannot be accessed by the caller. This could be caused by the owner of the Hiperspace being swapped out.
xxzz0Axx
The system does not recognize the macro request.
xxzz0Bxx
A storage key violation occurred on the specified Hiperspace virtual storage.
xxzz0Cxx
The caller did not issue a GETMAIN macro for the indicated address space virtual storage.
xxzz0Dxx
A storage key violation occurred on the specified address space virtual storage.
xxzz0Exx
The specified address space virtual storage did not start on a 4-kilobyte boundary or was not within the bounds of the private area. For CWRITE requests, the specified address space virtual storage did not start on a 4-kilobyte boundary or was not within the bounds of the private area or the (E)CSA area.
xxzz0Fxx
The specified Hiperspace virtual storage did not start on a 4-kilobyte boundary or was not within the bounds of the Hiperspace.
xxzz10xx
The SREAD or SWRITE request failed because it was issued against address space virtual storage that maps a data-in-virtual object, but the storage is virtual I/O (VIO) storage, fixed, or part of a disabled reference (DREF) subpool.
xxzz11xx
The caller specified a value for NUMRANGE that was not in the acceptable range.
xxzz12xx
The SREAD or SWRITE request failed because the caller was in cross-memory mode.
xxzz13xx
The SREAD or SWRITE request failed because it was issued against an ESO Hiperspace.
xxzz14xx
The request failed because the caller is not in 31-bit addressing mode.
xxzz15xx
The specified parameter list or range list is not accessible.
xxzz16xx
The caller specified an incorrect parameter list version.
xxzz17xx
The parameter list contains inconsistent data or data that is not valid.
xxzz18xx
The SWRITE request failed because the caller issued it against Hiperspace storage while a DIV SAVE macro was active.
xxzz19xx
The HSPSERV macro failed because an unauthorized caller requested it against a shared standard Hiperspace without supplying an access list entry token. (ALET).
xxzz1Axx
The supplied access list entry token (ALET) does not belong to the Hiperspace as indicated by the specified STOKEN.
xx0001xx
A problem-state program with PSW key 8-F attempted either to create a SCOPE=ALL or SCOPE=COMMON data space, a disabled reference (DREF) data space, or a non-fetch protected data space, or to assign ownership of a Hiperspace to another task.
xx0002xx
A supervisor-state caller attempted to create a data space on behalf of an owner that is not in the caller's home or primary address space.
xx0003xx
A service request block (SRB) mode request did not specify the owner of the data space or Hiperspace.
xx0004xx
The caller requested that a storage key be assigned to the data space, but the caller was not in supervisor state.
xx0008xx
The system did not create a data space because the designated owner does not exist.
xx000Axx
The problem-state program with PSW key 8-F attempted to prefix the data space name with SYS, which is reserved for system use.
xx000Bxx
The caller specified an incorrect number of blocks for the data space size.
xx000Dxx
The specified data space name is not correct. It must be left-justified or non-blank, can contain only alphabetic, numeric and national characters, cannot start with a numeric character, and must be padded on the right with blanks.
xx000Exx
A supervisor-state caller attempted to prefix the data space name with SYSDS, which is reserved for system use.
xx000Fxx
An unauthorized caller requested creation of an ESO Hiperspace.
xx0011xx
The parameter list is inconsistent.
xx0012xx
An unauthorized caller requested creation of a shared standard Hiperspace.
xx0013xx
An problem-state program with PSW key 8-F tried to create a data space and assign ownership of the data space to a task that is neither the caller's own task nor the caller's job step task.
xx0014xx
The creation of a SCOPE=COMMON data space failed because the caller was swappable or because the system detected that the owner of a SCOPE=COMMON data space has become swappable.
xx0015xx
An attempt was made to create a SCOPE=COMMON data space with a user key (8 - 15).
xx0016xx
HIDEZERO=YES was specified with TYPE=HIPERSPACE.
xx0101xx
The DELETE request failed because a problem program cannot specify TTOKEN.
xx0102xx
An authorized program specified a TTOKEN that is not valid.
xx0103xx
An authorized program attempted to delete a data space on behalf of an owner that is not its home or primary address space.
xx0104xx
A service request block (SRB) mode request failed because it did not specify a TTOKEN, which is required to determine the owner.
xx0105xx
A specified STOKEN does not represent a valid data space.
xx0106xx
The specified STOKEN's owner (as specified by the TTOKEN) is not the owner of the data space.
xx0107xx
The specified data space contains I/O defined pages.
xx0108xx
The specified data space contains pages mapped by the DIV macro.
xx0109xx
The specified data space contained pages for which a DIV SAVE operation was in progress.
xx010Axx
A problem program attempted to delete a SCOPE=ALL or SCOPE=COMMON data space.
xx010Bxx
A problem program attempted to delete a SCOPE=SINGLE data space that has a key different than the caller's key.
xx010Cxx
A problem-state program with PSW key 8-F tried to delete a SCOPE=SINGLE data space, created by the caller's task, that was assigned ownership to a task other than the caller's task or the caller's job step task.
xx010Dxx
The caller attempted to delete a Hiperspace while the Asynchronous Data Mover Facility (ADMF) was still processing a request to transfer data to or from the Hiperspace.
xx010Exx
The caller attempted to delete a data space which has one or more shared segments.
xx0201xx
The RELEASE request failed because the data space does not exist.
xx0202xx
The RELEASE request failed because the start address is not on a page boundary.
xx0203xx
The RELEASE request failed because the input STOKEN is not valid.
xx0204xx
The RELEASE request failed because the number of blocks is not valid.
xx0205xx
The RELEASE request failed because the requested range of blocks is not in the addressable range of the data space.
xx0206xx
The RELEASE request failed because the problem program caller attempted to release a SCOPE=ALL or SCOPE=COMMON data space.
xx0207xx
The RELEASE request failed because the problem-state program tried to release storage in either a Hiperspace it does not own or a SCOPE=SINGLE data space it does not own or did not create, or to release a data space on behalf of an owner that is not in its primary address space or is not the current dispatching task.
xx0208xx
The RELEASE request failed because the supervisor state program attempted to release a private data space on behalf of an owner that is not in the supervisor state's home or primary address space.
xx0209xx
The RELEASE request failed because the caller is not in key 0, and the key for the data space page did not match the caller's key.
xx020Axx
The RELEASE request failed because the data space page is fixed, or fixed in another view of a sharing group.
xx020Bxx
The RELEASE request failed because the caller was disabled and requested release of enabled reference storage.
xx020Cxx
The RELEASE request failed because the caller requested a page that is READONLY.
xx0213xx
The RELEASE request failed because the range list contains a non-zero value in one or more reserved fields.
xx0301xx
The DEFINE IOON request failed because the data space does not exist.
xx0302xx
The DEFINE IOON request failed because the start address is not on a 4-kilobyte boundary.
xx0303xx
The DEFINE IOON request failed because the input STOKEN is not valid.
xx0304xx
The DEFINE IOON request failed because the number of blocks is less than one.
xx0305xx
The DEFINE IOON request failed because the requested addressable range of blocks is not in the range of the data space.
xx0306xx
The DEFINE IOON request failed because the caller was in problem program state and not in system key.
xx0307xx
The DEFINE IOON request failed because the caller attempted to DEFINE IOON for a SCOPE=SINGLE data space on behalf of an owner that is not in the caller's home or primary address space.
xx0308xx
The DEFINE IOON request failed because the data space page has a DIV SAVE operation in progress.
xx0309xx
The DEFINE IOON request failed because it was issued for a hiperspace.
xx030Bxx
The DEFINE IOON request failed because the caller was disabled and specified storage that was neither in a disabled reference (DREF) state or an IOON state.
xx030Cxx
The DEFINE IOON request failed because the input range list contains a non-zero value in one or more reserved fields.
xx030Fxx
The DEFINE IOON request failed because the target page was backed by a one megabyte frame that was already page fixed, and the request was to page fix a subset of the one megabyte page. The one megabyte page could not be demoted.
xx0401xx
The DEFINE IOOFF request failed because the data space does not exist.
xx0402xx
The DEFINE IOOFF request failed because the start address is not on a 4-kilobyte boundary.
xx0403xx
The DEFINE IOOFF request failed because the input STOKEN is not valid.
xx0404xx
The DEFINE IOOFF request failed because the number of blocks is less than one.
xx0405xx
The DEFINE IOOFF request failed because the requested addressable range of blocks is not in the data space.
xx0406xx
The DEFINE IOOFF request failed because the caller was in problem program state and not in system key.
xx0407xx
The DEFINE IOOFF request failed because the caller attempted to DEFINE IOOFF for a SCOPE=SINGLE data space on behalf of an owner that is not in the caller's home or primary address space.
xx0408xx
The DEFINE IOOFF request failed because it was issued for a Hiperspace.
xx040Cxx
The DEFINE IOOFF request failed because the input range list contains a non-zero value in one or more reserved fields.
xx040Fxx
The DEFINE IOOFF failed, caller tried to DEFINE IOOFF (unfix) a partial large page segment.
xx0501xx
The specified STOKEN does not represent a valid data space or represents a data space for which the caller is not authorized.
xx0503xx
The new current size exceeds the maximum size for the data space and Hiperspace.
xx0601xx
The DEFINE DREFON request failed because the data space does not exist.
xx0602xx
The DEFINE DREFON request failed because the start address is not on a 4-kilobyte boundary.
xx0603xx
The DEFINE DREFON request failed because the input STOKEN is not valid.
xx0604xx
The DEFINE DREFON request failed because the number of blocks is less than one.
xx0605xx
The DEFINE DREFON request failed because the requested addressable range of blocks extends beyond the end of the data space.
xx0606xx
The DEFINE DREFON request failed because the caller was not in supervisor state.
xx0607xx
The DEFINE DREFON request failed because the caller attempted to use DREFON against storage in a scope-single data space on behalf of an owner that is not in the home or primary address space.
xx0608xx
The DEFINE DREFON request failed because the data space page has a DIV SAVE operation in progress.
xx0609xx
The DEFINE DREFON request failed because the input STOKEN is for a Hiperspace.
xx060Axx
The DEFINE DREFON request failed because the specified area is part of a data space that was created with a disabled reference (DREF) attribute.
xx060Bxx
The DEFINE DREFON request failed because the caller was disabled and specified storage that was neither in a disabled reference (DREF) state nor an IOON state.
xx060Cxx
The DEFINE DREFON request failed because the input range list contains a non-zero value in one or more reserved fields.
xx060Dxx
The requestor tried to DEFINE DREFON for a data space with shared segments.
xx060Fxx
The DEFINE DREFON failed, caller tried to DEFINE DREFON (fix) a partial large page segment.
xx071Bxx
CREAD processing detected a PGSER fix in progress for the address space virtual storage.
xx0B01xx
An OUT failed because the data space does not exist.
xx0B02xx
An OUT failed because the start address is not on a page boundary.
xx0B03xx
An OUT failed because the input STOKEN is not representing a caller's data space.
xx0B04xx
An OUT failed because the number of blocks is not valid.
xx0B05xx
An OUT failed because the requested range of blocks is not in the range of the data space.
xx0B06xx
An OUT failed because the problem program caller attempted to OUT a SCOPE ALL or SCOPE COMMON data space.
xx0B07xx
An OUT failed because the problem program caller attempted to OUT a data space on behalf of an owner that is not in its primary address space.
xx0B08xx
An OUT failed because the supervisor state program attempted to OUT a scope single data space on behalf of an owner that is not in its home address space.
xx0B09xx
An OUT failed because the data space is a Hiperspace.
xx0C01xx
A LOAD failed because the data space does not exist.
xx0C02xx
A LOAD failed because the start address is not on a page boundary.
xx0C03xx
A LOAD failed because the input STOKEN is not valid.
xx0C04xx
A LOAD failed because the number of blocks is not valid.
xx0C05xx
A LOAD failed because the requested range of blocks is not in the range of the data space.
xx0C06xx
A LOAD failed because the problem program caller attempted to LOAD a SCOPE ALL or SCOPE COMMON data space.
xx0C07xx
A LOAD failed because the problem state program caller attempted to load a data space on behalf of the data space owner, but the data space is not in the owner's primary address space.
xx0C08xx
A LOAD failed because the supervisor state program attempted to load a scope single data space on behalf of the data space owner, but the data space is not in the owner's home address space.
xx0C09xx
A LOAD failed because the data space is a Hiperspace.
xx0D01xx
The DEFINE DREFOFF failed because the data space does not exist.
xx0D02xx
The DEFINE DREFOFF failed because the start address is not on a 4-kilobyte boundary.
xx0D03xx
The DEFINE DREFOFF failed because the input STOKEN is not valid.
xx0D04xx
The DEFINE DREFOFF failed because the number of blocks is less than one.
xx0D05xx
The DEFINE DREFOFF failed because the requested addressable range of blocks is not in the range of the data space.
xx0D06xx
The DEFINE DREFOFF failed because the caller was not processing in supervisor state with a system program status word (PSW) key.
xx0D07xx
The DEFINE DREFOFF failed because the caller attempted to DEFINE DREFOFF a SCOPE SINGLE or data space on behalf of an owner that is not in its home or primary address space.
xx0D09xx
The DEFINE DREFOFF failed because the input STOKEN is for a Hiperspace.
xx0D0Axx
The DEFINE DREFOFF failed because the specified area is part of a data space that was created with the disabled reference attribute.
xx0D0Dxx
The requestor tried to DEFINE DREFOFF for a data space with shared segments.
xx0D0Exx
A DSPSERV DEFINE DREFOFF is issued with FORCE option. The option is no longer supported.
xx0D0Fxx
The DEFINE DREFOFF failed, caller tried to DEFINE DREFOFF (unfix) a partial large page segment.
xxFF01xx
The DSPSERV macro request failed because a secondary address space identifier (ASID) is not valid.
xxFF02xx
The request failed because the caller held locks but indicated DISABLED=NO.
xxFF03xx
The DSPSERV macro request failed because the caller issued a macro version that is not valid.
xxFF04xx
The DSPSERV macro request failed because reserved fields in the macro parameter list are not zeros.
xxFF05xx
The DSPSERV macro request failed because the caller requested an unknown service.
xxFF06xx
The DSPSERV macro request failed because a protection exception occurred while referencing the caller's parameter list.
xxFF07xx
The DSPSERV macro request failed because the caller must be in 31-bit addressing mode to use any service of the DSPSERV macro.
xxFF08xx
The request failed because the caller was disabled but requested a service that requires the caller to be enabled.
xxFF09xx
The request failed because the caller held one or more locks needed by the system to process the request.
xxFF0Axx
The request failed because the caller specified an input range list for a service that does not support a range list.
xxFF0Bxx
The request failed because the caller specified an incorrect value for NUMRANGE. It must be greater than zero.
xxFF0Cxx
The request failed because the caller specified a value for NUMRANGE that exceeded the maximum of 16 for an unauthorized caller.
xxFF0Dxx
The request failed because the caller specified an input range list that is not accessible to the service using the caller's PSW key.
xxFF10xx
The DEFINE request failed because IOON or IOOFF was incorrectly coded.

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)