I do not use the distribution disk as my sysres. Putting the new CP in place merely requires that the CPLOAD MODULE be made available on the PARM disk. Whenever I put a new module on the disk, I rename the existing file first. That way, the fallback module is right there and can be used simply by entering its new name in the SALIPL screen. Post fallback renaming to make it CPLOAD is needed if it is to remain the default for any amount of time.
Another advantage to doing it this way is that you do not have to update the Operators' Procedures. The IPL keeps the same volser and device address forever (or at least a very long time). So far, I have had to change the device address twice in 6 or 7 years I have been doing VM at this shop. Both were caused by hardware upgrades. The volser has been a fixture. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Le Grande Valerie > Sent: Wednesday, June 24, 2009 12:42 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Maintenance "Hot Standby" > > I am looking for some input: > > How do you do maintenance and keep a "hot standby" volume > (and old 540RES= > > and newly maintained 540RES)? > We have to bring maintenance in "off hours" and like to have > a volume operators can switch back to should there be problems. > > If anyone can share how-to, please contact me off list (or > copy me on the= > > list entry - I can't get to the list from my current work location). > > Valerie Le Grande > valerie.legra...@sentry.com >
