We currently have a 2 LPAR sysplex and the master catalog in not shared.  Prior 
to this job I worked at a shop where we supported sysplexes from a single 
system to up to 10 LPARs in a single sysplex.  The master catalogs were not 
shared , I think I would put forth one big reason for not sharing the master 
catalog, would be system upgrades, when we went through the z/OS upgrades, 
there were times where SYS1. Level data sets location changed from one release 
to the next and the catalog needed to point to the new location for the new 
release.  We would upgrade one LPAR at a time in a sysplex, which was once a 
week, so it would be several weeks to complete a sysplex.

I think there are a lot of questions you have to ask yourself about how you are 
going to handle the sysplex and what you are going to keep in the master 
catalog, besides SYS1.  Note: I believe System Symbols are your friend when 
setting up the catalog, for both data set names and VOLSER.


Al Nims
Systems Admin/Programmer 3
UFIT
University of Florida
(352) 273-1298

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Travis
Sent: Monday, November 21, 2016 3:54 PM
To: [email protected]
Subject: 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 
[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

Reply via email to