Agreed, way too much risk.   We don’t swap master cat's at all either.  No 
reason to, except maybe those shops that cannot fit the entire SYSRES on one 
volume, so you have the issue where DSN A is cataloged on the first volume of 
the set pre-upgrade, and post-upgrade it got placed on a different volume.  We 
solved that years ago by using mod-27's as sysres, and now mod-54's.

_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
[email protected]
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Jesse 1 Robinson
Sent: Monday, November 28, 2016 4:57 PM
To: [email protected]
Subject: Re: Catalogs in a SYSPLEX

As noted earlier in this thread, sysres datasets should be cataloged with 
volser ****** and unit 0000. That tells the system to look on the currently 
IPLed sysres regardless of volume name. 

BTW I don't subscribe to the floating MCAT strategy. Our master catalog lives 
away from sysres and therefore does not change on sysres swap. We've done this 
forever and don't see any serious problems. And you don't need multiple MCATs 
during upgrades as long you always call LINKLIB 'SYS1.LINKLIB'.  

.
.
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
[email protected]


This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to