On Tue, 2 Jan 2007 14:58:02 -0500, Jakubek, Jan <[EMAIL PROTECTED]> wrote:
>>And in our case, (just getting ready to install 1.7 into production) >>we went from mod3 to mod 9 volumes for our opsystem packs. >>I don't see how you can easily get away with not building a new master >>catalog. > >The way I did it: > >&SYSR2 = &SYSR1 >&SYSR3 = &SYSR1 > >(via IEASYMxx setup for a new mod9 sysres) >and kept my old master catalogue. > Exactly. Then sometime after all your systems are migrated you can change the &SYSR2/&SYSR3 catalog entries to &SYSR1 or ******. I haven't built a new master catalog to facilitate an OS upgrade since MVS/ESA V5 (I have built them for other reasons). Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - GITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
