Explanation
An error occurred during 
Device Allocation processing.
Register 15 contains
a hexadecimal reason code that you should report to the IBM® Support Center.
The following are
valid hexadecimal reason codes, for cases where the system programmer
might or might not be able to take corrective actions. There are other
internal reason codes that are not listed here. For any reason code
not documenented here, search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM Support Center.- Code
- Explanation
- 001
- System address space initialization denied the request to create
the allocation address space.
- 002
- The allocation address space received a nonzero return code from
GETMAIN processing.
- 003
- The display allocation tables manager received a request which,
if processed, would cause the DALTUSE count to be less than zero.
- 004
- An allocation module issued the POST macro instruction, and the
macro processing has entered the routine specified on the ERRET parameter.
- 005
- An allocation module issued the ESTAE macro instruction, and the
return code from ESTAE processing was not zero.
- 006
- An allocation module issued the STIMERM macro instruction, and
the macro processing has entered the routine specified on the ERRET
parameter.
- 101
- The ATTACH macro instruction was issued for the eligible device
table (EDT) verification routine during allocation initialization
processing. The return code from the ATTACH routine was not zero.
- 102
- An error occurred during an RESMGR ADD TYPE(ADDRSPC) when establishing
the ATS Address Space Resource Manager.
- 103
- An error occurred during an RESMGR ADD TYPE(TASK) when establishing
the ATS Task Resource Manager.
- 200
- IEFAB4F7 was called to read a single SWA block, and the SWAREQ
was unsuccessful.
- 201
- Allocation was invoked during DDR SWAP to update the unit control
block (UCB) pointer list (UPL) so that the UPL would reflect the swapped
UCBs. However, one or both of the swapped UCB addresses is not in
the UPL.
- 202
- Invalid UCB address.
- 203
- IEFAB4FP discovered that SIOTDDIB does not point to a DDIB.
- 210
- Invalid JCT in the JSCB.
- 211
- Invalid SCT in the JSCB.
- 212
- Invalid ACT in the JCT.
- 213
- Invalid ACT in the SCT.
- 214
- Invalid SVA found in IEFAB4FE.
- 219
- Internal error in Allocation I/O count table.
- 21A
- Internal error in Allocation data set ENQ management.
- 21C
- Allocation found a circular PDB chain when performing pending
device processing.
- 21D
- An allocation module issued the ISGENQ macro instruction, and
the return code from ISGENQ processing indicates that the token for
that particular ENQ was unable to be obtained.
- 21E
- Failed to attach IEFA1HST task.
- 220
- Device is not automatically switchable for a function that requires
it.
- 221
- Device is not registered to this system.
- 224
- Device type ENQ not held before requesting more than one Device
ENQ on a single request.
- 225
- Device ENQ not held before requesting a function on a device that
requires it.
- 226
- Needed device array was not passed to the IEFAB4FX service.
- 227
- Needed device type array was not passed to the IEFAB4FX service.
- 228
- Invalid function request for the IEFAB4FX service.
- 229
- Individual General Device Element (IGDE) not found.
- 230
- NED not found for self-describing device.
- 231
- Invalid Queue Manager Queue Block Chain (used by QMQBLK processing,
not IEFAB4FX)
- 232
- Unrecognized return code from IEFOIGDE methods.
- 233
- IGDE was not built when it was expected to be.
- 234
- TCB and/or ASCB address not supplied when requesting clean up
for terminating TCB or ASCB.
- 235
- Non-zero return code received from ?IXCMSGO.
- 236
- IGDE not owned when it should have been.
- 237
- Attempt to push a non-AS device.
- 238
- Recovery was entered after an abend or cancel and the ATS Service
Routines Recovery block (IEFZATRB) or Allocation Automatic Tape Sharing
(ATS) Parameter List (IEFZATSP)was corrupted. The address space has
been taken down to clean up ATS ENQs and Latches.
- 240
- An Autoswitchable (AS) device chosen for allocation is not assigned.
- 241
- DDR Swap failed because GRS failed trying to swap Device ENQs.
- 243
- IEFASWAP failed, issued against the target task.
- 244
- IEFASWAP failed, issued against the DDR/SWAP task.
- 245
- ENQ/DEQ for Tape device failed.
- 246
- Allocation Recovery is unable to verify all Automatic Tape Sharing
(ATS) Device ENQs have been released.
- 253
- A loop was detected in Queue Manager Queue Control Block.
- 254
- Detected a corrupted hash value.
- 255
- The request attempted to assign ownership to another TCB unconditionally.
- 257
- Error in determining the UCB common extension address by IOS.
- 301
- At the end of processing all allocation requests for a job step,
an unsatisfied request is detected. An incorrectly modified eligible
device table (EDT) or specifying VSAM parameters for a non-VSAM data
set is the probable cause.
- 303
- Error encountered in the EDL storage manager.
- 304
- Unexpected return code for IEFAB480.
- 305
- Either the EDT library section does not exist or an error occurred
while obtaining the library names from the current configuration.
- 306
- IEFAB480 found a cost adjustment value of zero which would fail
to decrease any transformed costs (TCs).
- 307
- IEFAB480 found an edge with a valid transformed cost (TC), but
never adjusted the transformed cost.
- 308
- Two jobs are allocated to the same tape drive.
- 309
- Devices selected by JES3 are not in the Allocation Eligible Device
List (EDL). Check the Job Log of the failing job for messages IEF202I/IEF272I.
Message IEF202I indicates that a previous step was not run because
of:
- condition codes
- COND=even
- COND=only
Message IEF272I indicates that a previous step was not executed.
- 311
- Array bounds were exceeded for an internal control block during
Tape Device Allocation. Search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM Support Center and provide the dump.
- 313
- Internal error in the allocation dynamic storage manager.
- 30A
- Invalid JCT in the JSCB.
- 30B
- Invalid first SCT in the JCT.
- 30C
- Invalid next SCT in the SCT.
- 30D
- An allocation module called SMS for the Data Set Stacking operation.
SMS returned an unrecognized return code.
- 30E
- An allocation module called SMS for the Device Pool Services.
SMS returned an unrecognized return code.
- 30F
- SIOT not found for affed DD (UNIT=AFF). Issued from IEFAB4FE.
- 501
- Undefined return code from JES3.
- 604
- IEFAB4MG (called by macro IEFMSGBL) was attempting to build a
message, but no message definition was found.
- 608
- IEFAB4MG (called by macro IEFMSGBL) was attempting to build a
message, but the SIOT pointer required for this message was not found.
- 60C
- IEFAB4MG (called by macro IEFMSGBL) was attempting to build a
message, but an incorrect number of variables was supplied.
- 610
- IEFAB4MG (called by macro IEFMSGBL) was attempting to build a
message, but an invalid buffer was passed.
- 614
- IEFAB4MG (called by macro IEFMSGBL) was attempting to build a
message, but no storage was defined for the message buffer.
- 618
- IEFAB4MG (called by macro IEFMSGBL) was attempting to build a
message, but the message text was too long.
- 701
- The scheduler JCL facility (SJF) returned an unexpected return
code or reason code.
- 702
- SVC 99 caller does not hold the SYSZTIOT resource and has requested
that TIOT resource be obtained.
- 704
- SIOT to be dechained is not found in the SIOT chain.
- 804
- Allocation tried to remove a DSAB entry from the dynamic communication
table, but the entry did not exist.
- 807
- Allocation tried to mark a DSAB entry in the dynamic communication
table as eligible for remove in-use processing, but the entry did
not exist.
- 80B
- Allocation tried to change the TCB address of a DSAB entry in
the dynamic communication table, but the entry did not exist.
- 8FF
- Allocation's dynamic communication table manager was called with
an invalid function code.
- xxxx0A90
- The system could not allocate a request, and the installation
has activated a DIAGxx parmlib member to cause this abend and obtain
an SDUMP of the problem.
- xxxx0A92
- The system could not allocate a request, and the installation
has activated a DIAGxx parmlib member to cause this abend and obtain
an SDUMP of the problem.
- xxxx0A93
- The system could not allocate a request, and the installation
has activated a DIAGxx parmlib member to cause this abend and obtain
an SDUMP of the problem. Remote SDUMPs of all systems in the sysplex
will be requested.
System action
For job-related errors, the system
may issue message IEF197I with the abend code and the reason code.
The system may also issue other messages related to the error. The
system stops allocation processing for the step. The system ends the
job. For errors that are not related to a job, the system may issue
other messages related to the error.
In all cases,
the system writes an SVC dump, and writes a logrec data set error
record.
For reason code 21C, Allocation will search for devices
that are pending offline or pending unload and will process them appropriately.
However, any commands or services that requested device(s) to be taken
offline or unloaded may not be notified that the device(s) have been
processed. This may leave the requestor waiting indefinitely.
For
reason code 229, if the number of the device can be determined, message
IEF707I is issued indicating the device number.
System programmer response
Search problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM Support Center.
For reason code 21C,
any command or service that requested device(s) be taken offline or
unloaded, including VARY OFFLINE or UNLOAD commands or programs that
call the IEEVARYD service, may be left waiting indefinitely. It may
be necessary to use the CMDS ABEND command to ABEND any VARY command
or UNLOAD command that appears to be hung, or to CANCEL any job that
may have invoked the IEEVARYD service that appears to be hung.
For
reason code 229, message IEF707I might be issued to indicate the number
of the device that cannot be found. If IEF707I is issued, see the
Operator Response and System Programmer Response for that message.
Source
z/OS MVS System Codes
Copyright IBM Corporation 1990, 2014