Explanation
JES3 may have issued one of the following messages
because of the indicated error:
- IAT1601
- The user is trying to perform I/O to a data set that is closed.
An
incorrect IATYDAT was found on the data buffer block (DAT) queue.
- IAT1602
- One of the following control blocks either (1) could not be validated
or (2) contains incorrect data: IATYDAT, IATYDMC, IATYDSB or IATYDSS.
- IAT1603
- A JES3 module passed, as a parameter to IATDMEB, a code that requested
an incorrect data management function.
- IAT1604
- A start I/O operation in the user's storage returned an error
code.
- IAT1605
- A start I/O operation in the user's storage returned an error
code.
- IAT1606
- IATDMEB found an incorrect unprotected buffer (IATYDAT) address
or the associated IATYDMC address was incorrect.
- IAT1607
- IATDMEB could not allocate an unprotected buffer.
- IAT1609
- One of the following occurred:
- When module IATDMEB or IATSIAD attempted to set up a data management
WAIT, the module found a data management function already waiting.
- When module IATDMEB or IATSIAD attempted to set up a subsystem
interface WAIT, the module found a subsystem function already waiting.
- IAT1610
- During ENDREQ processing, a request for macro IATYJDS failed.
- IAT1611
- The JES3 SSVT was either (1) incorrect or (2) could not be found.
- IAT1612
- The SYSOUT class to be allocated is not alphanumeric.
- IAT1614
- A failure occurred while processing a started task or TSO logon
internal reader data set.
- IAT1803
- An attempt to move data from a JES3 protected buffer in the JES3
auxiliary address space to a user storage unprotected buffer failed.
- IAT6700
- During deallocation, when attempting to update the JDSENTRY, the
module could not find a job data set (JDS) entry.
- IAT6703
- When the module attempted communication, an error that disrupted
operations occurred in the global processor.
- IAT6704
- OPEN could not allocate a user address space buffer to a data
set.
- IAT6707
- At deallocation of the external writer data set, the module could
not find an output scheduling element (OSE).
- IAT6708
- A permanent I/O error occurred on an output data set.
- IAT6711
- A SSISERV macro sent incorrect data to the global processor; the
request could not be serviced.
- IAT6309
- A failure has occurred during an MVS™ LOAD
or BLDL of a JES3 input service module.
If none of these messages appear, JES3 found
an incorrect IFGACB, IATYDSS, or IATYDSB control block or received
an error return code as a result of either a SJFREQ request or a
multi-system core buffer request.
System action
Depending on the error, the system ends either
the job step or the user address space.
System programmer response
If messages accompany this abend,
register 3 in the dump points to a copy of the data set status block
(DSS). A hexadecimal reason code explains the error. Use this reason
code to determine the cause of the error.
If the reason codes report errors from IATDMCB, requestors
of multi-system core buffer information will experience a delay in
getting a response. Following the delay, the information reported
will include only the records that have been written to spool. The
core buffer information will not be reported. To repair this processing,
request an IPL of the main that received the 1FB Abend.- Code
- Explanation
- 01
- Module IATDMEB, while performing verification of the subsystem
vector table (SVT), has found that the SVT block ID (SVTID) is incorrect.
- 03
- Module IATDMEB contains undefined function code.
- 04
- Module IATDMEB received an error code from the IATXSIO macro while
processing the GET routine.
- 05
- Module IATDMEB3 received an error code
from the IATXSIO macro while processing the data management point
routine.
- 06
- Module IATDMEB3 received an error code
from the IATXSIO macro while processing the SSI point routine.
- 07
- Module IATDMEB received an error code from the IATXSIO macro while
processing the GET routine.
- 08
- Module IATDMEB received an error code from the IATXSIO macro while
processing the PUT-Update routine.
- 09
- Module IATDMEB contains a dynamic address translation (DAT) validation
error. The DAT address is out of range (too low).
- 0A
- Module IATDMEB contains a dynamic address translation (DAT) validation
error. The DAT address is out of range (too high).
- 0B
- Module IATDMEBS received an error code
from the IATXSIO macro while reading a previous
record.
- 0C
- Module IATDMEB3 received a busy return
from macro IATXUBAL while processing the buffer checkpoint routine.
- 0D
- Module IATDMEBS received an error return
from macro IATXUBAL while processing a POINT request.
- 0E
- Module IATDMEBS received an error code
from the IATXSIO macro while attempting to read
ahead.
- 0F
- Module IATDMEBS received an error code
from the IATXSIO macro while processing a write
error retry.
- 10
- Module IATDMEBS received an error code
from the IATXSIO macro while processing a required
read.
- 11
- Module IATDMEBS received a busy return
from macro IATXUBAL while processing a get-update
point I/O termination.
- 12
- Module IATDMEB3 detected a CLOSE serialization
failure in the ENDREQ routine.
- 13
- Module IATDMEBS received a busy return
form macro IATXUBAL while processing a single record
request.
- 14
- Module IATDMEB received an UBUFF validation error while processing.
DMC block ID (DMCID) is incorrect.
- 15
- Module IATDMEB found the data management wait already outstanding.
- 16
- Module IATDMEB found the SSI wait already outstanding.
- 17
- Module IATDMEB received an error return from macro IATXSIO.
- 18
- Module IATDMEB received an DMC validation error. The DMC block
ID (DMCID) is incorrect.
- 19
- Module IATDMEB received an DMC validation error. DMC address is
out of range (too low).
- 1A
- Module IATDMEB received an DMC validation error. DMC address is
out of range (too high).
- 1B
- Module IATDMEB received an DAT validation error. DAT block ID
(DATID) is incorrect.
- 1C
- Module IATDMEB received an DAT validation error. DAT address is
out of range (too low).
- 1D
- Module IATDMEB received an DAT validation error. DAT address is
out of range (too high).
- 1E
- Module IATDMEB3 received a GETMAIN failure
while processing ENDREQ routine.
- 1F
- Module IATSICC received a permanent I/O error writing last buffer.
- 20
- Module IATDMFR received a failure in IATDMEB channel end routine
(IATDMEBS).
- 21
- Module IATDMEBS received a cross memory
move (IATXMVXM) error return.
- 22
- Module IATDMEB detected the data set status block id (DSSID) is
not valid upon entry.
- 23
- Module IATDMEB received an DSS validation error. The SVT pointer
(DSSSSVT) is incorrect.
- 24
- Module IATDMEB received an DSB validation error. DSB block ID
(DSBID) is incorrect.
- 25
- Module IATDMEBS received an error return
from UBUFF while processing the allocation routine.
- 26
- Module IATDMEBS received an error return
from IATXSIO while redriving the I/O for a DMC.
- 27
- Module IATDMEB3 could not free user memory
buffers. The DSS or DSB failed validation in module IATDMUB.
- 28
- Module IATDMEB2 or IATDMEB3 received an
DAT validation error. DAT address is out of range (too low).
- 29
- ModuleIATDMEB2 or IATDMEB3 received an
DAT validation error. DAT address is out of range (too high).
- 2A
- Module IATDMEB3 received an SSISERV error
while processing ENDREQ routine. The JIB block ID incorrect.
- 2B
- Module IATDMEB3 received an error in JDS
access while processing ENDREQ routine.
- 2C
- Module IATDMEB received an DMC validation error. DMC address is
out of range (too low).
- 2D
- Module IATDMEB received an DMC validation error. DMC address is
out of range (too high).
- 2E
- Module IATDMEBS received an DAT validation
error. DAT address is out of range (too low).
- 2F
- Module IATDMEBS received an DAT validation
error. DAT address is out of range (too high).
- 30
- Module IATDMEB received an error return from spool record allocation
(IATDMDKR).
- 31
- Module IATDMEB3 received an DAT validation
error. DAT address out of range (too low).
- 32
- Module IATDMEB3 received an DAT validation
error. DAT address out of range (too high).
- 33
- Module IATDMEB3 received an DAT validation
error. DAT block ID (DATID) is incorrect.
- 34
- Module IATDMEB3 received an DAT validation
error. DAT address out of range (too low).
- 35
- Module IATDMEB3 received an DAT validation
error. DAT address out of range (too high).
- 36
- Module IATDMEB3 received an DAT validation
error. DAT block ID (DATID) is incorrect.
- 37
- Module IATDMEB3 received an DAT validation
error. DAT address is out of range (too low).
- 38
- Module IATDMEB3 received an DAT validation
error. DAT address is out of range (too high).
- 39
- Module IATDMEB3 received an DAT validation
error. DAT block ID (DATID) is incorrect.
- 3A
- Module IATDMEBS received an error while
adding a data set status block (DSS) to the record allocation block
(RAB) queue during write error recovery.
- 3B
- Module IATDMEBS received an error while
adding a data set status block (DSS) to the record allocation block
(RAB) queue after IATXSIO processing.
- 3C
- Module IATDMEB received an error while
resetting a data set status block (DSS).
- 3D
- Module IATDMEB received an error while adding the data set status
block (DSS) to the record allocation block (RAB) queue.
- 3E
- DSB validation failed.
- 3F
- Module IATDMEB detected that an RPL was not provided upon entry
from IATDMDM.
- 40
- Module IATDMDM received an incorrect ACB on entry.
- 41
- Module IATDMDM received an DSB validation error. DSB block ID
(DSBID) incorrect.
- 42
- Module IATDMDM received an DSS validation error. DSS block ID
(DSSID) incorrect.
- 43
- Module IATDMDM received an incorrect DAT address while processing
the PUT routine.
- 44
- Module IATDMDM received an incorrect buffer point while processing
the PUT routine.
- 45
- Module IATDMDM found that no room remains in the buffer while
processing the PUT routine.
- 46
- Module IATDMDM received an DAT validation error. DAT address out
of range (too low).
- 47
- Module IATDMDM received an DAT validation error. DAT address out
of range (too high).
- 48
- Module IATDMDM received an unsuccessful GETMAIN while processing
the ENDREQ routine.
- 49
- Module IATDMDM received an input service error while processing
the ENDREQ routine.
- 4A
- Module IATDMDM did not receive the JOBID from input service while
processing the ENDREQ routine.
- 4B
- Module IATDMDM received an error re-opening INTRDR data set while
processing the PUT routine.
- 4C
- Module IATDMDM detected serialization failure in the PUT routine.
- 4D
- GETMAIN failed while processing a started task or TSO logon request.
- 4E
- Module IATDMDM detected an error while processing a SYSIN in-stream
data set.
- 4F
- Module IATDMDM received a negative record number generated for
RPLRBAR.
- 50
- Module IATSIAD received an SSISERV error return.
- 51
- Module IATSIAD received an SSISERV error return.
- 52
- Module IATSIAD received an SSISERV error return. The job is marked
delete only.
- 53
- Module IATSIAD received a catastrophic error from SSISERV.
- 54
- Module IATSIAD detected bad data was sent during SSISERV processing.
- 55
- Module IATSIAD received an error during PSO unallocation from
SSISERV error return.
- 56
- Module IATSIAD received an SSISERV error return. There was no
job number available.
- 57
- Module IATSIAD received an SSISERV error return.
- 58
- Module IATSIAD received an SSISERV error return.
- 5A
- A JES3 module received an allocation request for a SYSOUT class
that is not A-Z or 0-9.
- 60
- Module IATSIOR detected an OPEN serialization failure.
- 61
- Module IATSIOR detected an OPEN serialization failure.
- 62
- Module IATSIOR found ORT not available.
- 63
- Module IATSIOR found ORT not available.
- 64
- Module IATSIOR received an error return from IATSIOD module.
- 65
- Module IATSIOR found the user writer name was not specified.
- 66
- Module IATSIOR received an SSISERV error return. The job was
marked delete-only.
- 67
- Module IATSIOR received a catastrophic error from SSISERV.
- 68
- Module IATSIOR did not find a job data set (JDS).
- 69
- Module IATSIOR received an SSISERV error return. There was no
job number available.
- 6A
- Module IATSIOR received a BUSY return from the buffer allocation
routine.
- 6B
- Module IATSIOR received an error while adding a data set status
block (DSS) to the record allocation block (RAB) queue after an error
during OPEN processing.
- 6C
- Module IATSIOR received an SSISERV error return. The job is marked
delete only.
- 6D
- Module IATSIOR detected an OPEN serialization failure.
- 6E
- Module IATSIOR detected an OSE buffer number overflow.
- 6F
- A JES3 module received a JDS pointer value that was zero during
DS OPEN processing.
- 70
- Module IATSICC received an SSISERV error return. The job was
marked delete-only.
- 71
- Module IATSICC received an SSISERV error return while processing
INTRDR job.
- 72
- Module IATSICC received a catastrophic error from SSISERV.
- 73
- Module IATSICC received an SSISERV error return. Bad data was
sent.
- 74
- Module IATSICC received an SSISERV error return. The job number
is not available.
- 75
- Module IATSICC detected a CLOSE serialization failure.
- 76
- Module IATSICC detected a PUT serialization failure.
- 79
- Module IATSICC detected an INTRDR serialization failure. The
DSBOCTCB lock was overlayed while processing the INTRDR close request.
- 80
- Module IATDMFR received a failure in module IATSIAD while processing
the IATSIADD routine.
- 81
- Module IATDMDK failed when adding a DSS to the PBUF wait queue.
- 82
- Module IATDMDK failed when adding a DSS to the SRB wait queue.
- 83
- Module IATDMDK failed when attempting to reset the DSS after it
was removed from the RAB wait queue.
- 84
- Module IATDMER failed when adding a DSS to the SRB wait queue.
- 85
- Module IATDMFR detected a recovery error or control block validation
error.
- 90
- Module IATDMDM received an error code from a STORAGE OBTAIN request.
- 91
- Module IATDMDM received an error code from a call to IATGRAS.
- 92
- Module IATDMDM received an error code from a call to IXZXIXSM.
SEGTYPE=FIRST was specified on the call.
- 93
- Module IATDMDM received an error code from a call to IXZXIXSM.
SEGTYPE=LAST was specified on the call.
- 94
- Module IATDMDM received an error code from a call to IXZXIXAC.
- 95
- Module IATDMDM received an error code from a STORAGE RELEASE request.
- 96
- Module IATDMDM found no output buffer or the buffer failed validation.
- 97
- Module IATDMDM detected a record size error.
- 98
- Module IATDMDM detected a record size error.
- 99
- Module IATDMDM detected a record size error.
- 9A
- Module IATDMDM detected a record size error.
- 9B
- Module IATDMDM detected a record size error.
- 9C
- Module IATDMDM detected a record size error.
- 9D
- Module IATDMDM detected a record size error.
- 9E
- Module IATDMDM detected a record size error.
- 9F
- Module IATDMDM detected a record size error.
- A0
- Module IATDMDS, while processing a chain of DMCs, found them
chained in a circular chain.
- A1
- Module IATDMDS, while in the Link-up routine, detected an error
in processing the Extent Busy queue.
- A8
- Module IATDMIT detected that the channel program for I/O request
was incomplete while the request complete normally.
- A9
- Module IATDMIT detected a failure when attempting to a DSS to
the SRB Wait Queue.
- AA
- Module IATDMIT detected a failure when attempting to reset a DSS
after it had been removed from the Protect Buffer (PBUF) Wait Queue.
- AB
- Module IATGRSP detected a failure when releasing the DSB spinoff
lock.
- AC
- Module IATGRSP detected a failure writing a buffer.
- AD
- Module IATGRSP detected a failure freeing unprotected buffers
(UBUFs).
- AE
- Module IATGRSP detected a failure obtaining UBUFs .
- AF
- Module IATGRSP detected a failure during a dataset point operation.
- B0
- Module IATGRSP detected a failure during spinoff processing.
- B1
- Module IATGRSP detected a failure trying to obtain the UBUF lock.
- B2
- Module IATGRSP detected a failure when freeing the UBUF lock.
- C0
- Module IATDMEB3 detected an error in the
EBR000 routine. The EBGETUBF service returned +0.
- C2
- Module IATDMEBS detected an error. The
EBGETUBF returned +0.
- C4
- Module IATDMEB2 detected an error when
freeing the buffer pointed to by DSBLSTBF.
- C5
- Module IATDMEB3 detected an error in the
EBT000 routine. The EBGETUBF service returned +0.
- C7
- Module IATDMEB detected an error in the EBG000 routine. The read
buffers were not in a sequential order.
- D0
- Module IATDMEB3 or IATGRSP detected that
a job termination request was made before the data management request
was processed.
- D1
- Module IATDMEBS detected zero DATPREV when
searching backward during a POINT operation.
- D2
- Module IATDMEBS found the current UBUF
chained to the list of waiting buffers.
- D3
- The DMC failed validation in the GET routine of IATDMEB.
- D4
- Module IATDMEB was unable to allocate a buffer for a spool browse
GET.
- D5
- Module IATDMEB3 was unable to allocate
a buffer for a spool browse GET.
- D7
- Module IATDMEB detected that the next spool buffer was not sequential.
- D8
- Module IATDMEB2 attempted to free the top
DMC on the DSBBDMC chain.
- D9
- Module IATDMEB3 was unable to allocate
a buffer for a spool browse GET.
- DA
- Module IATDMEB was unable to allocate a buffer for a spool browse
GET.
- DB
- Module IATDMEB detected that no buffer existed on the DSBBDMC
queue.
- DC
- Module IATDMEB3 detected that no buffer
existed on the DSBBDMC queue.
- DE
- Module IATDMDM detected that the point failed for a Sysin control
record.
- DF
- Module IATDMEB3, the Data Management Point
routine, received an IATXSIO error return.
- E0
- Module IATDMEB3 was unable to allocate
a buffer for a spool browse GET.
- E1
- Module IATDMEB3 detected a JIB error while
processing a response from the global.
- E2
- Module IATDMEB3 detected that no CLST pointer existed after a
data set switch.
- E3
- Module IATDMEB task failed due to preceding buffer corruption
most likely caused by a preceding job failure.
- E4
- Module IATDMCB detected an error when receiving a message from
its mailbox.
- E5
- Module IATDMCB detected an error in the JESXCF message envelope
for a message received from the mailbox. The eye catcher is not correct.
- E6
- Module IATDMCB detected an error in the JESXCF message envelope
for a message received from the mailbox. The buffer provided to hold
a response is too small.
- E7
- Module IATDMCB detected an error when attempting to acknowledge
a request for multi-system core buffer data.
- E8
- Module IATDMEB3 was unable to allocate a buffer in the Data Management
Point routine.
- E9
- Module IATDMEB3 detected that no buffer existed on the DSBBDMC
queue.
Programmer response
If the problem occurred in an I/O operation,
correct any I/O errors in your program. Then rerun the job.
If
JES3 issued message IAT6309, correct the cause of the LOAD or BLDL
failure. Then rerun the job. Otherwise, notify your system programmer,
supplying a SYSABEND dump.
Source