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> On Thu, 30 Nov 2006 15:55:48 +0100, R.S. <[EMAIL PROTECTED]> wrote: >Chase, John wrote: >>> -----Original Message----- >>> From: IBM Mainframe Discussion List On Behalf Of R.S. >>> >>> Tom Marchant wrote: >>>> On Thu, 30 Nov 2006 15:05:27 +0100, R.S. wrote: >>>> >>>>> Tom Marchant wrote: >>>>> [...] >>>>>> I _strongly_ suggest that you move SYS1.PARMLIB off the IPL >> volume. >>>>> Why ??? >>>> So that you don't have to be concerned about keeping myltiple copies >> >>>> of SYS1.PARMLIB in sync. >>> OK, however keeping *single* copy of PARMLIB on IPL volume is >>> not a problem, am I right ? >> >> If you have only one "IPL volume", you're right. But then, how do you >> apply maintenance, or implement z/OS upgrades? >> >> If you have two or more "IPL volumes" for a given z/OS image, the >> implication is that you also have two or more instances of SYS1.PARMLIB >> which you must keep synchronized to avoid astonishment when IPLing from >> one of the alternate "IPL volumes". > >I don't keep my PARMLIB on IPL volume. However I was curious why it's >not recommended. The above reason sounds reasonable <g> >However I don't see a problem in simply overwriting the PARMLIB when >change IPL volume. ---------------------------------------------------------------------- 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
