We have defined in our policy both the CF's normally in use during Production and the CF that will be used in a DR. That way when the policy is replicated to the DR site all the information required is already present and we do not have to switch policies. In normal life a D CF command shows one unreachable CF and 2 active ones. During DR the opposite shows with the DR CF active and the 2 normal ones unreachable.
Jerry Whitteridge Delivery Manager / Mainframe Architect GTS - Safeway Account 602 527 4871 Mobile jerry.whitteri...@ibm.com IBM Services IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> wrote on 01/23/2020 12:39:56 PM: > From: Elaine Beal <elaine.b...@gxs.com> > 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 <IBM-MAIN@LISTSERV.UA.EDU> > > 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 following- > > IXC248E COUPLE DATA SET dsname ON VOLSER volser FOR typename MAY > BE IN USE BY ANOTHER SYSPLEX. > > IXC247D REPLY U to ACCEPT USE OR D TO DENY USE OF THE COUPLE DATA > SET FOR typename. > > to which both are replied to with U > > ISG379E GRS UNABLE TO CONNECT TO THE ISGLOCK STRUCTURE. VALIDATE > THAT THERE IS A COUPLING FACILITY DEFINED IN THE CFRM POLICY AND > THAT IT IS PHYSICALLY CONNECTED TO THE SYSTEM. ENSURE THAT THE CF IS > IN THE PREFLIST FOR THE ISGLOCK STRUCTURE. > > CF facility is same as prod and is defined in DR CFRM > CF is in PREFLIST > > one unusual thing is on my report for the DR CFRM > it shows both the prod policy and the new DR policy but not sure why > since I formatted a new CFRM > > The backup CTCs are in parmlib but could possibly not be connected. > should I remove those? > > Thanks, > Elaine > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
