Only 1 host does Backup and Migration. It has the Backup windows
defined. The 2 Recall only LPARS have (0000 0000 0000)
as the defined window for Backup, Primary Space Mgt. and Secondary Space
Mgt.
Addvol commands are the same for all members.

However another posting on this subject mentioned the ONLYIF HOSTID(n)

example follows:
Note:  Because the ONLYIF command processes the next command, if the
line
       after the ONLYIF command is blank or contains a comment, DFSMShsm
       considers that line.  For example, the comment after the ONLYIF

       command is considered for processing, not the actual SETSYS

       command.

 

          ONLYIF HSMHOST(A)

          /* The following is only done for Host A */

          SETSYS ABSTART(0600 0700) 
                                     
  To avoid this error, use a continuation character to join the   
  comment to the command, like this:                              
                                                                  
     ONLYIF HSMHOST(A)                                            
     /* The following is only done for Host A */ +                
     SETSYS ABSTART(0600 0700)                                    

If your level of software supports it, ONLYIF will allow you to have 1
ARCCMD member for all LPARs. 

-----Original Message-----
From: Bob Henry [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 18, 2006 4:47 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: DFHSM multi-host environment

The following is from the "DFSMShsm Implementation and Customization
Guide",  chapter 5, "Primary Address Space Startup Procedure". Note the
last sentence. Maybe I misunderstood something or took too literal an
interpretation. 


The CMD=00 keyword refers to the ARCCMD00 member of PARMLIBs discussed
in "Parameter Libraries (PARMLIBs)" in topic 2.3.1.2. You can have as
many ARCCMDxx and ARCSTRxx members as you need in the PARMLIBs. DFSMShsm
does not require the values of CMD= and STR= to be the same, but you may
want to use the same values to indicate a given configuration. In this
publication, the ARCCMD member is referred to generically as ARCCMDxx
because each different ARCCMDxx member can be identified by a different
number. 
Much of the rest of this discussion pertains to what to put into the
ARCCMDxx member. 
For information about the ARCCMDxx member in a multiple DFSMShsm-host
environment, see "Defining All DFSMShsm Hosts in a Multiple-Host
Environment" in topic 1.11.4. To minimize administration, we recommend
that you use a single ARCCMDxx and a single ARCCSTRxx member for all
DFSMShsm hosts sharing a common set of control data sets in an HSMplex. 


Are all your DFHSM hosts doing autobackup & migration or do you control
that by setting up different ADDVOL parms in each ARCCMDxx?
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------
Bob Henry * Mgr., Rochester IT * SunGard Higher Education * 3000 Ridge
Rd. 
E., Rochester, NY  14622
Tel 585-339-2366 * Mobile 585-330-5240 * Fax 610-578-3014 *
[EMAIL PROTECTED] * www.sungardhe.com

CONFIDENTIALITY: This email (including any attachments) may contain
confidential, proprietary and privileged information.
Unauthorized disclosure or use is prohibited. If you received this email
in error, please notify the sender and delete this email from your
system. Thank you.


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

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