Our experience was you are correct zero down time except we ipl bi-weekly. The driver was put on concurrent during the week but took 3 hours a processor to install, CE had to baby sit ;) We then ipl'ed (even though im pretty sure we didnt have to) to change the clock member for STP. We did it all in the same weekend.
Andy Internet: Mailto:[EMAIL PROTECTED] "IBM Mainframe Discussion List" <[email protected]> wrote on 08/13/2007 08:53:37 AM: > Bert, we're told it is a concurrent update. Hard to do better than zero > as downtime. > > > Cheers,,,Steve > > Steve Conway > Lead Systems Programmer > Information Systems & Services Division > Computer & Network Operations > Phone: (703) 450-3156 > Fax: (703) 450-3197 > > > > > To > [email protected] > cc > > Subject > Re: z9 DRIVER 67 > > > > > > > Hi there, > We are also planning to upgrade to driver 67. > I understand the time needed for an upgrade, 3 hours, is rather a lot for > this > action. > Has anyone tried to install 67 on the secondary SE in advance and restart > the > machine while making the sec SE primary ? > By using this method, the downtime will be less. > > hope to hear from you all. > Bert > > ---------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. ---------------------------------------------------------------------- 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
