Faver and HSMPlexes how to setup manual process.

book

Article ID: 141193

calendar_today

Updated On:

Products

CA FAVER VSAM Data Protection for Z/OS

Issue/Introduction

In preparation for a sysplex split of our production and test environments, I have created a new HSMPlex.  Our current sysplex has 2 HSMPlexes.  HSMPLexT is accessible from LPARs 2 and 5.  HSMPLexP is accessible from LPARs 1, 3, 4 and 7.  All disk is shared for now.
 
How can I set up FAVER to access either HSM when a user chooses to recall during an export operation?
 
I would prefer not to have them code in the JCL as the HSM CDS names will likely change.

Environment

Release : 4.5

 

Resolution

 Not sure why anyone would want to have DFHSM restore a file that is simply being backed up for a short time like a Faver export would be.

We never advise customers to increase their overhead for that process. Faver is not a data management utility like DFHSM or CA DISK. Faver is a IDCAMS utility.

However, on page 68 of the Faver User Guide is an example showing how to use the DD statement to point to a specific MCDS.

//MCDS DD DSN=mcds.data set.name

Please be sure that you have not already used GVPARMS to define a MCDS globally for Faver as well. To determine what you are using for your global parms you can run this job.

//GVPARMS  EXEC  PGM=GVPARMS                      
//SYSLIB   DD  DISP=SHR,DSN=your.FAVR45.CBSVLINK
//SYSPRINT DD  SYSOUT=*                           
//SYSIN    DD  *        

If you decide to define something globally you can use the following sample to setup GVPARMS.

//SYSIN    DD  *

SMGR=HSM                  
NORECALL                  
SMGRDDN(3)=FILES          
SMGRDSN(3)='DFHSM.FILES'  
SMGRDDN(4)=PARMLIB        
SMGRDSN(4)='DFHSM.PARMLIB'                

To utilize more than one set of HSM files you can use this pattern

SMGR=HSM                  
SMGRDDN(1)=MCDS1DD        
SMGRDSN(1)=MCDS1.filename 
SMGRDDN(2)=MCDS2DD        
SMGRDSN(2)=MCDS2.filename