Paolo's procedure will handle the change with what amounts to a
sysplex-wide cold start. I always worry about 'cold start' of any stripe or
flavor. What happens if some otherwise trivial error results in no system
available? With GRS star, you absolutely MUST have at least one system
that's happy with the new configuration or you will have no way to fix the
problem. Here's an alternate suggestion.
For Disaster Recovery purposes, we define in our standard CFRM policy all
the normal CF LPARs at the production site plus all the DR CF LPARs at the
failover site. During normal IPL, we get complaints of 'unable to connect'
for the DR CFs, but at the DR site, systems connect to the DR CFs, build
structures there, and complain about the production CFs. No harm no foul in
either scenario.
So, you might consider dynamically implementing a CFRM policy that defines
the new CF LPARs just like the production ones. Include the new LPARs in
the preference list for all structures. When this policy takes effect, it
should have no impact on running systems other than messages about
unreachable CFs. Then when you bring up the new CF LPARs, every system
should be happy to build structures there. The advantage with this solution
is that you are never exposed to the 'no active policy' condition. There
are mechanisms to handle this--mainly the default policy specification in
COUPLExx--but for a once-only, untestable, do-or-die situation, I would opt
for a procedure with stepwise changes rather than earthquake-style
upheavals.
.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]
Paolo Cacciari
<[EMAIL PROTECTED]
T.IBM.COM> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Re: Change CFRM policy name for IPL
09/05/2007 06:16
AM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
snip..................
LPAR numbers will be changed during next IPL. The number of CF LPAR will
change. The system (resides on the same CPC) uses GRS=STAR, so valid CF
policy is required during IPL.
I can prepare new CFRM policy to reflect the change. However default
policy is last used one.
Q: How can I fix the policy name for IPL ?
Is it CFRMPOL(policy_name) in COUPLExx?
snip .......................
Roland,
this can be an option for you:
1 - allocate a NEW FORMATTED XCF couple dataset (primary and alternate)
2 - allocate a NEW FORMATTED CFRM couple dataset (primary and alternate)
3 - write a NEW CFRM POLICY in new datasets, addressing your new CF LPAR
4 - set up a COUPLExx member in PARMLIB to address new XCF cuple datasets,
new CFRM couple datasets and use CFRMPOL(xxx) to activate your NEW
CFRM policy (see -3- above)
----------------------------------------------------------------------
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
