It's in the messages manual for IEC032I for E37 abends. 08 A multi-volume physical sequential data set was being written on a direct access device. All space was filled on the volume, and an attempt was made to obtain space on the next specified volume. Either the space was not available on that volume, the data set already existed on that volume, or there is no space available in the VTOC or the VTOC index. The message contains the volume serial number of the last volume used.
Lennie -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Peter Sent: 21 December 2025 14:12 To: [email protected] Subject: Re: Multi volume dataset copy Thanks all for the ideas and here is what I did and it was successful with copy Connected productions Test database to the test LPARs mcat. So allocated the empty PS LARGE dataset on 5 mod-54 volumes then ran IDCAMS repro and it worked. Well I was only thinking why the empty dataset created 9 mod-27 couldn't span over 6 volumes. Is there a difference between NON SMS LARGE PS dataset using batch vs ISPF 3 2 ? Initially when we allocate multivolume NON-SMS, we can view the dataset on first volume and once the first volumes fills then automatically the dataset allocates on second volume and until 6 volumes. But after 6th volume it fails with E37-08. Well I had a tight deadline of testing the database on test lpar and so got mod-54 to help and it worked. However I will try to find the reason for the volume count for NON-SMS mod-27 multivolume Thanks again On Sun, 21 Dec 2025, 16:05 Jousma, David, < [email protected]> wrote: > If it is just a PS file, allocated the new empty one on the other load > and just ftp it over there and you are finished. > > > _______________________________ > > Dave Jousma > > Vice President | Director, Platform Engineering > > Fifth Third Bank | 1830 East Paris Ave, SE | Grand Rapids, MI 49546 > <https://www.google.com/maps/search/1830+East+Paris+Ave,+SE+%7C+Grand+ > Rapids,+MI+49546?entry=gmail&source=g> > > ________________________________ > From: IBM Mainframe Discussion List <[email protected]> on > behalf of Peter <[email protected]> > Sent: Saturday, December 20, 2025 10:27:16 PM > To: [email protected] <[email protected]> > Subject: Re: Multi volume dataset copy > > > > > I did pre allocate a empty dataset on 9 volume but it failed after 6th > volume > > On Sun, 21 Dec 2025, 00:02 Radoslaw Skorupka, < > [email protected]> wrote: > > > Yes, of course. The limit is 59 for both: SMS and non-SMS datasets. > > However... do you have those volumes? > > First try to use IEFBR14 and allocate empty dataset on target volumes. > > Then you can use it for copy operation. > > > > -- > > Radoslaw Skorupka > > Lodz, Poland > > > > > > > > W dniu 20.12.2025 o 19:48, Peter pisze: > > > Hello > > > > > > A general question > > > > > > A non-sms dataset cannot span over volume count of more than 6 ? > > > > > > Cause I was able to allocate using ISPF 3.2 dataset on 11 mod27 > > > but the > > job > > > failed with the below error spanning not more than 6 volumes. > > > > > > I used IDCAMS repro to copy > > > > > > IEC032I E37-08 , IFG0554P. > > > > > > > > > > > > > > > > > > On Sat, 20 Dec 2025, 20:24 Radoslaw Skorupka, < > > > [email protected]> wrote: > > > > > >> W dniu 20.12.2025 o 01:08, Michael Watkins pisze: > > >>> From memory: No z/OS dataset can span more than 59 volumes. 16 > > extents > > >> can reside on each volume unless the data set is SMS-managed and > > >> the DSNTYPE is defined as 'EXTENDED', in which case up to 123 > > >> extents can reside on each volume. However, unless Extent > > >> Constraint Removal is specified as 'Y' in the DATACLAS, the total > > >> number of extents spanning > > all > > >> volumes is 255. > > >> > > >> Not exactly. > > >> Datasets are limited to 16 or 123 extents per volume. > > >> Some datasets can be multi-volume, other datasets are > > >> single-volume only. Maximum is 59 volumes (on DASD). > > >> Some datasets are limited to 64k TRK per volume, other are not > limited. > > >> The limits depends on dataset organisation and type. Examples: > > >> basic PS - 16 ext, 59 vol, 64k TRK large PS - 16 ext, 59 vol, 16M > > >> TRK extended format PS - 123 ext, 59 vol, no known limit for > > >> size. > > >> PDSE - 123 ext, 1 vol, no practical limit for size. > > >> VSAM - 123 ext, 59 vol, 4GB limit size (with exception for ZFS) > > >> ext-fmt & ext-addr VSAM - 123 ext, 59 vol, 4G CI size (up to 128 > > >> TB), other interesting features. > > >> > > >> (the above is not full list) > > >> > > >> SMS is pre-req for extended format, however as we can see it is > > >> not pre-req for 123 extents. > > >> Extent constraint removal is for VSAM only and for VSAM-specific > > >> limit > > >> (255 ext per dataset or rather component). > > >> > > >> > > >> -- > > >> Radoslaw Skorupka > > >> Lodz, Poland > > >> > > >> ----------------------------------------------------------------- > > >> ----- For IBM-MAIN subscribe / signoff / archive access > > >> instructions, send email to [email protected] with the > > >> message: INFO > IBM-MAIN > > >> > > > ------------------------------------------------------------------ > > > ---- For IBM-MAIN subscribe / signoff / archive access > > > instructions, send email to [email protected] with the > > > message: INFO IBM-MAIN > > > > -------------------------------------------------------------------- > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO > > IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > > This e-mail transmission contains information that is confidential and may > be privileged. It is intended only for the addressee(s) named above. If > you receive this e-mail in error, please do not read, copy or > disseminate it in any manner. If you are not the intended recipient, > any disclosure, copying, distribution or use of the contents of this > information is prohibited. Please reply to the message immediately by > informing the sender that the message was misdirected. After replying, > please erase it from your computer system. Your assistance in correcting this > error is appreciated. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
