My experience too with PUT2PROD is that it can be disruptive, sometimes doing disruptive steps that aren't needed for the software product that's being serviced.
In some cases, to avoid unnecessary outages follow the software product's Program Directory VMSES service steps instead of using PUT2PROD. -------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Thursday, March 22, 2007 2:28 PM To: [email protected] Subject: Re: How are you handling z/Linux Only fixes to the CP nucleus need an IPL of VM. Everything else can be done by recycling selected virtual machines. But, then you need to know somewhat more of VM than "PUT2PROD" (I never used it, it is too disruptive in my eyes). We have for example two copies of the CMS resident, so we can update CMS while everything goes on. To place the new levels in production, we only swap the minidisk addresses of the two residents. e.g. MAINT 190 and MAINT 193 are the active CMS, 490 and 493 the alternates swapping levels is simply changing the addresses of those two minidisk sets Users logging on after the swap use the new CMS, others continue with the old one, one can recycle servers one by one for those you want to use the new level. (it is a bit more complicated as CMS also has saved segments, we make their name unique too) -- Kris Buelens, IBM Belgium, VM customer support
