From: Kees > > Probably not of much help, but do you mean with "the MCAT" the one and only shared MCAT for the entire sysplex? > > I have never understood the rationale of those constructs: first IBM invented sysplex to create a single system view on separate systems, that could be transparently upgraded, removed from, moved into the sysplex etc. And then they started introcuding single-points-of-failure, like shared MCATs, shared Parmlibs, Sysplex Root HFSs etc. etc. > > We still run with as little shared as possible between the members of our sysplexes. If you have a shared MCAT, you could consider using the planned activities to move to dedicated MCATs per system. >
Yes, this customer does run a shared MCAT - at my suggestion it should be noted. I happen to like the convenience, and this is only the second "glitch" I can recall. Due to some recent rearrangements, they no longer have any systems that run a "standalone" MCAT. That will be rectified next week when this issue is put to bed. In the interim I have two copies I can load at whim. Generally I don't have an issue with everything shared, but if something breaks, it gets reflected everywhere (mirrored systems, flashed backups, etc). Might indeed need some deeper cogitation. Cheers ... Shane ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
