The following JCL produced the error. Attempting to backup 25,000 CYLS of data to 3 - empty MOD9's. When I checked the volumes after the abend I noted that the file (TSH.CAPUNLD3) allocated 3300 CYLS on each of the volumes indicated in the TAPE DD statement. There are approx. 6708 cyl left on each of the volumes.
None of the situations indicated as a potential cause of this abend in the system messages manual seem to apply.
The PRODxx volumes are a mix of MOD3 and MOD9. The volumes indicated in the TAPE DD are not SMS controlled.
I'm not sure if this is a JCL or DFDSS issue (or a combination of both).
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
Dick is not mis-remembering; as you've specified the data set you are limited to just over 4000 cylinders per pack. There is a DSNTYPE=LARGE JCL parameter which allows you to use more than 65535 tracks per volume. But since we can see you didn't specify DSNTYPE=LARGE in your JCL, the 65535 tracks per volume limit applies.
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
Quote:
The 3390 MOD9 contains the equivalent of 3 3390 mod3's. The total free cyls on each volume prior to execution is 10008.
The dataset being created is not SMS managed.
And none of what you're saying here changes the fact that a data set is limited to 65535 tracks on a single volume, absent the DSNTYPE=LARGE specification in JCL. Your backup JCL must be changed to include DSNTYPE=LARGE for the DD name, or you must change the backup JCL to point to six 3390 disk packs instead of 3 to get the amount of space you need -- but one way or the other, the JCL must be changed to fix this error.
