A lot depends on whether you're creating a net new member or combining two existing systems into a single plex. As I said in a previous thread, combining systems is very tough unless you're willing to put up with the vagaries of a 'bronze-plex'.
If you're creating a new system, you can clone the existing one. You should aim to share everything that can be shared. I don't know why anyone would stop short of total sharing: one master catalog; one RACF (or other security product) data base; one JES spool. If someone can give you a compelling reason for separate anything--like page data sets--then you could consider it. I would be very dubious about proposed subdivisions. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Travis Sent: Monday, November 21, 2016 12:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Catalogs in a SYSPLEX We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared master catalog or multiple master catalogs on each system. The IBM manuals recommend a single shared master catalog but our CE has been advocating multiple catalogs. What are the pros and cons of running each? We have two identical systems in the PLEX and for right now there is no plan to add more, however that could change at any time in the near future. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
