Message-
From: IBM Mainframe Discussion List On Behalf Of
Elaine Beal
Sent: Monday, February 3, 2020 12:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: DR Sysplex Procedure
CAUTION EXTERNAL EMAIL
Thanks all.
We were able to issue the start policy for the DR policy and all went well
Thanks all.
We were able to issue the start policy for the DR policy and all went well!
till we got to the network :)
Elaine
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Thank you.
I believe you may have hit on our issue.
We're getting the in use for the LOGR which is not new and I am okay with that.
I'm confident we're picking up the DR COUPLExx but we've never had the POLICY
statement.
We were planning on issuing the SETXCF START with the new policy name.
The
Sysplex Procedure
To expand on this...
yes, we are just getting to the DR test:)
I have new XCF and CFRM datasets pointing to new plant id and serial number,
policy but no new LOGR and WLM, using same as prod (on another machine)
defined a new policy in DR CFRM
We IPLd at the other site for DR
Unless we're picking up the wrong COUPLE member, the CFRM and XCF
are pointing to the DR datasets
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO
on
01/23/2020 12:39:56 PM:
> From: Elaine Beal
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 01/23/2020 12:40 PM
> Subject: [EXTERNAL] Re: DR Sysplex Procedure
> Sent by: IBM Mainframe Discussion List
>
> To expand on this...
> yes, we are just getting to the DR test:)
>
It sounds like your COUPLExx still points to your prod XCF and CFRM
datasets.
On Thu, Jan 23, 2020 at 1:40 PM Elaine Beal wrote:
> To expand on this...
> yes, we are just getting to the DR test:)
>
> I have new XCF and CFRM datasets pointing to new plant id and serial
> number, policy
> but no
To expand on this...
yes, we are just getting to the DR test:)
I have new XCF and CFRM datasets pointing to new plant id and serial number,
policy
but no new LOGR and WLM, using same as prod (on another machine)
defined a new policy in DR CFRM
We IPLd at the other site for DR and got the
At one point, I had a setup that included a SITE system symbol in the CDSs
for XCF and CFRM to auto-resolve such things
Rob Schramm
Senior Systems Consultant
On Thu, Oct 17, 2019 at 12:41 PM Elaine Beal wrote:
> Yes, I would IPL with a different loadparm to point to COUPLExx with DR
> XCF
Yes, I would IPL with a different loadparm to point to COUPLExx with DR XCF and
CFRM
but WLM and LOGR would not change (use same ones as in current environment)
In falling back, I would use the same current (not DR) XCF/CFRM/WLM/LOGR
so I would use the same LOGR and WLM for DR and 'prod'
no
Are you talking LOGR and WLM CDS's in the couplexx member?
if so as long as they are defined in the DR's COUPLExx member
Carmen Vitullo
- Original Message -
From: "Elaine Beal"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, October 16, 2019 11:52:43 AM
Subject: Re:
So, both systems down
IPL LPAR1 with new XCF and CFRM, use existing LOG and WLM files
Will that cause an issue falling back?
by using the same LOG and WLM files?
Thanks,
Elaine
--
For IBM-MAIN subscribe / signoff / archive
Kees, thank you. I see that would not work and it would be better to have both
systems down and IPL one at a time.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Elaine Beal
> Sent: 09 October, 2019 16:17
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: DR Sysplex Procedure
>
> We are planning to test a remote copy sysplex environment and I would like
> to test it in
We are planning to test a remote copy sysplex environment and I would like to
test it in our home DEV environment
PROD data will not be accessible during the DR test so PROD sysplex should not
be affected
To test in DEV I have defined a new XCF and CFRM since I will need to do that
for DR
to
15 matches
Mail list logo
