I've lost track of the original postings in this thread, but I have this
suggestion: never IPL an entire sysplex into a new XCF-anything unless you
absolutely have no other choice. It's always preferable to move
dynamically into a new XCF-something with at least one member running on
the old one. It's (almost always?) possible to define a new thing in
advance and migrate to it via SETXCF commands. This may mean defining a
currently nonexistent resource ahead of time. XCF will tolerate a new
thing it can't find yet as well as later tolerate an old thing it no
longer find. Just clean up definitions at the very end to reflect the new
environment.
In the case of control data sets, create new ones with modern attributes,
then SETXCF-migrate to them. By the time an actual hardware replacement
occurs, new things should already be defined to the existing sysplex. The
danger in cold starting with new components is that there's no way to test
the process in advance, and falling back to a known environment may be
complicated beyond reasonable resolution.
.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: Jihad Kawkabani <jihad_k_kawkab...@progressive.com>
To: IBM-MAIN@bama.ua.edu
Date: 04/16/2012 12:05 PM
Subject: Re: brand new CF LPAR
Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu>
When you define your CFRM policy using IXCMIAPU you can point to your
newly created CFRM CDS as Such:
DATA TYPE(CFRM) REPORT(YES)
DSN(Your newly created CFRM CDS name)
DEFINE POLICY NAME(policyname here) REPLACE(YES)
Etc..........................
That populates the newly created CFRM CDS with the policy(ies) that point
to the new coupling facilities. In your COUPLExx member you can simply
specify the new CFRM data sets as well as the POLICY you want to use by
specifying CFRMPOL(xxxxxxxx) where xxxxxxxx is your new policy name as
specified by the IXCMIAPU job.
The above is an example of only how to populate an inactive CFRM dataset.
The DSN keyword on the DATA statement is what you need.
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of Munif Sadek
> Sent: Monday, April 16, 2012 09:08 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: brand new CF LPAR
>
> Just to add to my previous request, I have to define new coupling
facility
> datasets to enbale support for newer protocols and do not know **yet**
> how to pouplate them with our exisitng sysplex policies.. May I IPL an
LPAR
> (z/OS 1.13) with the new coupling facility datasets and then definine
&
> activate (old) policies.. will it work?..
>
> thanks again.. Munif
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
