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 > > > > >***************************** Disclaimer ***************************** > >The contents of this electronic message and any attachments are intended only >for the addressee and may contain privileged or confidential information. They >may only be used for the purposes for which they were supplied. If you are not >the addressee, you are notified that any transmission, distribution, >downloading, printing or photocopying of the contents of this message or >attachments is strictly prohibited. The privilege of confidentiality attached >to this message and attachments is not waived, lost or destroyed by reason of >mistaken delivery to you. If you receive this message in error please notify >the sender by return e-mail or telephone. > >Please note: the Department of Science, Information Technology, Innovation and >the Arts carries out automatic software scanning, filtering and blocking of >E-mails and attachments (including emails of a personal nature) for detection >of viruses, malicious code, SPAM, executable programs or content it deems >unacceptable. All reasonable precautions will be taken to respect the privacy >of individuals in accordance with the Information Privacy Act 2009 (Qld). >Personal information will only be used for official purposes, e.g. monitoring >Departmental Personnel's compliance with Departmental Policies. Personal >information will not be divulged or disclosed to others, unless authorised or >required by Departmental Policy and/or law. > > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
