IOxx Error Messages
The following error codes are I/O errors and thus have the subsystem prefix of •IO." All of the IOxx errors with error qualifier 0 are equivalent to the RTE IOxx errors.
IOXX Error Messages
Code | Meaning | Action |
|
|
|
IOXX(0) | See RTE IOxx Errors for |
|
| description. |
|
|
|
|
IO00(4) – INVALID CLASS | (#RQUE) Source class | Correct call parameters and try |
SPECIFICATION | parameter is zero or greater | again. |
| than maximum class number. |
|
|
|
|
IO01(1) – IMPROPER, | (DEXEC) A parameter error has | Correct your DEXEC call |
MISSING, OR TOO MANY | been detected by the DEXEC | parameters and try again. |
PARAMETERS | intrinsic. |
|
|
|
|
IO01(2) – IMPROPER OR | (EXECM) A parameter error has | Correct your DEXEC call |
MISSING PARAMETERS | been detected by EXECM. | parameters and try again. |
|
|
|
IO01(4) – PARAMETER | (#RQUE) Call parameters are | Correct call parameters and try |
MISSING, INVALID, OR | missing or invalid or the search | again. |
CLASS SEARCH FAILED | for the class header failed. |
|
|
|
|
IO02(4) | (#RQUE) Illegal logical unit | Correct LU and try again. |
| number. |
|
|
|
|
IO04(1) – IMPROPER | (DEXEC) (a) User buffer length | Correct call parameters and try |
BUFFER SPECIFICATION | specification > 512 words; (b) In | again. |
| a write/read request, the write |
|
| length is greater than the read |
|
| length. |
|
|
|
|
IO04(4) – INVALID BUFFER | (#RQUE) An illegal buffer was | Correct call parameters and try |
SPECIFICATION | specified. Extends beyond | again or check SAM usage. |
| RT/BG area or not enough SAM |
|
| to buffer the request. |
|
|
|
|
IO07(2) – DRIVER | (EXECM) A request issued by | Correct call parameters and try |
REJECTED REQUEST | EXECM in response to a user | again. |
| call to the DEXEC intrinsic has |
|
| resulted in a rejection by the |
|
| driver. |
|
|
|
|
IO10(4) – PROGRAM | (#RQUE) Another program is | Try again. |
WAITING ON SOURCE CLASS | waiting on the source class |
|
| number and requeueing is not |
|
| allowed. |
|
|
|
|
IO12(2) – LU NOT DEFINED | (EXECM) The session you are | Either log on to an account with |
FOR THIS SESSION | executing under at the remote | the necessary resources or have |
| node does not have the | them added to the default |
| specified LU defined. This may | account definition. |
| be the result of a logon failure or |
|
| inadequate resources of the |
|
| default session account. |
|
|
|
|
Alphanumeric Error Messages 39