If you've run for some time with these systems sysplexed, you--and your user community--may be surprised at the functionality you will lose. I'm sure that you have good business reasons for dismantling the sysplex, but there may be less disruptive alternatives. For example, some time ago we bolted together two formerly separate sysplexes. They run independently in may ways, including separate JES2 complexes and RACF data bases, but they share a common GRS environment. Now this happens to be a parallel sysplex with coupling facility, but you may have options within a basic sysplex as well.
. . 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: Scott Fagen <[email protected]> To: [email protected] Date: 09/04/2012 08:46 AM Subject: Re: Remove a system from a SYSPLEX but keep it in the GRS ring Sent by: IBM Mainframe Discussion List <[email protected]> It can be done, you need to define and connect CTCs between all the non-sysplex system(s) and the sysplex systems (see GRSCNFxx http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.ieae200%2Fgrscnf.htm ). If you don't fully interconnect the non-sysplex system(s) with the sysplex, there is a potential for creating situations where only a subset (or none) of the complex will continue when a system leaves the ring (you can read about that in Planning: GRS, http://publib.boulder.ibm.com/infocenter/zos/v1r12/topic/com.ibm.zos.r12.ieag400/oldsplx.htm#oldsplx ). Adding non-sysplex systems to the GRS complex also turns off a bunch of sysplex-exclusive goodies while those systems are active in the GRS complex, e.g. fully automated recovery from system failures and dynamic RNL changes, implying you have to design and implement local processes to deal with those events. Scott Fagen Chief Architect - Mainframe CA Technologies On Tue, 4 Sep 2012 16:12:03 +1000, Gregory Peck (CITEC) <[email protected]> wrote: -snip- >Any real world experiences on bringing up a system that was previously part of a basic SYSPLEX, >whilst keeping it in the same GRS ring as the other SYSPLEX members? -snip- >Any obvious gotchas from the GRS point of view? > >Thanks, >Greg ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
