"Do both LPARs need to be down (not desirable) before IPLing either of them 
with the new CF and XCF?"

I would try to test the real situation as much as possible.

Besides, I think it will not work. LPAR's don't join each other, they join a 
Sysplex. After ipling one system with the new definitions, it runs from 
different Couple datasets and is a Sysplex of its own, but with XCF connections 
to the other LPAR that runs from the old Couple Datasets, so in the old 
Sysplex. This seems asking for unexpected problems.

Kees

> -----Original Message-----
> From: IBM Mainframe 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 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 account for the different CPU serial number.
> In DEV I have not changed the serial number for the test, I'm just trying
> out the procedure.
> 
> At DR we will IPL the sysplex LPARs one at a time so I'm not concerned
> about the order, the files or the join.
> 
> I'm not sure about the order for DEV.
> 
> Do both LPARs need to be down (not desirable) before IPLing either of them
> with the new CF and XCF?
> Or is one at a time okay since one is removed from the sysplex at shutdown
> and just won't be able to join the current one at IPL
> 
> I am not planning to create new LOGR and WLM files at DR but I will need
> to create them for the test as they are shared.
> 
> so, the plan is-
> 
> 1. create new XCF and CFRM DR files (new LOGR and WLM for testing DEV at
> home but not at DR)
> 
> 2. update COUPLXX with new files
> 
> 3. shutdown LPAR1
> 
> 4. IPL LPAR1 with new COUPLxx and respond toinitialize new files
> 
> 5. Shutdown LPAR2 and IPL with new COUPLxx (no initialize)
> 
> Thanks,
> Elaine
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to