Question 1: I see you got 3 extents. How many of the 7 volumes did that cover? 
Two (2) mod-9's; RLSE released all the other requested space.
            From MVS File-Aid
                CCCCC-HH -------- D A T A S E T   N A M E ----------- Org   
Trks   XofY STAT    VOLSER
                02999 00 NFCPPARA.B5I.EHRI.HS00.SF50.XMLT             PS   
59970   1      2     PRDC46
                03860 00 NFCPPARA.B5I.EHRI.HS00.SF50.XMLT             PS   
34275   1      1   PRDJ77

Question 2: what amount was allocated in the three extents?
                94245tracks or 6283cylinders: see below

3.4 Data Set Information shows 6654 cylinders (cannot explain that)
                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***


Question 3: Any reason not to use an SMS pool? Yes; we are a Payroll Processing 
center that pays 660,000 Federal Employees utilizing Computer Associates
                IDMS.  A lot of the code was written in the 1970's and 1980's; 
more importantly a lot of the batch processes that are used
                Un-catalogs DSNs which my understanding in SMS un-catalogs does 
a delete which the programmer could not go back to a previous step where a      
        DSN was un-cataloged re-catalog the DSN and start processing from that 
step.


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, February 10, 2014 5:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Large Multi-Volume Physical Sequential allocation question

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" <bob.co...@nfc.usda.gov>
>Sent: Feb 10, 2014 2:42 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>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:IBM-MAIN@LISTSERV.UA.EDU]
>On Behalf Of Lizette Koehler
>Sent: Friday, February 07, 2014 7:52 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>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:IBM-MAIN@LISTSERV.UA.EDU]
>> On Behalf Of Cosby, Bob - OCFO
>> Sent: Friday, February 07, 2014 11:46 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> 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 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN





This electronic message contains information generated by the USDA solely for 
the intended recipients. Any unauthorized interception of this message or the 
use or disclosure of the information it contains may violate the law and 
subject the violator to civil or criminal penalties. If you believe you have 
received this message in error, please notify the sender and delete the email 
immediately.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to