Datacom dynamic extend fails with a SE37-08 abend due to insufficient space on the volume.
The following errors can be seen in the dynamic extend:
DB01705I - DYNAMIC EXTEND START IXX999 TRK 1,487,550 PRD.IXX999
DB01709I - EXTEND SIZE IXX999 TRK 15,000 - DIRECTED - DIRECTED CYL 1,000
IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR 801
DATA SET PRD.IXX999
IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS (04034379) , 809
IEC032I E37-08,IFG0554P,DCOMPRD,DCOM,IXX999,19CB,DCI025,04034379, 810
ERROR DESCRIPTION: IEC032I
A multi-volume physical sequential data set was being written on DASD.
Space on next volume is needed. Either no space, or data set already
existed, or no space on the VTOC or VTOC index. See manual for more
END ERROR DESCRIPTION: IEC032I
DB01702I - DYNAMIC EXTEND OF AREA IXX999 HAS FAILED
The file may still be usable by the MUF but will issue the following message:
IEC145I 413-1C,IFG0193A,DCOMPRD,DCOM,IXX999,1C60,DCI000, 760
ERROR DESCRIPTION: IEC145I
An OPEN macro instruction was issued for a data set, but volume
sequence number on the associated DD statement was greater than the
number of volumes containing the data set.
END ERROR DESCRIPTION: IEC145I
Any further attempt to EXTEND the file again will corrupt the file further and make it unusable.
A second EXTEND will receive message DB01405I - DATA SET VOLUME IGNORED, NOT CHAINED and incorrectly calculate the number of tracks on the file.
After this any attempt to use the file will fail with return codes 13 (05) or 94 (86).
Release : 15.1
Component : DATACOM/DB
This is caused by a z/OS problem with managing the VTOC. The error occurs during IBM EOV processing. When an ABEND E37-08 occurs the DS1IND80 bit (last volume indicator) is being turned off in the DSCB on the last volume in the VTOC. This causes the DEBEOF flag (X'20'– end of file (EOF) encountered ) not to be set in the DEB.
To resolve the problem you will need to restore the file from a backup.
This can be done using z/OS system utilities if it was backed up that way.
Otherwise use Datacom utilities:
Currently, there is no IBM PTF to fix the problem.
IBM FIN APAR OA60902 has been created for this problem and will be fixed in the next product release of DFP End-Of-Volume code.