The error occurred while the control program was processing a sequential data set with BSAM or QSAM, or creating a direct data set.
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.
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.
The user's DCB ABEND exit routine is taken if one is provided, except for return code ED.
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.
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.
DFSMSdfp
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 |
11
6