On Thu, 30 Nov 2006 11:51:20 -0600, Matthew Stitt <[EMAIL PROTECTED]> wrote:
>I find it to my advantage to keep SYS1.PARMLIB on the IPL volume. I catalog >it with VOLSER of ****** so I can find it on whichever volume I IPL from. > >I also don't change or put anything into it that IBM did not provide when >the system was installed. Since I have multiple systems, each system has an >individual PARMLIB on a specific volume which contains the modified stuff. >And that one is concatenated ahead of SYS1.PARMLIB. > >As many on this list know, each one has their way of doing things and their >reasons for doing things that way. YMMV. <g> > That's good as long as the "SYS1.PARMLIB" you are referring to is the one that ServerPac ships as SYS1.IBM.PARMLIB (some call it IBM.PARMLIB) and is the one that the PARMLIB DDDEF points to (on a maintenance sysres of course) in SMP/E. If it isn't your SMP/E target parmlib then there is no advantage or reason to keep it on the sysres volume. 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
