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


2C6

z/OS MVS System Codes
SA38-0665-00

2C6

Explanation

The MIHQUERY service, the IOSCDR service, the IOSPTHV service, or the IOSCAPU service has encountered an abend condition while attempting to satisfy the caller's request.

MIHQUERY

The reason codes for the MIHQUERY service are as follows:
0001
Caller of MIHQUERY is not in supervisor state.
0002
Caller of MIHQUERY is not in key 0-7.
0003
Incorrect parameter list. For one of the following reasons, an error occurred when the MIHQUERY service tried to copy the list:
  • The caller passed an incorrect parameter list address.
  • The caller passed an address that the caller did not own.
  • The storage was in an incorrect key.
0004
Incorrect parameter list. For one of the following reasons, an error occurred when the MIHQUERY service tried to update the list:
  • The caller passed an incorrect parameter list address.
  • The caller passed an address that the caller did not own.
  • The storage was in an incorrect key.
The caller might have freed the parameter list between the time when MIHQUERY copied the parameter list and the time when it updated the list.
0005
The caller of MIHQUERY passed an incorrect UCB address in the parameter list.
0006
The caller of MIHQUERY is in cross memory mode; that is, PASN=HASN=SASN is not in effect.

IOSCDR

The reason codes for the IOSCDR service are as follows:
0100
Incorrect authorization. For LINKAGE=LINK callers, the caller is not in supervisor state. For LINKAGE=SYSTEM callers, the caller is not any one of the following:
  • In supervisor state
  • In PKM 0-7
  • In problem state
  • In PSW key 0-7
  • APF-authorized
  • RACF® authorized to the FACILITY class and the IOSCDR entity.
0101
Caller of IOSCDR is not in task mode.
0102
Caller of IOSCDR is locked.
0103
Incorrect AMODE. Caller of IOSCDR is not in 31-bit mode.
0200
Incorrect parameter list. Caller of IOSCDR passed an incorrect version of the parameter list.
0201
Incorrect parameter list. The integrity of the parameter list was compromised. For example, more than one parameter in a list of mutually exclusive parameters was specified.
0202
Incorrect parameter list. For one of the following reasons, an error occurred when the IOSCDR service tried to read the list:
  • The caller passed an incorrect parameter list address.
  • The caller passed an address that the caller did not own.
  • The storage was fetch protected.
0203
Incorrect parameter list. For one of the following reasons, an error occurred when the service tried to update the list:
  • The caller passed an incorrect parameter list address.
  • The caller passed an address that the caller did not own.
  • The storage was in a key that is not accessible from the key of the caller.
The caller might have freed the parameter list between the time when the service read the parameter list and the time when it updated the list. In addition, if the storage is not accessible from the key of the caller, then reads may work, but updates may not.
0204
Incorrect IOCTOKEN storage. For one of the following reasons, an error occurred when the service tried to read the IOCTOKEN.
  • The caller passed an incorrect IOCTOKEN address.
  • The caller passed an address that the caller did not own.
  • The storage is fetch protected.
0205
Incorrect IOCTOKEN. For one of the following reasons, an error occurred when the service tried to update the IOCTOKEN:
  • The caller passed an incorrect IOCTOKEN address.
  • The caller passed an address that the caller did not own.
  • The storage was in a key that is not accessible from the key of the caller.
The caller might have freed the IOCTOKEN storage between the time when the service read it and the time when it attempted to update it. In addition, if the storage is not accessible from the key of the caller, then reads may work, but updates may not.
0206
Incorrect CDRAREA. For one of the following reasons, an error occurred when the IOSCDR service tried to update the CDRAREA.
  • The caller passed an incorrect CDRAREA address.
  • The caller passed an address that the caller did not own.
  • The storage was in a key that is not accessible from the key of the caller.
The caller might have freed the CDRAREA storage before IOSCDR attempted to update it.

IOSPTHV

The reason codes for the IOSPTHV service are as follows:
0100
Caller of IOSPTHV is not in supervisor state.
0101
Caller of IOSPTHV is not in task mode.
0102
Caller of IOSPTHV is locked.
0103
Incorrect AMODE. Caller of IOSPTHV is not in 31-bit mode.
0200
Incorrect parameter list. Caller of IOSPTHV passed an incorrect version of the parameter list.
0201
Incorrect parameter list. For one of the following reasons, an error occurred when the IOSPTHV service tried to read the list:
  • The caller passed an incorrect parameter list address.
  • The caller passed an address that the caller did not own.
  • The storage was fetch protected.
0202
Incorrect parameter list. For one of the following reasons, an error occurred when the IOSPTHV service tried to update the list:
  • The caller passed an incorrect parameter list address.
  • The caller passed an address that the caller did not own.
  • The storage was in a key that is not accessible from the key of the caller.
The caller might have freed the parameter list between the time when the service read the parameter list and the time when it updated the list. In addition, if the storage is not accessible from the key of the caller, then reads may work, but updates may not.
0203
Incorrect IOCTOKEN storage. For one of the following reasons, an error occurred when the IOSPTHV service tried to read the IOCTOKEN.
  • The caller passed an incorrect IOCTOKEN address.
  • The caller passed an address that the caller did not own.
  • The storage is fetch protected.
0204
Incorrect IOCTOKEN. For one of the following reasons, an error occurred when the service tried to update the IOCTOKEN:
  • The caller passed an incorrect IOCTOKEN address.
  • The caller passed an address that the caller did not own.
  • The storage was in a key that is not accessible from the key of the caller.
The caller might have freed the IOCTOKEN storage between the time when the service read it and the time when it attempted to update it. In addition, if the storage is not accessible from the key of the caller, then reads may work, but updates may not.
0205
Incorrect MSGBUF. For one of the following reasons, an error occurred when the IOSPTHV service tried to update the MSGBUF.
  • The caller passed an incorrect MSGBUF address.
  • The caller passed an address that the caller did not own.
  • The storage was in a key that is not accessible from the key of the caller.
The caller might have freed the MSGBUF storage before IOSPTHV attempted to update the MSGBUF.

IOSCAPU

The reason codes for the IOSCAPU service are as follows:
01000100
Caller of IOSCAPU CAPTUCB or IOSCAPU UCAPTUCB is locked or is not enabled.
01000101
Caller of IOSCAPU CAPTOACT is locked.
01000102
Caller is in SRB mode during nucleus initialization program (NIP) processing and authorization for a PC routine is not available.
01000103
Caller of IOSCAPU CAPTUCB or IOSCAPU UCAPTUCB is in cross memory mode.
01000104
Caller of IOSCAPU CAPTUCB, IOSCAPU UCAPTUCB, or IOSCAPU CAPTOACT ASID is in problem state and is not in key 0-7.
01000200
Caller of IOSCAPU passed an incorrect version of the parameter list.
01000201
For one of the following reasons, the integrity of the parameter list was compromised:
  • More than one parameter in a list of mutually exclusive parameters was specified.
  • A function parameter was not specified.
  • Reserved fields are not zero.
  • A required parameter associated with a function parameter was not specified.
01000202
For one of the following reasons, an error occurred when IOSCAPU tried to read the parameter list:
  • The caller passed an incorrect parameter list address.
  • The caller passed an address that the caller did not own.
  • The storage was fetch protected.
01000203
For one of the following reasons, an error occurred when IOSCAPU tried to update the parameter list:
  • The caller passed an incorrect parameter list address.
  • The caller passed an address that the caller did not own.
  • The storage was in a key that is not accessible from the key of the caller.
01000204
The access list entry token (ALET) for the parameter list is not valid.
01000205
The requested function does not exist.
01000300
The release of the specified captured UCB exceeds the number of captures specified with the LASTING parameter or in SRB mode.

System action

The system continues processing. The caller ends abnormally with the appropriate reason code.

Application Programmer Response: The application recovery routine should have recorded and/or dumped the data needed to debug this problem. The dumped data should include the parameter list and its UCB address, the caller's key and the key of the storage that the caller was attempting to obtain. Correct the application and resubmit. If the recovery routine did not save the dump information, fix the recovery routine and try to recreate the original problem. If the error recurs, notify the system programmer.

System programmer response

If the application programmer is unable to debug the error, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the dump data from the application recovery routine.

Source

Input/output supervisor (IOS)

Parent topic: System completion codes

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014