On Wednesday, 01/25/2006 at 10:24 EST, Mark Bodenstein <[EMAIL PROTECTED]> wrote:
> But since the Shark supports CUIR (Control Unit Initiated > Reconfiguration), shouldn't VM be able to get through this kind of > Shark microcode upgrade without operator assistance? > > We went through a Shark microcode upgrade a while ago when we were > running z/VM 4.3 and z/OS 1.4 in separate LPARs on a 9672 with Shark > DASD. We had a similar channel setup - one CHPID per Shark host > bay. MVS got through the upgrade with no operator intervention, but > VM needed some help. If I remember correctly VM responded fine as > each CHPID was being taken offline by the control unit, but needed us > to do something when they came back online. Also if I remember > correctly z/VM 4.4 was supposed to have an improvement over 4.3 in > CUIR support? There have been 9 PTFs related to CUIR since we first introduced the function, so be sure to get current with service. Also make sure your Shark microcode is current. If it were *my* production system, I would use the more traditional method I described in my previous post and would not depend on CUIR as a planned outage tool. I would work with it in my test LPAR. Alan Altmark z/VM Development IBM Endicott
