Thanks to both for this additional info. Tom, You are correct that we require 2 for Global mirroring. The other 8 are for the Hyperswap which requires 1 pair(2) for each sysplex and we run 4 plexes.
Craig, I am beginning to believe this to be true. Do you happen to be doing this today? My concern is like what was pointed out earlier in the thread...RO commands won't work across the systems that run different security products. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Craig Pace Sent: Thursday, July 30, 2015 6:12 PM To: [email protected] Subject: Re: Different Security Products in a Sysplex This will not be a problem at all. Although you are in a Sysplex, you can still have separation with the LPARs themselves. You can have separate shared security databases, different vendors, separate DB2, JES, CICS, etc. The beauty of the Sysplex is the ability to share as much as you want or as little as you want. Craig -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Thomas Conley Sent: Thursday, July 30, 2015 17:22 To: [email protected] Subject: Re: Different Security Products in a Sysplex On 7/30/2015 5:11 PM, Givens, Dennis W. wrote: > I appreciate all of the input on my question. Here is additional information > that may help clarify.... > > We have an 8 LPAR sysplex. All are sharing a Top Secret DB. > We need to add 10 more to provide IBM GDPS Hyperswap and Global mirroring. We > would like these (due to political reasons) to use a shared RACF DB. > These new lpars will have limited system access by users and run a reduced > product set. > They will function as Control systems for the Hyper swap and Mirroring > functions for the sysplex. > > > Can these 18 systems function just fine in this configuration. > > I understand that commands will not work between the lpars running different > packages. We may be able to overcome this short coming. > Any more capabilities that will be impacted. > > Thanks in advance for any additional insight. > Dennis, No reason they shouldn't. If you're setting up Global Mirror, you should only need a controlling LPAR in the local datacenter, and a remote system in the remote datacenter. Not sure why you need 10 LPARs unless you have 8 LPARs processing data. I would recommend defining your sysplexes before introducing GDPS. Have you engaged IBM yet? Regards, Tom Conley ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ________________________________ This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN CNA SURETY voted the #1 Carrier for Surety Bonds by PROPERTYCASUALTY360 Survey NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
