Possibly your output dataset is being assigned a DATACLAS which has a default allocation for UNIT=(SYSDA,2). Consider coding a UNIT= DD with additional volumes greater than 2. Of course, my suggestion warrants testing with your application before presuming multi-volume allocations are even supported.
Also, regarding DSNTYPE=LARGE (related to follow-on post responses), it's best not to assume any given sequential dataset is suitable candidate for DSNTYPE=LARGE. For example, SAS announced DSNTYPE=LARGE support but not yet supported with sequential-format SAS datasets, typically tape-based SAS files or backups. So it's unclear whether a SAS-generated tape/sequential backup copy (using SAS PROC COPY) will be suitable for a restore / recovery operation. Scott Barry SBBWorks, Inc. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark Steely Sent: Thursday, May 31, 2007 3:19 PM To: [email protected] Subject: 3390-MOD's 9 This is my first experience with these volumes and I have a little problem. There was a requirement to use these mod 9 volumes so our customers could dump very large files to these packs. These two volumes are SMS managed. The first test failed with a E37. The JCL contained space(cyl,(3000,1000)). It allocated only 4000 cylinders on the first volume, switched to the second volume and allocated another 4000 cylinders and then abended. Is there something in the JCL that needs to be coded to make the system understand these files are allowed to go beyond the default size. We are z/OS v1r7. Any help would be appreciated. Thank You ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
