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.
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
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
