Have you tried allocating non-sms multi volume via ISPF 3.2?

You have to choose a DS HLQ that isn’t typically SMS managed that you have 
access to create, and have some volumes that aren’t SMS managed, and then just 
go through allocation, but put a slash in that last field, and you get the 
pop-up where you fill in the rest.  I just did that, and was able to allocate a 
non-sms multi-volume dataset.

I think your problem is that you don’t have the ability to tell SMS to stay out 
of the way.

  Average record unit                  (M, K, or U)                         
  Primary quantity  . . 15             (In above units)                     
  Secondary quantity    30             (In above units)                     
  Directory blocks  . . 0              (Zero for sequential data set) *     
  Record format . . . . FB                                                  
  Record length . . . . 80                                                  
  Block size  . . . . . 27920                                               
  Data set name type                   (LIBRARY, HFS, PDS, LARGE, BASIC, *  
  Data set version  . :                 EXTREQ, EXTPREF or blank)           
  Num of generations  :                                                     
  Extended Attributes                  (NO, OPT or blank)                   
  Expiration date . . .                (YY/MM/DD, YYYY/MM/DD                
 Enter "/" to select option             YY.DDD, YYYY.DDD in Julian form     
 /  Allocate Multiple Volumes           DDDD for retention period in days   
                                        or blank)                           



Command ===>                                  
                                              
 Enter the number of volumes to allocate or   
 the names of one or more volumes and         
 press Enter to allocate or enter Cancel      
 command to exit.  If a number is entered,    
 any volume names will be ignored.            
                                  More:     + 
 Number of volumes to allocate:               
                                              
 Volume names:                                
  1. VSM01A  2. VSM02A  3. VSM03A  4.         
  5.         6.         7.         8.         
  9.        10.        11.        12.         

_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Engineering
[email protected]
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Charles Mills
Sent: Wednesday, April 06, 2016 1:52 PM
To: [email protected]
Subject: Re: How force dataset non-SMS?

Nice idea but no cigar.

IEF236I ALLOC. FOR xxxxxxxx STEP1                                     
IGD101I SMS ALLOCATED TO DDNAME (TESTDD  )                            
        DSN (xxxxxx.xxxxxxxx.DELETEME                    )            
        STORCLAS (STANDARD) MGMTCLAS (STANDARD) DATACLAS (STANDARD)   
        VOL SER NOS= LS0501                                           

One volume. (And the SMF 18 confirms that.)

Here is the exact DD:

//TESTDD  DD    DISP=(NEW,CATLG),UNIT=(SYSALLDA,3),SPACE=(TRK,3),  
//  DSN=xxxxxx.xxxxxxxx.DELETEME,                                  
//  VOL=(,,,3)                                                     

I suspect I am going to have to write a program to fill the thing up. Wish I 
could do an FEOV in Rexx.

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of R.S.
Sent: Wednesday, April 06, 2016 8:42 AM
To: [email protected]
Subject: Re: How force dataset non-SMS?

So, you want multi-volume dataset, not non-SMS dataset - yes?

Instead of fighting against SMS ACS routines you could try the following:
DSN=ANY.PROPER.NAME,DISP=(,CATLG),VOL=(,,,4),SPACE=(TRK,(1,1,))...

----------------------------------------------------------------------
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

Reply via email to