- snip -
I have a full test this weekend, so hopefully will have some of this ironed
out. I am going with a newly formatted CFRM dataset and retaining all the
other COUPLE datasets.
If I use a new CFRM dataset, where is the CF policy information stored? I
was thinking it was stored in the
You should probably *not* use the DSN/VOL parameters for normal production
policies. By default the system will find and use the active CFRM couple
data set. But whenever you need to put a policy into *another* couple data
set, that's where the parameters come into play. You only need to put
I have a full test this weekend, so hopefully will have some of this ironed
out. I am going with a newly formatted CFRM dataset and retaining all the
other COUPLE datasets.
If I use a new CFRM dataset, where is the CF policy information stored? I
was thinking it was stored in the XCF COUPLE
When you create/reformat the CFRM couple data set, there is no CFRM
policy. It must be (re)created from a driver system before the first DR
IPL. (You could kludge it with multiple IPLs of the DR system, but you
really don't want to go there.)
On the driver system, (re)create the CFRM policy
- snip -
We were early users of XRC circa 1998. In our first few tests, we had
lingering problems because, with mirrored CFRM data set, the newly IPLed
systems could never get over the loss of the two CFs left back in the
smoking hole. They were convinced that some magic would bring the
Migrating to a new CF is different from recovering in a DR environment. In
migrating, you move structures from one CF to another in a controlled
fashion. Once all structures have been moved out, the CFRM couple data set
knows that the old CF is no longer in use. It can be left ready for
We were early users of XRC circa 1998. In our first few tests, we had
lingering problems because, with mirrored CFRM data set, the newly IPLed
systems could never get over the loss of the two CFs left back in the
smoking hole. They were convinced that some magic would bring the lost CFs
back
In a message dated 3/13/2006 4:33:53 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
They can still be in the (composite) CFRM policy, but now they're simply
unreachable in DR just as the DR CFs are unreachable in production. No
more problem. Paolo is right.
Welcome back, you
SHARE in Seattle was very fine. ;-)
Thanks for asking about ESCON cards: the question motivated me to inquire
and actually make a plan. Cards are coming out this weekend; we need a POR
to force SAP reallocation. Stay tuned...
.
.
JO.Skip Robinson
Southern California Edison Company
SHARE MVS
In a message dated 3/13/2006 5:18:44 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
and actually make a plan. Cards are coming out this weekend; we need a POR
to force SAP reallocation. Stay tuned...
Thanks for update...
Pat,
believe me or not... there's no way to restart a Parallel Sysplex on a D/R
site and
with a one shot IPL operation, unless you have an empty XCF Couple
Dataset and a
COUPLExx parameter for D/R purposes. XCF couple datasets have an
administrative section,
generally not accessible by customer
Patrich,
that can work provided thet you have defined and initialized a new XCF
couple dataset and a DR copy
of your COUPLExx member of PARMLIB, pointing to this XCF CDS and containing
the CFRMPOL
parameter, related to the CDRM policy name you want to start at the DR
site. In this case, your
I was hoping to use the existing COUPLE dataset and the existing policy.
Since these datasets will be PPRC mirrored I was hoping to find a way to
not maintain 2 separate policy definitions so that the day-to-day policy
definitions would be automatically used at the DR location.
Pat,
as I wrote, you actually CAN mantain your CFRM couple datasets, with your
policy, provided that
your policy comprises both primary and DR CF; what you need to have for DR
purposes only, is an
empty and initialized XCF COUPLE dataset (easy to do once and to
forget) and a PARMLIB
COUPLExx
- snip -
as I wrote, you actually CAN mantain your CFRM couple datasets, with your
policy, provided that your policy comprises both primary and DR CF; what you
need to have for DR purposes only, is an empty and initialized XCF COUPLE
dataset (easy to do once and to forget) and a
these datasets will be PPRC mirrored
One of the two sets of datasets IBM recommends to not mirror is the CDS set.
The other is PAGE.
I have another set that I never mirror'd: SCRATCH.
The overhead of synchronous mirroring kills the first two, for sure.
-
-teD
I’m an enthusiastic proselytiser
- snip -
these datasets will be PPRC mirrored
One of the two sets of datasets IBM recommends to not mirror is the CDS set.
The other is PAGE.
I have another set that I never mirror'd: SCRATCH.
The overhead of synchronous mirroring kills the first two, for sure.
- snip -
The
The GDPS hyperswap is impossible without mirroring the PAGE datasets.
When I got downsized from IGS, hyperswap hadn't been invented.
I am now in a non-GDPS environment, so I haven't been keeping up with it all.
I was just recalling from the manual we used as part of the GDPS service.
Thanks for
On Tue, 7 Mar 2006 17:51:26 +0100, TISLER Zaromil [EMAIL PROTECTED]
AUSTRIA.COM wrote:
- snip -
these datasets will be PPRC mirrored
One of the two sets of datasets IBM recommends to not mirror is the CDS
set.
The other is PAGE.
I have another set that I never mirror'd: SCRATCH.
The
--- snip ---
- snip -
these datasets will be PPRC mirrored
One of the two sets of datasets IBM recommends to not mirror is the CDS
set.
The other is PAGE.
I have another set that I never mirror'd: SCRATCH.
The overhead of synchronous mirroring kills the first two, for sure.
- snip
We are in the process of setting up a new Disaster Recovery scenario
using PPRC DASD and a Hot Stand-by datacenter (z9 CBU processor)
I have a question concerning how others have dealt with using a Coupling
Facility in this scenario. At our DR site we will have one ICF
configured on the same
Though not recovering in the exact manner you are planning your PREFLIST
proposal looks good to me. With a PREFLIST consisting of ICFXXA, ICFXXB
and ICFXXD here are some syslog messages for your review. ICFXXD does not
exist at home.
At home:
IXC517I SYSTEM ABLE TO USE
COUPLING
22 matches
Mail list logo
