I use full volume copy for the sysres vols and dfdss logical copy for
the z/FS files. 

Our sysres sets are 3 -3390-3 for non-VSAM and 2 3390-3 for VSAM( ZFS).
We use the target volser as part of the DSN to ensure unique names per
version across multiple images.

Sample DFDSS control cards (one volume omitted for brevity).

//*---------------------------------------------                   
//*  ZFS FILES ARE LINEAR VSAM                                     
//*  DELETE FILES FROM TARGET VOLUME(S) &TVOL4 AND TVOL5           
//*---------------------------------------------                   
//*                                                                
//IDCAMS  EXEC PGM=IDCAMS,REGION=256M,COND=(0,NE)                  
//SYSPRINT  DD SYSOUT=*                                            
//DD2       DD UNIT=3390,DISP=SHR,VOL=SER=TVOL5                    
//SYSIN     DD DATA,DLM=$$                                         
 DEL 'SYS1.OMVS.JAVA31V5.TVOL5'   FILE(DD2) CAT(SYS1.PRD2Z19.MCAT) 
 DEL 'SYS1.OMVS.JAVA64V5.TVOL5'   FILE(DD2) CAT(SYS1.PRD2Z19.MCAT) 
 SET MAXCC=0                                                       
$$                                                                 
//*---------------------------------------------                   
//*  ZFS FILES ARE LINEAR VSAM                                     
//*  USE DFDSS DATASET COPY W/RENAME TO COPY Z/FS FILES            
//*---------------------------------------------                   
//*                                                                
//COPY2   EXEC PGM=ADRDSSU,REGION=256M PARM='TYPRUN=NORUN'        
//SYSPRINT  DD SYSOUT=*                                           
//SYSIN     DD *                                                  
 PARALLEL                                                         
 COPY DS                                               -          
        (INCLUDE                                       -          
              (                                        -          
              SYS1.OMVS.**                             -          
              )                                        -          
        )                                              -          
        RENAMEUNC                                      -          
        (                                              -          
         (SYS1.OMVS.JAVA31V5.VOL5,SYS1.OMVS.JAVA31V5.TVOL5)      -
         (SYS1.OMVS.JAVA64V5.VOL5,SYS1.OMVS.JAVA64V5.TVOL5)      -
        )                                              -          
  LOGINDYNAM(VOL5)                                     -          
  ODY(TVOL5) RECATALOG(SYS1.XXXXXXX.MCAT) OPT(4)       -          
  ADMIN  NSC TOL(ENQF)  BYPASSACS(**)                             


HTH,

<snip>
Our upcoming migration from HFS to zFS for the root file systems is
causing a 
new problem for us. 

The previous maintenance method was to keep the HFS root file system on 
the sysres with all other non-VSAM SMPE-target files. All datasets were 
implicitly cataloged at IPL time. By replacing the SYSRES volume a total

replacement or back-off of maintenance was just an IPL away. We
currently 
are running from a single mod 27 sysres. The rest of the HFS/ZFS file
systems 
will be mounted from other non-SMPE impacted volumes. 

The zFS file systems on the other hand is subject to the special volume 
ownership and naming requirements of VSAM. We can no-longer use a simple

full volume copies to transfer the test SYSRES to production. Further it
looks 
like a second dump will need to be done of the test zFS root files and
then a 
restore with the RENAMEU option run made under the production master 
catalog. We may even have to put the zFS files on separate sysres
volumes 
which are "owned" by the production system catalog structure.
</snip>
 

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

Reply via email to