I think the issue is a catalog shared between PLEXs and not a catalog that is shared within a Plex. GRS maybe tricky when more than one Plex can access a catalog.
Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of van der Grijn, Bart (B) > Sent: Friday, June 12, 2015 5:27 AM > To: [email protected] > Subject: Re: Share IODF in different sysplex same CPC > > Seeing that I originally suggested using a shared catalog in this thread, I > have > to ask why people believe this is a dangerous setup for the topic at hand. > Yes, there are potential issues with sharing catalogs, but with the suggested > configuration (single dedicated volume, single HLQ, single catalog, IODF only) > I'm just not seeing what the issues are. Can those that dubbed this > dangerous enlighten me? > > We've used this setup for longer than I can remember in multiple > environments and I don't recall it ever causing an issue. > The advantage is that your IODF datasets are always the same across all your > environments without having to rely on a manual sync-up. Note: we switch > to a new IODF every time we make updates > > Thanks, > Bart > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jorge Garcia > Sent: Friday, June 12, 2015 2:46 > To: [email protected] > Subject: Re: Share IODF in different sysplex same CPC > > Hello: > > I've reviewed all the post and the best option is the HCD export/import in > the productions monoplex. If all the IODFs have the same HLQ yoy can do > dynamic activation and it' no necessary to do a ipl. The user catalog among > sysplex is dangerous. I agree with us. > > Thanks for your posts!! > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
