just a random pick

JCL Abend code : S002

Very large record length/ wrong record length

With variable format files used for output. The record is larger than the track size. The record length is greater than allowed maximum 32,768 bytes. The wrong record length is being used on output. The 4-byte record length indicator (RDW) is wrong.

File doesnot possess the required directory blocks length or stated blocksize, could not be contained in one extent, or too many tracks specified for cylinder overflow,DCB had the wrong block size

IEHMOVE - attempt to rename data set when new name already exists

Check out IEC036I message for more details

For return code 2C, change the CYLOFL operand of the DCB macro instruction to reflect the correct number of tracks, or correct the DCB BLKSIZE.

Sub Response code

Sub response codeExplanation
04An Invalid record was encountered on a GET operation. The Length field of a Record Descriptor Word (RDW) for a variable length record specifies a value less than 4.
08An Invalid record was encountered on a PUT or WRITE operation. The record or block length plus the key length and required overhead add up to more than 32,767 bytes.
0C An Invalid record was encountered on a 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 Invalid record was encountered on a PUT operation; The dataset uses the track overflow feature.The RDW for a variable length record specifies a length greater than 32,752.
14An Invalid record was encountered on a PUT or WRITE operation. The record length is greater than the blocksize specified in the DCB.
18An Invalid record was encountered on a PUT operation; The dataset uses the variable record format. the length value of the RDW is either: less than 4, greater than 32,767, greater than the blocksize specified in the DCB, or less than 5 if ASA control characters are being used.
1C The Error occurred during the creation of a direct dataset. A WRITE macro was issued for a record larger than the track capacity, and the record format does not use the track overflow feature.
20The Error occurred during the creation of a direct dataset.A WRITE macro was issued causing a secondary extent to be obtained. The block will not fit on the amount of space allocated for the secondary extent.
24The Error occurred during the creation of a direct dataset. A WRITE macro was issued to write out a block larger than the primary extent on the preallocated dataset.This could also occur if allocation of the primary extent was non-contiguous and any of the secondary extents were smaller than the block.
28 The Error occurred during the creation of a direct dataset. During the execution of OPEN it was detected that the blocksize was larger than the primary extent.
2C The Error occurred while opening an ISAM dataset. Too many tracks were specified for cylinder overflow.
30one of the following is true: A READ was issued but the length to be read was zero. A QSAM PUT with move mode was issued for RDW=F, FB or but DCB LRECL contained a non-positive value.
34A READ macro was issued for an output-only DASD data set.
3C PDS member creation was prevented because the PDS already had the maximum number of members (2**19 - 2).
50Serialization of an internal sam control block (SACB) used FOPR processing has been violated.
54DEBCHK failure during PDS processing.
58An Internal SAM control block (SACB) used for processing PDSE requests is incorrect.
5C An Internal SAM control block (FRQ) used for queuing PDSE requests is incorrect.
60For BSAM, the read or write request could not be accepted because the value of NCP in the DCB had already been reached.
68Incorrect blocksize specified
6C Unable to create a PDSE member.
70Unable to update an Internal SAM control block (PACB) used for PDSE processing with information concerning the member being accessed.
74An Internal SAM control block (PACB) used for storing PDSE directory and member information is incorrect.
78Error return from IGWFMPCR when attempting to give control to a routine to process PDSE requests.
7C Point detected that information concerning the member being accessed is not found in the PACB.
80Point detected an error while attempting to synchronize data on output.
84Point detected an error while attempting to reconnect to a PDSE member for hold.
88Point detected an error while attempting to reconnect to a PDSE member for I/O.
8C Point detected an error while attempting to disconnect from a PDSE member.
90Point detected an error while attempting to connect to a PDSE member.
94Incorrect attempt to create a PDSE member since the maximum number of members have already been created.
98Unable 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 a PDSE directory. either: - write attempted to the directory of a PDSE. - read attempted to the directory of a PDSE and either the RECFM was not F with BLKSIZE>= 256 ==or== RECFM was not U with BLKSIZE >= 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 Maximum number of records in member has been exceeded.
AC Bad buffer format detected for variable length records. either: - RDW length is less than 4. - length of 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 in buffer.
B0 Either RECFM=F and DCBBLKSI does not equal DCBLRECL,or RECFM=FB and DCBBLKSI is not a multiple of DCBLRECL.

Suggestion / Complaint / Feedback