I am not sure you know you also have a serious alternative: do not share the DASD between the sysplexes, but keep the needed datasets (also PDSE's) in sync by synchronizing them periodically. We to this. Once a day, a number of PDSs, PDSE's and other datasets are unloaded at sysplex1, FTPed to Sysplex2 and loaded there. You can do this at your desired frequency.
If this solves your problem, it will be much less work than to merge the 2 sysplexes into 1. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dyck, Lionel B. (TRA) Sent: 04 April, 2016 19:46 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: Advice needed - GRS across 2 sysplexes with shared dasd Thank you - I've come to the conclusion that we should be in a single sysplex so we have grs protecting every device. Now the discussion begins :-) -------------------------------------------------------------------------- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI&T Service Delivery & Engineering -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joseph W Gentile Sent: Monday, April 04, 2016 12:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Advice needed - GRS across 2 sysplexes with shared dasd Hello Lionel, Regarding your OP, GRS ENQs are generally obtained at the GRS complex level, by various operating system programs and other applications that do I/O. GRS only knows about its own complex, not another GRS complex. In your description it sounds like you have two GRS complexes one for prod and one for test. The GRS complex usually matches the Sysplex unless you are using GRS Ring with GRS managed CTCs. The two complexes do not communicate ENQs between one another. If the two complexes collide on the same resource, data corruption can occur. Some resources can be safely shared outside the complex by using RESERVE. You can code the RNLs to exclude a resource from global processing and thus propagate the HW RESERVE. But not all applications doing I/O use RESERVE so this method is not sufficient protection, unless you know the resource is protected by RESERVE from product documentation. A CATALOG is one of those resources you can serialize with RESERVE and here is an info APAR that explains how to code your RNLs for that: http://www-01.ibm.com/support/docview.wss?uid=isg1II14297. Note that only protects the catalog from corruption and not the datasets themselves. RESERVE has its own risks, particularly a higher chance for contention, because only one system can own the RESERVE (which locks the whole volume) at a time. -Joe Joe Gentile z/OS GRS Lead jwgen...@us.ibm.com ---------------------------------------------------------------------- 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 ******************************************************** 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
