Re: In over my head again...

Well, you could define a volume group in the EDT using DYNAMASK with only that 1 volume, and then use UNIT=<volume group> in your TSO alloactions.  That would work except for dynamic allocations from TSO applications like RPF,  where you can't override the UNIT parameter.  I'm not sure if that is what you want.  
If you are in control of your allocations you may also assign the volume directly e.g. VOL=SER=cccccc, or ALLOC ..... VOL(CCCCCC) etc.

Roger

--- In [email protected], Ron Hudson <hudson.ra@...> wrote:
>
> On Mon, Apr 26, 2010 at 4:18 PM, ScottC <scosel@...>wrote:
> 
> >
> >
> >
> >
> > Ok Ron,
> >
> > Here are the steps I followed. It all worked:
> > I have my own question to the group at the end...
> >
> > 1) Startmvs and Startterm
> >
> > 2) Create DASD volume - use Hercules Utility command:
> > DASDINIT -a -z user01.141 3350 user01
> >
> 
> > 3) Copy created file user01.141 to DASD directory
> >
> > I actually created mine directly in the dasd directory.
> 
> 
> > 4) On the Hercules console type:
> > attach 141 3350 dasd/user01.141
> >
> > 5) Submit the following JCL to initialize the DASD:
> > //ICKDSF JOB ICKDSF,CLASS=A,MSGLEVEL=(1,1)
> > //ICKDSF EXEC PGM=ICKDSF,REGION=4096K
> > //SYSPRINT DD SYSOUT=A
> > //SYSIN DD *
> > INIT UNITADDRESS(141) NOVERIFY VOLID(USER01) OWNER(HERCULES) -
> > VTOC(0,1,1)
> > //
> >
> > 6) Reply on the MVS console (prefix with "/" on a Consolidated Console) to
> > go ahead and alter the volume:
> > r xx,U
> >
> > 7) Enter on the MVS console (prefix with "/" on a Consolidated Console):
> > v 141,online
> > m 141,vol=(sl,USER01),use=STORAGE
> >
> > 8) In SYS1.PARMLIB(VATLST00)
> > add:
> > USER01,0,0,3350 ,N USER PACK 01 - (STORAGE)
> >
> > 9) Submit the following JCL to define User Catalog:
> >
> > //DEFUCATS JOB USER=HERCAD,CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)
> > //IDCAMS EXEC PGM=IDCAMS,REGION=4096K
> > //SYSPRINT DD SYSOUT=A
> >
> > //USER01 DD UNIT=3350,VOL=SER=USER01,DISP=OLD
> > //SYSIN DD *
> >
> > DEFINE USERCATALOG ( -
> > NAME (UCUSER01) -
> > VOLUME (USER01) -
> > TRACKS (8324 0) -
> > FOR (9999) ) -
> > DATA (TRACKS (15 5) ) -
> > INDEX (TRACKS (15) )
> > DEFINE ALIAS (NAME (USER01) -
> > RELATE (UCUSER01) )
> > //
> >
> > 10) Reply on the MVS console (prefix with "/" on a Consolidated Console) to
> > continue:
> > r xx,SECRET <== if mastercatalog password requested
> > r xx,SECRET <== if mastercatalog password requested
> >
> > 11) Add to your ".conf" script:
> > 0141 3350 dasd/user01.141 ro sf=shadow/user01_1.141
> >
> > 12) On RPF Screen 3.2, allocate a USER01 dataset on Volume USER01:
> > RPF Data set utility: userid=HERC01---------------------------Dataset
> > allocated
> > Option ===> 1
> >
> > 1 ALLOCATE - Allocate a dataset
> > 2 DELETE - Delete a dataset
> > X EXIT - Return
> >
> > Data set information
> >
> > Prefix = USER01
> > Library = TEST
> > Type = CNTL
> >
> > Volume space and DCB info (option 1 only)
> >
> > Unit = SYSDA RECFM = FB
> > Volume = USER01 LRECL = 80
> > Space unit = CYL BLKSIZE = 3120
> >
> > Primary= 1 Secondary= 0 Directory= 0
> >
> > Hit PF03/15 to return
> >
> > Dataset was allocated.
> >
> 
> Seems like that is what I did too..  I have gone ahead and moved
> user HUDSON to SYS1.UCAT.TSO after finding out that HERCxx all have all
> files there anyway.
> 
> But now I have a DASD spinning but not really being used...
> 
> 
> >
> > Now, I have a question... Is there a way to force USER01 datasets to first
> > attempt to be allocated on Volume USER01 by default instead of always
> > allocating on PUB002 by default?
> >
> > Scott
> >
> >  
> >
>