I maintain a production sysres that is not a part of the maintenance system. This disk does not have to be replaced when the release or version of VM changes. It has the Parm disk, the object directory, the checkpoint and warm start areas on it. When I am ready to put a new CP in production, I simply rename the current CPLOAD MODULE that in on the PARM disk, calling it CPOLD, and copy the new module to the disk. It is always a good idea to keep the old nucleus, changing its name but retaining the filetype MODULE. That makes fallback easy, you simply IPL the previous nucleus.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Tobias Doerkes > Sent: Thursday, February 07, 2008 6:31 AM > To: [email protected] > Subject: Anybody using a multi-sysres concept for maintenance? > > hi list, > > is there anybody out there using a multi-sysres-concept for > activating maintenance? we are a mvs shop. so i would like to > adopt some processes f= or maintaining vm. normally we build > up a sysres in our maintenance environment. after some > testing we deploy this sysres to all systems/sysplexes and > bring it up by ipling the image. parameters, ckpt, = etc are > separated from the sysres. > > i would like to share my thoughts and code to perform this > process automa= ted. > > regards, > > tobias. >
