It would be SO nice to have a mirrored DR, but alas no. Thanks for your
comments.
Mark Jacobs
On 12/28/11 14:04, Skip Robinson wrote:
We use *all* couple data sets in DR, just not necessarily the mirrored
copies.
-- Sysplex, ARM, SFM, BPXMCDS, and WLM data sets are mirrored from
production.
-- CFRM data sets are created and populated with the (presumed) current
CFRM policy from the driving system before first IPL. This process is
required for GRS star, which must have an active structure at IPL. When
you create a CFRM policy, you can point to any couple data on any volume.
-- Logger data sets are created from the driving system before first IPL
but populated with the (presumed) current logger policy from the newly
IPLed DR system. When you create a logger policy, the policy can only go
to the current active logger data set.
-- 'Presumed current' is based on the ISPF last update stats in the
(mirrored) common policy data set.
-- During the first IPL, there is a WTOR for each of the newly created
data sets; it requires 'C': go with PARMLIB specification rather than last
used.
.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]
From: Mark Jacobs<[email protected]>
To: [email protected]
Date: 12/28/2011 10:11 AM
Subject: Re: Couple Data Sets - DR Considerations
Sent by: IBM Mainframe Discussion List<[email protected]>
Regarding the WLM couple datasets, no we don't have a reason other than
the desire not to run with some production couple datasets, and some
specifically for DR.
Do you use your production logr couple dataset, or one specifically for
DR? If the latter how do you keep the two in sync since AFAIK you can't
add/change logger entries in a specific couple dataset, only the active
one.
Mark Jacobs
On 12/28/11 12:37, Skip Robinson wrote:
We provide our own DR between data centers with fully mirrored disk, but
we still handle couple data sets in a manner similar to yours. However,
we
do not create new WLM data sets. Do you have a specific reason for doing
so? We (OS sysprogs) are caretakers of CFRM and logger policies, which
can
be recreated before (CFRM) or immediately after (logger) the first IPL
by
automated batch processes. But WLM AFAIK requires ISPF and manual
involvement by the performance/tuning group, who owns WLM policies.
We've
never seen a need to tailor WLM for the DR environment.
From: Mark Jacobs<[email protected]>
To: [email protected]
Date: 12/28/2011 06:53 AM
Subject: Couple Data Sets - DR Considerations
Sent by: IBM Mainframe Discussion List<[email protected]>
We recover three sysplex's at DR, two single system sysplexes and one
multi-system parallel sysplex. Since we don't utilize any data
replication processes, we still perform DR via full volume backups and
restores using our providers floor system.
The two single system sysplexes use their production couple datasets at
DR, but we have a separate set of DR couple datasets for the parallel
sysplex that we populate at DR (mainly CFRM, LOGR, WLM, the others we
don't care about at DR).
Just wondering how everyone else is doing it.
--
Mark Jacobs
Time Customer Service
Tampa, FL
----
One of life's greatest mysteries is how the boy who
wasn't good enough to marry your daughter can be the
father of the smartest grandchild in the world.
Yiddish Proverb
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
