Hello Crispin,

I agree.  Thanks for all your info and knowledge.  

Ed Martin
Aultman Health Foundation
330-588-4723
ext 40441

From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Crispin Hugo
Sent: Friday, January 23, 2009 4:13 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DS6800 concurrent microcode updates

THE sea.jar IS THE ONLY ONE WHERE you need to have system down. That
means about 1.5 hours out. As each processor is updated seperatly , then
the power failure scenario does not occur.
I suggest that for the first time, you get everybody off BUT don't shut
system and see what happens. Just have bare VM and VSE running.  

Crispin Hugo
Systems Programmer, Macro 4
<http://www.macro4.com/>
Macro 4 plc, The Orangery, Turners Hill Road, Worth, Crawley, RH10 4SS
Direct Line: +44 (0)1293 872121 Switchboard: +44 (0) 1293 872000
Fax: +44 (0) 1293 872001
This message contains confidential information and is intended only for
the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
contain viruses. The sender therefore does not accept liability for any
errors or omissions in the contents of this message which arise as a
result of e-mail transmission. If verification is required please
request a hard-copy version. This message is provided for informational
purposes and should not be construed as a solicitation, offer or
acceptance of any offer.
                -----Original Message-----
                From: The IBM z/VM Operating System
[mailto:ib...@listserv.uark.edu] On Behalf Of Edward M Martin
                Sent: 23 January 2009 21:09
                To: IBMVM@LISTSERV.UARK.EDU
                Subject: Re: DS6800 concurrent microcode updates

                Hello Crispin Hugo, Mace (Larry Macioce), and Tom
Duerbusch,
                Thank you for the info.  I am on both z/VM 5.3 and z/VSE
4.1.2.  I tried to wire the two racks to all have a path if we lost
                Full connection.
                It is the two hours that worry me.  I get Tuesday nights
here at the Hospital.  And as long it works.
                So what is your backup plan?  What happens if you get a
power failure in the middle of the update?
                Yea, I know UPS but I have to plan for worst case.   Say
in your best Germany accent 'WE WILL NOT FAIL!'  (sorry Martin) 
                Crispin, you have indicated the 3 updates.  I see the
SEA.JAR that I believe will update the microcode in the DS6800,
                I see the DS6800STorageManager_WIN_5.2.200.1678.zip (for
the Windows version of Storage Manager), and 
                DSCLI_5.2.2.411.tar.gz and DSCLI_5.2.2.411.zip  which I
thought was the Data Storage Command Line interface.
                Are these the three that you updates you are talking
about?
                Because it would be ok to get the SEA.JAR done and the
do the Windows  Storage Manager as the system runs.
                Ed Martin
                Aultman Health Foundation
                330-588-4723
                ext 40441
                From: The IBM z/VM Operating System
[mailto:ib...@listserv.uark.edu] On Behalf Of Crispin Hugo
                Sent: Friday, January 23, 2009 3:32 PM
                To: IBMVM@LISTSERV.UARK.EDU
                Subject: Re: DS6800 concurrent microcode updates
                Our experience with VM and Z/os is that they may not
survive. It appears to me to that it drops the second connection too
soon after the first one is put back online.
                We always close system down.
                With our system it takes about 2 hours to do all three
software updates
                Crispin Hugo
                Systems Programmer, Macro 4
                <http://www.macro4.com/>
                ____________________
                
        
________________________________________________________________________
                This email has been scanned for all known viruses by the
MessageLabs Email Security Service and the Macro 4 plc internal virus
protection system.
        
________________________________________________________________________

________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs
Email Security Service and the Macro 4 plc internal virus protection
system.
________________________________________________________________________

Reply via email to