IEC036I 002-`rc`,`mod`, `jjj`,`sss`,`ddname`[-#], [`dev`,`ser`,`dsname`(`member`)]

Explanation
The error occurred while the control program was
processing a sequential data set with BSAM or QSAM, or creating a
direct data set.
In the message text: rc
Associates this message with system completion code 002 and with
the return code.
jjj
The job name.
sss
The step name.
ddname[-#]
DDname (followed by a concatenation number if it is part of a
concatenation and not the first DD statement in the concatenation).
dev
The device number.
ser
The volume serial number.
mod
The name of the module in which the error occurred.
dsname(member)
The data set name. Member name if specified.

The unit address, volume serial number, and
data set name do not appear in the message text when it applies to
a subsystem data set, such as SYSIN or SYSOUT.
The explanation
for the hex return code is as follows: Return Code
Explanation
04
One of the following occurred: An incorrect record was encountered during a QSAM GET operation.
The data set consists of variable format records. The length field
in the record descriptor word (RDW) is incorrect for one of the following
reasons: The RDW specifies a length less than 4.
The RDW specifies a length greater than the DCBLRECL value that
was specified when the data set was opened.  DCBLRECL is the logical
record length (LRECL) in the data control block (DCB).

QSAM tried to read segments of variable spanned records that are
not in proper sequence.
LRECL is not large enough.
The record area in QSAM locate mode is too small to contain a
logical record from a spanned-format data set.
The BDW contained a length greater than the block size specified
in the data control block (DCB).

05
The file mark at the end of a PDS member is missing. The member
is at        the end of the data set.
08
One of the following is true: An incorrect record was encountered on a QSAM or BSAM PUT or WRITE
operation.  If the large block interface is not being used, or output
is not to a magnetic tape device, then the record or block length
plus the key length and required overhead add up to more than 32,767
bytes. If the large block interface is being used and output is to
a magnetic tape device, then the block length is greater than 65,535
bytes and greater than the block size specified when the DCB was opened.
The data consists of spanned format records, and the RDW, SDW,
or BDW length field, being translated to an ISO/ANSI format, exceeds
the length field capacity (9999) of the ISO/ANSI format RCW, SCW,
or block prefix.

0C
An incorrect record was encountered on a QSAM or BSAM PUT or WRITE
operation.  The record or block length plus the key length and required
overhead is greater than the DASD track capacity.
10
An incorrect record was encountered on a QSAM PUT operation; the
data set uses the track overflow feature. The record descriptor word
(RDW) for a variable length record specifies a length greater than
32,752.
14
An incorrect record was encountered on a QSAM PUT or WRITE operation.
The record length is greater than the block size specified in the
DCB.
18
An incorrect record was encountered on a QSAM PUT operation; the
data set uses the variable record format. The value in the length
of the record descriptor word (RDW) is incorrect for one of the following
reasons: It is greater than 32,767, or greater than the block size specified
in the DCB.
It is less than 4, or less than 5 if ASA or machine control characters
are used.
It specifies a value greater than the DCBLRECL value (maximum
record size) that was specified when the data set was opened.

1C
The error occurred during the creation of a direct data set. A
WRITE macro instruction was issued for a record larger than the track
capacity. Return code 1C also occurs when a DCB, LRECL, BLKSIZE, RECFM,
or KEYLEN parameter is missing.
20
The error occurred during the creation of a direct data set. A
WRITE macro instruction was issued causing a secondary extent to be
obtained.  The block will not fit on the amount of space allocated
for the secondary extent.
24
The error occurred during the creation of a direct data set. A
WRITE macro instruction was issued to write out a block larger than
the primary extent on the preallocated data set. This could also occur
if allocation of the primary extent was split and any of the secondary
extents were smaller than the block.
28
The error occurred during the creation of a direct data set. During
the processing of OPEN it was detected that the block size was larger
than the primary extent.
2C
The file is a z/OS UNIX file. A POINT macro was issued to position
a block other than the first block, but this is not allowed when FILEDATA=BINARY
is in effect and the record format is variable or undefined.
30
One of the following is true: A READ macro was issued, but the length calculated to be read
was zero.
A PUT macro using move mode was issued for a format ‘F’, ‘FB’,
or ‘U’ QSAM data set, but the DCBLRECL field contained
zero or a negative value.

38
Either a READ macro was issued for a DASD data set that was open
for output only, or a WRITE macro was issued for a DASD data set that
was open for input only.
40
While processing a data conversion request for an ISO/ANSI Version
4 tape, an internal SAM data conversion control block (SDC) was found
to be not valid.
41
While processing a data conversion request for an ISO/ANSI Version
4 tape, it was detected that the key of the request was different
than the key of the task.  This is not supported.
42
While processing a data conversion request for an ISO/ANSI Version
4 tape, an invalid user record length was detected.
43
While processing a data conversion request for an ISO/ANSI Version
4 tape, an error was returned from the system services used to perform
the data conversion.
44
While processing a data conversion request for an ISO/ANSI Version
4 tape, an internal SAM data conversion control block (SDC) was found
to contain a zero conversion token.
50
Serialization of an internal SAM control block has been violated.
 (For PDSE processing, it is the SACB.  For extended format data set
processing, it is the SSCB.)
54
DEBCHK failed.  The DEBCHK was issued while attempting to process
a request for a PDSE or extended format data set.
58
An internal SAM control block contains incorrect information.
(For PDSE processing, it is the SACB.  For extended format data set
processing, it is the SSCB.)
5C
An internal SAM control block used for queueing requests contains
incorrect information.  (For PDSE processing, it is the FRQ.  For
extended format data set processing, it is the SAQ or SRQ).
60
A non-zero keylength specified in the DCB on output for a PDSE
member or an extended format data set.
64
For BSAM, the READ or WRITE request could not be accepted because
the value specified in the DCB for NCP had been exceeded.
65
Either the DECB was overlaid or an internal BSAM or BPAM control
block was overlaid.  This might be due to the number of READ or WRITE
macros that have not had a corresponding CHECK macro issued exceeding
the NCP value specified in the DCB.
68
Incorrect block size specified in the DCB for a PDSE or an extended
format data set.
6C
Unable to create a PDSE member.
70
Unable to update an internal SAM control block (PACB) used for
PDSE processing with information concerning a member being accessed.
74
An internal SAM control block (PACB) used for storing PDSE directory
and member information is incorrect.
78
Error return from IGWFMPCR when attempting to give control to
a routine to process a request for a PDSE or extended format data
set.
7C
POINT detected that information concerning the member being accessed
is not found in the PACB.
80
POINT detected an error while attempting to synchronize data on
output.
84
POINT detected an error while attempting to reconnect to a PDSE
member for hold.
88
POINT detected an error while attempting to reconnect to a PDSE
member for I/O.
89
JCDM would not upgrade a connection for hold to input or output.
This is likely because it is connected to the directory for EXECUTE.
This would be due to one of the data sets in the concatenation being
RACF EXECUTE only.
8A
A POINT macro instruction issued against a UNIX directory in a
BPAM concatenation failed because the user had insufficient UNIX permissions
to access the file.
8C
POINT detected an error while attempting to disconnect from a
PDSE member.
90
POINT detected an error while attempting to connect to a PDSE
member.
94
A write would have had to create another member in a PDSE which
already contained the maximum allowable number of members. The limit
is 522,239 members.
98
Unable to complete a WRITE request issued within a PDSE member.
9C
Incorrect update WRITE detected. All outstanding READS had not
been CHECKed prior to the WRITE.
A0
Incorrect attempt to access the directory of a PDSE. Either: WRITE attempted to the directory of a PDSE.
READ attempted to the directory of a PDSE and either RECFM was
not F with a block size greater or equal to 256, or RECFM was not
U with a block size greater or equal to 256.

A4
Unable to complete the READ against the PDSE directory due to
an error return code from an SMS service used to obtain directory
information.
A8
One of the following: Maximum number of records in PDSE member has been exceeded.
Maximum number of blocks allowed in an extended format data set
has been exceeded.
A NOTE macro was issued for a PDSE data member,
but the record is more than 15,728,639 records into the member and
BLOCKTOKENSIZE=LARGE was not specified for the PDSE when it was opened.
 NOTE could not return a valid value

AC
Bad buffer format detected for variable length records. Either: The program attempted to WRITE an extended format BDW, but the
output device is not a magnetic tape, or the large block interface
is not being used.
RDW length is less than 4.
Length of a spanned record is greater than 32760.
The sum of the lengths in the RDWs plus 4 does not equal the length
specified in the BDW.
RECFM does not specify blocked but more than 1 RDW was found in
the buffer.

B0
Either RECFM = F and DCBBLKSI does not equal DCBLRECL, or RECFM
= FB and DCBBLKSI is not a multiple of DCBLRECL. Note that since
concatenated data sets can have different block sizes, and in most
cases the BLKSIZE the system will use for the entire concatenation
is the largest one in the concatenation, this block size can cause
invalid attribute combinations when combined with the attributes (e.g.,
RECFM or LRECL) obtained from the first data set in the concatenation.
B4
Unable to create a system buffer required for PDSE processing.
B8
Unable to obtain or release a lock required for processing a PDSE
directory.
BC
A sequential compressed format data set was opened for BSAM POINT
processing.  However, control information within the data set required
by POINT was found to be invalid.  The data set should be copied (via
REPRO, GENER or etc.).  After being copied, the resulting data set
should no longer have a problem with POINT processing.  ISPF COPY
3.3 cannot be used to copy the data set as it invokes POINT processing.
C0
Invalid attempt to read program object member of PDSE due to one
of the following reasons: not OPEN for input
not RECFM = U or F(B)
DCBBLKSI not a 4 KB multiple

C8
Error return from a system service while reading a directory of
a PDSE containing program objects.
CC
Invalid attempt to create a data member in a PDSE already containing
program object members. One PDSE cannot contain both program object
members and data members.
D0
Access to PDSE program object is denied.
D4
One of the following invalid combinations was specified in the
DCB for a PDSE: DCBBLKSI=0 or LRECL=0 and RECFM = FB or RECFM = U
DCBBLKSI=0 and RECFM = VB

D8
An error was returned from a system service used to initialize
system control blocks required for processing an extended format data
set.
DC
An error was returned from a system service used to process I/O
requests for an extended format data set.
DE
SF64 or SF64P was coded on the READ or WRITE macro but fixing
or unfixing a 64-bit data area failed.
E0
During the execution of a READ or WRITE macro instruction for
an extended format data set, it was detected that a POINT had been
issued before ensuring that all outstanding I/O had completed.
E1
One of the following situations occurred while processing a tailored
compressed data set on output:An error was encountered while writing a tailored dictionary to
a compressed format data set.
An invalid situation was detected in tailored dictionary processing.
This could be the result of a previous cancel or time-out situation
which occured while processing the sampling buffers. Or, this could
be the result when the tailored compressed data set was opened with
the INOUT option and an output operation was attempted without a preceding
input operation.

E2
An error was encountered while reading a tailored dictionary from
a compressed format data set.
E3
An invalid dictionary token for a tailored compressed format data
set was encountered.
E4
Error attempting to access catalog while processing a data set
in the compressed format.
E5
An invalid tailored dictionary was found within a compressed format
data set.
E6
An error was encountered from Compression Services while validating
a tailored dictionary for a compressed format data set.
E7
A serialization problem was detected within an internal SAM control
block (SAQ) which prevented further compression of user blocks for
a compressed format data set being created with tailored compression.
E8
Error return code from Compression Services COMPRESS/DECOMPRESS.
E9
An error was encountered in a routine (IGG019VX) while attempting
to compress a user block for a compressed format data set using tailored
compression. The user IOB was marked in error.
EA
An error return code was returned from a routine (IGG019VX) while
attempting to compress a user block for a compressed format data set
using tailored compression.
EB
While attempting to store a dictionary token in the catalog for
a compressed format data set being created with tailored compression,
it was discovered that a dictionary token had been stored in the catalog
since the time this DCB was opened. This implies that more than one
DCB was writing to this data set concurrently.
EC
An invalid compressed format physical block (CI) encountered on
output with BSAM/QSAM.
ED
An error was encountered while writing a tailored dictionary to
a compressed format data set. The dictionary is allowed only on the
first volume, and there was insufficient space on the first volume
to write the dictionary.
EE
READ or WRITE macro coded with SF64 or SF64P but data
set is compressed format or is not extended format.This failure
might be caused by a READ macro that was not coded correctly for BSAM
or BPAM.  An example is coding a BDAM READ macro with the DI option.

EF
An I/O error occurred while writing shadow buffers.
F0
Compressed record found in data set but the dictionary token in
the catalog is not valid.
F1
Large block interface is being used, and one of the following
occurred: RECFM = U, but READ or WRITE macro does not specify 'S'.
RECFM = D, but WRITE macro does not specify 'S'.

F4
EOV detected a bad return code from a system service used to calculate
the high allocated RBN when externing to a new volume of an extended
format data set.
F8
Autodata area passed to IGG019VX from IGG019V7 is already in use.
FC
Autodata area passed to IGG019VX from IGG019V9 is already in use.

System action
Pertinent control blocks are written to the GTF
trace data set as follows: Code
Trace Data
04
DCB, IOB, or ICB seek field, current logical record (maximum,
88 bytes).
08,10,14
DCB, DECB (if BSAM), current block (maximum, 88 bytes).
0C,1C
DCB, DECB (if BSAM), current block (maximum, 88 bytes), track
capacity.
18
DCB and the current logical record (maximum, 88 bytes).
20,24
DCB, DECB, current block (maximum, 88 bytes), track capacity,
current DEB extent.
28
DCB, DSCB.
30, DE, EE
DCB.
38
DCB and the JFCBDSNM field of the JFCB.

The user's DCB ABEND exit routine is taken if
one is provided, except for return code ED.

System programmer response
If the error recurs and the program
is not in error, look at the messages in the job log for more information.
Search problem reporting data bases for a fix for the problem. If
no fix exists, contact the IBM® Support
Center. Provide the JCL and the program listing for the job.

Programmer response
Probable user error.
If rc is 04 or
18, ensure that the DCBLRECL value specified includes the maximum
data length plus 4 bytes for the RDW.
If rc is 08, 10, or 14,
verify that the record size passed to the access method is correct.
If
rc is 14, if necessary, increase the block size to accommodate the
largest logical record.
If rc is 0C or 1C, use a smaller block
size, or a device with a greater track capacity.
If rc is 20,
24, or 28, allocate a larger primary or secondary extent, specify
a smaller block size, or use a device with greater track capacity.
 If the error occurred because the primary allocation was fragmented
into a number of extents, specify the CONTIG subparameter on the SPACE
parameter.
If rc is 2C, do not issue the POINT macro for a binary
EOF with RECFM=V(B(S)) or RECFM=U specified in the DCB.
If rc
is 30 and BSAM or BPAM is processing the data set, verify that the
BLKSIZE value in the DCB or DCBE is greater than zero or, for undefined
record format data sets without the 'S' parameter specified, that
the value of the DECLNGTH field in the DECB is greater than zero.
 If the program is not using LBI, large block interface, the BLKSIZE
field is DCBBLKSI.  If the program is using LBI, the BLKSIZE field
is DCBEBLKSI. The program is using LBI only if the DCBH0, DCBH1 and
DCBESLBI bits are on.
If rc is 30 and QSAM is processing the
data set, the LRECL value must be greater than zero and less than
or equal to 32760 for format ‘F’, ‘FB’, or ‘U’
data sets.
If rc is 38, open the data set for INPUT, OUTIN,
INOUT, or UPDATE.
If rc is 60, set DCBKEYLE to zero.
If
rc is 64 or 65, verify that the number of outstanding READs and WRITEs
issued prior to a CHECK does not exceed the value specified in DCBNCP.
If
rc is 68 and a WRITE (BSAM) or an OPEN with DISP=MOD (QSAM) is issued,
verify that the value for BLKSI (or in DECLNGTH if RECFM=U and BSAM)
does not exceed the block size of the data set. For extended format
data sets, once the block size of the data set is determined, no larger
blocks can be added to the data set.  If the program is not using
LBI, large block interface, the BLKSIZE field is DCBBLKSI.  If the
program is using LBI, the BLKSIZE field is DCBEBLKSI.  The program
is using LBI only if the DCBH0, DCBH1 and DCBESLBI bits are on.
If
rc is 94, delete a member to allow the creation of another member
(even one with an existing name). The member name to be deleted must
be a primary member name, not an alias.
If rc is 9C, verify
that a CHECK has been issued for all outstanding READs prior to issuing
a WRITE.
If rc is AC and a WRITE (BSAM) is issued, verify that
the data in the block is correct.
If rc is DE, the 64-bit storage
must be obtained with the CONTROL=AUTH option of the IARV64 macro
or with the TYPE=FIXED option of the IARCP64 macro or with the IARST64
macro. 
If rc is ED, reallocate the data set and ensure that
the space is not released before writing to the data set. Make sure
partial release is not used prior to writing to the data set or allocate
the data set in cylinders.
If rc is EE, choose an extended format
data set that is not compressed format. If the failure is caused
by issuing a READ macro that is not coded correctly for BSAM or BPAM,
correct the READ macro coding.
Contact the system programmer
for the following return codes: 40, 43, 44, D8, DC, E4, E8, EC, F0,
F4, F8 and FC.
Correct the error and rerun the job step.

Source
DFSMSdfp

Module
ABEND 002-rc
Detecting modules
ABEND 002-rc
Detecting modules
ABEND 002-rc
Detecting modules

002-04
IGG019AE, IGG019AB, IGG019AD, IGG019BN, IGG019BO,
IGG019FB, IGG019FD, IGG019FF
002-D8	
IGG019VX
002-EA	
IGG019VT

002-0C
IGG019V9
002-DC	
IGG019VX
002-EB	
IGG019VT

002-2C
IGG019DN
002-DE	
IGG019V8, IGG019V9, IGG0201V
002-EC	
IGG019VX, IGG019V8

002-40
IGG019TQ
002-E0	
IGG019VX
002-ED	
IGG055V1

002-41
IGG019TQ
002-E1	
IGG019VT
002-EE	
IGG019BH, IGG019BA

002-42
IGG019TQ
002-E2	
IGG019VT, IGG0193V
002-EF	
IGG019VT

002-43
IGG019TQ
002-E3	
IGG019VT, IGG0193V
002-F0	
IGG019VX

002-44
IGG019TQ
002-E4	
IGG019VT, IGG019V7
002-F1	
IGG019BA, IGG019DK

002-45
IGG019BK
002-E5	
IGG019VT, IGG0193V
002-F4	
IGG055V1

002-50
IGG019V9
002-E6	
IGG019VT, IGG0193V
002-F8	
IGG019V7, IGG055V1

002-54	
IGG019VX
002-E7	
IGG019VT
002-FC	
IGG019V9

002-68	
IGG019V9
002-E8	
IGG019VX

002-A8	
IGG019V7
002-E9	
IGG019VT

Routing code
11

Descriptor code
6

ABEND 002-rc	Detecting modules	ABEND 002-rc	Detecting modules	ABEND 002-rc	Detecting modules
002-04	IGG019AE, IGG019AB, IGG019AD, IGG019BN, IGG019BO, IGG019FB, IGG019FD, IGG019FF	002-D8	IGG019VX	002-EA	IGG019VT
002-0C	IGG019V9	002-DC	IGG019VX	002-EB	IGG019VT
002-2C	IGG019DN	002-DE	IGG019V8, IGG019V9, IGG0201V	002-EC	IGG019VX, IGG019V8
002-40	IGG019TQ	002-E0	IGG019VX	002-ED	IGG055V1
002-41	IGG019TQ	002-E1	IGG019VT	002-EE	IGG019BH, IGG019BA
002-42	IGG019TQ	002-E2	IGG019VT, IGG0193V	002-EF	IGG019VT
002-43	IGG019TQ	002-E3	IGG019VT, IGG0193V	002-F0	IGG019VX
002-44	IGG019TQ	002-E4	IGG019VT, IGG019V7	002-F1	IGG019BA, IGG019DK
002-45	IGG019BK	002-E5	IGG019VT, IGG0193V	002-F4	IGG055V1
002-50	IGG019V9	002-E6	IGG019VT, IGG0193V	002-F8	IGG019V7, IGG055V1
002-54	IGG019VX	002-E7	IGG019VT	002-FC	IGG019V9
002-68	IGG019V9	002-E8	IGG019VX
002-A8	IGG019V7	002-E9	IGG019VT

IEC036I 002-rc,mod, jjj,sss,ddname[-#], [dev,ser,dsname(member)]

Explanation

System action

System programmer response

Programmer response

Source

Module

Routing code

Descriptor code

IEC036I 002-`rc`,`mod`, `jjj`,`sss`,`ddname`[-#], [`dev`,`ser`,`dsname`(`member`)]