The reason for the questioning is that there are PDSE's that are access from both sysplexes, since the dasd/catalogs, are shared that have gone bad. Adding more discipline on the access is one way and the other is to let the system manage the access.
-------------------------------------------------------------------------- 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:[email protected]] On Behalf Of Staller, Allan Sent: Friday, April 01, 2016 8:18 AM To: [email protected] Subject: [EXTERNAL] Re: Advice needed - GRS across 2 sysplexes with shared dasd Yes, you can configure GRS for all 4 LPARS. *DON'T DO IT* You are just asking for trouble...... GRS has *ALWAYS* claimed to have a scope of SYSPLEX. Which brings to mind, why are you (or anyone else) seeking to change this? <snip> Seeking advice on how to configure the system to allow GRS to manage all of our environment. Current config: 4 lpars 2 in prod sysplex 2 in test sysplex All dasd is shared Each currently has its own grs environment. I asked ibm l2 and was told I couldn't have grs manage all 4 lpars but was also told by a friend that it should be possible. </snip> This email ? including attachments ? may contain confidential information. If you are not the intended recipient, do not copy, distribute or act on it. Instead, notify the sender immediately and delete the message. ---------------------------------------------------------------------- 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
