I see you got 3 extents. How many of the 7 volumes did that cover? The VOLUME SERIAL shows multiple volumes, but it is helpful to know how many were used.
next, what amount was allocated in the three extents? I would suspect that for non sms the VOL= might need to include serial numbers it could go to. Any reason not to use an SMS pool? Lizette -----Original Message----- >From: "Cosby, Bob - OCFO" <[email protected]> >Sent: Feb 10, 2014 2:42 PM >To: [email protected] >Subject: Re: Large Multi-Volume Physical Sequential allocation question > >Lizette you are correct I found out from Tom this has been around since OS 360 >must have missed that part of the class; at any rate we are starting to >allocate NON SMS DSNs that span multiple volsers. We kept getting SB37 abend >until we used the UNIT=(3390,P) and VOL=(,,,7) parameters. > >Data Set Name . . . . : NFCPPARA.B5I.EHRI.HS00.SF50.XMLT > >General Data Current Allocation > Management class . . : **None** Allocated cylinders : 6,654 > Storage class . . . : **None** Allocated extents . : 3 > Volume serial . . . : PRDC46 + > Device type . . . . : 3390 > Data class . . . . . : **None** > Organization . . . : PS Current Utilization > Record format . . . : FB Used cylinders . . : 6,654 > Record length . . . : 200 Used extents . . . : 3 > Block size . . . . : 27800 > 1st extent cylinders: 3998 > Secondary cylinders : 4369 Dates > Data set name type : LARGE Creation date . . . : 2014/02/05 > SMS Compressible. . : NO Referenced date . . : 2014/02/05 > Expiration date . . : ***None*** > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Lizette Koehler >Sent: Friday, February 07, 2014 7:52 PM >To: [email protected] >Subject: Re: Large Multi-Volume Physical Sequential allocation question > >The P indicates > >Asks the system to allocate the same number of devices as requested in the >VOLUME volume-count or SER subparameter, whichever is higher. Thus, all >volumes for the data set are mounted in parallel. > >If you specify the P subparameter for system-managed DASD, the system ignores >it. If you specify the P subparameter for system-managed tape libraries, the >system honors it > > >So according to the JCL Reference manual, the P will be ignored for DASD. >Since you say NON-SMS I am not sure. > >However, you have only asked for 7 volumes. What size is the volumes it is >getting allocated on? 3390-3,3390-27???? >Is there sufficient space on the 7 volumes? > >Did you receive any messages when this ran? If so, please post the complete >messages? > > > >The subparameter P has been around for a bit. > > >Lizette > > >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] >> On Behalf Of Cosby, Bob - OCFO >> Sent: Friday, February 07, 2014 11:46 AM >> To: [email protected] >> Subject: Large Multi-Volume Physical Sequential allocation question >> >> Had a problem allocating a NON SMS Large PS file that would not span >volumes; is >> anyone on this list familiar with the parameter UNIT=(3390,P) which >worked? >> This parameter pre-allocates the volsers; never saw this before and is >this a new >> feature with z/OS R1.13? >> >> //DD01 DD DSN=DSN1,DISP=SHR >> // DD DSN=DSN2,DISP=SHR >> // DD DSN=DSN3,DISP=SHR >> //DD01O DD DSN=DSN.OUTPUT, >> // DISP=(,CATLG,DELETE),UNIT=(3390,P),DSNTYPE=LARGE, >> // >> DCB=(NFCP.PRODMODL,DSORG=PS,RECFM=FB,LRECL=200,BLKSIZE=0), >> // SPACE=(CYL,(4369,4369),RLSE),VOL=(,,,7) >> >> >> > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
