| 0 (X'00') |
|
SUCCESSFUL: The request
to the service completed
without error. |
| 4 (X'04') |
|
REQUEST FAILED: The
request to the service completed
with the reason code specified below. |
| |
1 (X'01') |
Some or all of the eligible volumes for allocation
are unknown to the system. |
| |
2 (X'02') |
Some
or all of the separation volumes are unknown
to the system. |
| |
3 (X'03') |
Some or
all of the volumes in both the eligible
and separation lists are unknown to the system. |
| |
4 (X'04') |
INSUFFICIENT STORAGE: GETMAIN failure occurred
within the service. This may indicate that the region size for your
IDCAMS job or the region size for TSO/E needs to be increased. IDCAMS
should have issued IDC2011I when this error code was returned. Refer
to IDC2011I for details on the error condition. If the GETMAIN failure
is for a system component, then a system message indicating the failure
should appear on the system console, and you should follow the directions
for the system component's message. |
| |
8 (X'08') |
INVALID
PARAMETER LIST: Internal error. IDCAMS
should have issued IDC31601I or IDC31550I for this error condition.
Refer to this message for further details on the error. If the error
was received for a system component, this error code indicates an
internal error in that component. |
| |
12 (X'0C') |
UNAUTHORIZED
REQUEST: IDCAMS was not authorized
for this request. Possible reasons are that IDCAMS was: invoked by
a TSO CALL command; not link-edited as authorized; not residing in
an authorized library. This should not occur with any system component
modules. Contact your system programmer. |
| |
16 (X'10') |
UNABLE TO ESTABLISH ESTAE: Internal error. IDCAMS
should issue message IDC2391I when this error occurs. Refer to this
message for further details on the error condition. If this error
occurs with any other system component, refer to messages issued by
that component (for example, SMS) for details on that component's
recovery actions. |
| |
20 (X'14') |
INVALID
CCW OR DATA AREA POINTER: Internal error.
IDCAMS should issue message IDC31602 when this error occurs. Refer
to this message for further details on the error condition. This is
an internal error with all other system components. Refer to messages
that the other components issue. |
| |
24 (X'18') |
INVALID
REQUEST TYPE FOR CONTROL UNIT: Internal
error. |
| |
28
(X'1C') |
SUBSYSTEM DATA AREA NOT
LARGE ENOUGH: Internal
error. |
| |
32
(X'20') |
UNABLE TO LOCATE SSSCB
ENTRY: Internal error. |
| |
36 (X'24') |
REQUEST
BUFFER SIZE NOT A MULTIPLE OF 8: Internal
error. |
| |
40
(X'28') |
CONFIGURATION TABLE INDEX
TOO HIGH: Internal error. |
| |
44 (X'2C') |
SSSCBUPD
VALUE(S) INVALID: Internal error. |
| |
48 (X'30') |
UNABLE
TO OBTAIN COMPLETE SSSCB ENTRY: Internal
error. |
| |
52
(X'34') |
DEVICE NUMBER INVALID:
Internal error. |
| |
56 (X'38') |
UCB ADDRESS
OR DEVICE NUMBER NEEDED FOR RACF® CHECK:
Internal error. |
| |
60 (X'3C') |
INVALID RACF LEVEL:
Internal error. |
| |
64 (X'40') |
INVALID
COMMIT/DISCARD EXTENTS OR DISCARD PSFFLAG:
Internal error. |
| |
68 (X'44') |
UNABLE
TO DESTAGE DATA ON A COMMIT: Internal error. |
| |
72 (X'48') |
INVALID CFW TOKEN: Internal error. |
| |
76 (X'4C') |
ONLY ONE ACCESS CODE AVAILABLE: Internal error. |
| |
80 (X'50') |
INVALID EYE-CATCHER IN SERVL OR UNABLE TO ACCESS
LAST BYTE IN SERVL: Internal error. |
| |
84(X'54') |
UCB
ADDRESS OR DEVICE NUMBER POINTS TO NON-DASD
DEVICE: Internal error. |
| |
88 (X'58') |
SSDL
MISSING: Internal error. |
| |
92 (X'5C') |
REQTYPE
DRVR PARM(S) NOT ALLOWED: Internal error. |
| |
96 (X'60') |
SSDP AND SSDL NOT ALLOWED: Internal error. |
| |
100 (X'64') |
REQUEST BUFFER HAS ONLY ONE SUB-BUFFER: Internal
error. |
| |
104
(X'68') |
INDIRECT ADDRESS LISTS
NOT ALLOWED IN DRVR CHANNEL
PROGRAM: Internal error. |
| |
108 (X'6C') |
TIC
MUST POINT AT *-8: Internal error. |
| |
112 (X'70') |
UCB
ADDRESS OR DEVICE NUMBER MISSING: Internal
error. |
| |
116
(X'74') |
SSDP MISSING: Internal
error. |
| |
120
(X'78') |
COUNT MISSING FROM EXTENT
BUFFER: Internal error. |
| |
124 (X'7C') |
NO
3990 MODEL 3 IN THE SYSTEM: Internal error. |
| |
128 (X'80') |
INVALID REQUEST FOR REQTYPE MULTI: Internal error. |
| |
132 (X'84') |
INVALID EYE-CATCHER IN INPUT BUFFER: Internal
error. |
| |
136
(X'88') |
SSDP POINTS TO AREA NOT
OWNED BY CALLER: Internal
error. |
| |
140
(X'8C') |
DEVICE TO BE USED FOR
AOMSERV REQUEST DOES NOT
POINT TO THE BASE UCB OF A MULTIPLE EXPOSURE D/T3350: AOMSERV caller
error. UCB pointer must be corrected to point at the base UCB for
the device. |
| 8 (X'08') |
|
OPERATION FAILED:
The request to the service completed
with the reason code specified below. |
| |
1 (X'01') |
AOM01039 was passed a SERVL in which either SERVVPTR
or SEVSPTR is zero. |
| |
2 (X'02') |
AOM01039
was passed a SERVL in which either the
eligible or separation volume count is zero. |
| |
3 (X'03') |
The chain of pointers needed to locate the SSCT
contains a zero pointer. |
| |
4 (X'04') |
I/O
ERROR EXECUTING CALLER'S CHANNEL PROGRAM:
An I/O error occurred. IDCAMS issues message IDC31559I when sense
data is available. Otherwise, IDCAMS issues message IDC2375I. Refer
to that message for further information on the error condition. For
other system components (for example, SMS), refer to messages issued
by those components detailing actions taken as the result of this
I/O error. Refer to SYS1.LOGREC for information regarding the specific
I/O error that occurred. |
| |
5 (X'05') |
Volume
List storage is not owned by caller. Set
by IGX00039 ESTAE routine. |
| |
6 (X'06') |
Separation
List storage is not owned by caller.
Set by IGX00039 ESTAE routine. |
| |
8 (X'08') |
ASYNCHRONOUS
OPERATION PENDING: The asynchronous
operation is still in progress, and IDCAMS should still be waiting
for completion. For other system components (for example, SMS), refer
to messages issued by those components detailing actions taken as
the result of this return/reason code. Check IOSCOD
and IOSXRCOD, saved in AOMSERVL, for more details. |
| |
12 (X'0C') |
ASYNCHRONOUS OPERATION COMPLETED IN ERROR: IDCAMS
should issue message IDC31610I for this error condition. Refer to
that message for details on the error. For other system components
(for example, SMS), refer to messages issued by those components detailing
actions taken as the result of this return/reason code. |
| |
16 (X'10') |
ASYNCHRONOUS OPERATION FAILED: IDCAMS should issue
message IDC31610I for this error condition. Refer to that message
for details on the error. For other system components (for example,
SMS), refer to messages issued by those components detailing actions
taken as the result of this return/reason code. |
| |
20 (X'14') |
ASYNCHRONOUS OPERATION TIME OUT: The asynchronous
operation is still in progress, but the timer for IDCAMS waiting for
the operation has expired. When the asynchronous operation completes,
if it 'Fails' or 'Completes In Error' message AOM000I will be issued
to the system console. If the operation is successful, the status
will be correctly reflected in the storage control and in all attached
host systems. Generally this error will occur while establishing or
reestablishing a dual copy pair and contention from other hosts or
the host trying to do the operation causes time to be taken away from
the 3990 copy operation. For other system components (for example,
SMS), refer to messages issued by those components detailing actions
taken as the result of this return/reason code. |
| |
24 (X'18') |
REQUEST LOST BY SUBSYSTEM: The storage control
lost knowledge of the asynchronous operation. Refer to a merged LOGREC
listing for more details. Running an IDCAMS LISTDATA report will give
you the current state of the subsystem and device. After determining
the current state, you may need to rerun your IDCAMS job to establish
the new states that you desire. For other system components (for example,
SMS), refer to messages issued by those components detailing actions
taken as the result of this return/reason code. |
| |
28 (X'1C') |
DESTAGE-ALL DID NOT COMPLETE SUCCESSFULLY: message
AOM001I is issued for a failing subsystem. Refer to message AOM001I
for the problem determination information required to isolate the
devices attached to the subsystem that have pinned data. |
| |
32 (X'20') |
I/O ERROR EXECUTING INTERNAL CHANNEL PROGRAM:
Internal error. |
| |
36 (X'24') |
I/O ERROR
AFTER RE-DRIVING CHANNEL PROGRAM TO
ESTABLISH A DUAL COPY PAIR: Internal error. |
| |
40 (X'28') |
THE DEVICE TO BE USED FOR THE AOM DRIVER REQUEST
HAS NO LOGICAL PATHS ONLINE OR THE I/O OPERATION COMPLETED WITH CONDITION
CODE 3 (Device not operational): Ensure that the correct device is
being referenced and that a minimum of one logical and one physical
path is available. |
| |
44 (X'2C') |
AOM RECEIVED
INTERVENTION REQUIRED IN RESPONSE
TO AN I/O OPERATION TO DEVICE: Ensure that the correct device is being
referenced and is available to system. If the device is available,
follow your installation's procedures for resolving hardware problems. |
| 12 (X'0C') |
|
ASYNCHRONOUS OPERATIONS
MANAGER ERROR: The request
to the service completed with the reason code specified below. |
| |
1 (X'01') |
Load module AOM01039 could not be loaded by module
IGX00039. SERVFRC will contain the failure return code from LOAD.
This code is set by module IGX00039. |
| |
2 (X'02') |
AOM01039 was passed a SERVL in which either the
eligible or separation volume count is zero. |
| |
4 (X'04') |
An asynchronous I/O operation ended with an unexpected
completion status. For diagnostic purposes, the unexpected status
is stored in the SERVL control block at offset '24'X (immediately
following SERVRETC and SERVREAS). The SERVL is traced using CTRACE
(refer to Using IPCS to format the AOM trace table). |
| |
8 (X'08') |
ABNORMAL TERMINATION: Internal error. |
| |
12 (X'0C') |
BRANCH ENTRY ADDRESS FOR ASYNCHRONOUS OPERATIONS
MANAGER NOT FOUND IN SSSVT: Internal error. |
z/OS DFSMSdfp Diagnosis
Copyright IBM Corporation 1990, 2014