On Tuesday, 01/24/2006 at 05:00 PST, Randy Dray <[EMAIL PROTECTED]> 
wrote:
> Last night we had IBM upgrade the code on our 800ESS
> Shark.
> 
> 
> The statement was this would not be a service
> impacting upgrade.
> 
> all the CHPIDs upgrade fine for our open systems stuff
> but when we got to all my VM CHPIDs VM crashed.

You probably interrupted 

> I am looking for a way to vary offline the CHPIDs that
> that we need to upgrade.
> 
> 
> CHPID 14, is host bay 1
> CHPID 15, is host bay 2
> CHPID 16, is host bay 3
> CHPID 17, is host bay 4
> 
> IBM said that he thought the operating system zVM 4.4
> should have been smart enough to switch over due to
> the multiple paths into the system.

IBM?  There is a bit of confusion.  The I/O subsystem will select an 
available path automatically, but once chosen, a failure in the chpid will 
result in an I/O error.  Depending on what part of CP was performing the 
I/O, it may be critical (i.e. paging).  So you can't yank the cables 
(physically or logically) *VM is using* out from under VM without warning. 
 First you must quiesce CP I/O to the affected path (chpid).  This is done 
by VARY OFFLINE PATH nn FROM ALL.  If you don't do that, then CP will 
start I/O operations on any available chpid.  CP just removes the chpid 
from the Logical Path Mask (LPM), but leaves the chpid in place.  The LPM 
is what tells the channel subsystem what chpids it can use to start an I/O 
operation.

Then perform your host bay update, then VARY ONLINE PATH nn TO ALL.  Then 
proceed to the next chpid and the next bay update.

(*Some* device errors will cause the channel subsystem to retry the I/O on 
its own.)

> QUESTION:   Can I issue a Vary OFFLINE CHPID nn Force,
> then will it automatically switch over to another
> chpid.  When all the maintanance is done, Vary ONLINE
> CHPID NN to get it back.

This is evil.  You will deconfigure (but not remove) the chpid from the 
LPAR, effectively killing any I/O in flight.  That can result in the same 
abend you got before.

Taking the chpid offline is not necessary unless directed to by device 
service instructions.  The only device I know of that gets benefit from 
taking the chpid offline is the OSA.  When all OSA chpids go offline, the 
device reIMLs itself.  I mean, it doesn't *hurt* to take the chpid 
offline, but it typically doesn't help you, either.

Alan Altmark
z/VM Development
IBM Endicott

Reply via email to