If possible, could you please give a little more detail.  What model of EMC 
DMX and what level of microcode?


Paul Feller
AIT Mainframe Technical Support


-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Dieltiens Geert
Sent: Monday, March 30, 2009 6:35 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: FW: IPL 190 hangs in zVM 5.4 - solved

Well, it seems that our missing interrupts were being caused by a bug in the 
EMC-microcode, in combination with z/VM 5.4.  Eventually, last Friday 
afternoon, it did kill our production (and me too, feeling better now, thanks).
Upgrading to the latest EMC-microcode apparantly fixed it.

But to be fair I must say this was the first time in 15+ years that the 
EMC-boxes caused a serious mainframe-related problem, and EMC-support was very 
quick to repair it.

If you're planning to be or already are running z/VM 5.4 on a multi-LPAR System 
z with shared dasd in an EMC Symmetrix DMX, then make shure you have that 
latest EMC-microcode.

Thanks,
Geert.

> ______________________________________________
> From:         Dieltiens Geert
> Sent: dinsdag 24 maart 2009 18:16
> To:   IBMVM@LISTSERV.UARK.EDU
> Subject:      FW: IPL 190 hangs in zVM 5.4
>
> An update:
>
> This seems to be related to missing interrupts for the volume(540RES) where 
> the CMS IPL minidisk resides.
>
> Almost exactly 5 minutes after I issued IPL 190, the IPL came through. Better 
> late than never :-) But the IPL worked eventually, which is quite a relief. I 
> repeated the IPL a couple of times, and every time I had to wait 5 minutes.
>
> The 5 minute interval is twice our MITIME interval for DASD (2 x 2 minutes 
> and 30 seconds). If I set MITIME to 5 seconds for volume 540RES then I always 
> have to wait 10 seconds before I get the CMS IPL-headermessage after an IPL 
> 190. That's quite a bit quicker than before it's not like it's supposed to be.
>
> So it seems that 2 missing interrupts have to be processed before the IPL 190 
> continues. I still have no idea what could be causing this...
>
> Bye,
> Geert.
>
> _____________________________
> Geert Dieltiens
> Systeembeheerder
> Informatica J. Van Breda & C°
> Tel.: + 32 3 217 50 16
>
>
>
> ______________________________________________
> From:         Dieltiens Geert
> Sent: dinsdag 24 maart 2009 16:35
> To:   IBMVM@LISTSERV.UARK.EDU
> Subject:      IPL 190 hangs in zVM 5.4
>
> Hi all,
>
> 10 days ago we activated z/VM 5.4 in production. All worked really well.
>
> But yesterday when I logged on MAINT I noticed that CMS didn't IPL. It now 
> seems that IPL 190 no longer works (in any VM-userid).  After entering the 
> IPL 190 command (or just logging on to MAINT) nothing happens.  From that 
> point on other users that issue IPL 190 or IPL CMS will hang as well.
> A LINK to a minidisk on the same volume (540RES) will hang as well. It seems 
> that the whole volume is being locked.
> We can solve the hang by issuing #CP IPL CMS in the machine where the IPL 190 
> was issued (IPL CMS still works fine). Other users can then proceed as well.
>
> When I do an IPL 190 in user MAINT, Performance Toolkit shows this for USER 
> MAINT:
>
>  ...
>  Device activity and status:
>  0009 3215   .0                          000C 254R      CL *, EOF    NOH NCNT
>  000D 254P      CL A, CO 01, NOH NCNT    000E 3211      CL A, CO 01, NOH NCNT
>  0112 3390   .0 B001,RR,  65Cyl,--->0    0123 3390   .0 B03C,WR,3339Cyl,--->0
>  0124 3390   .0 B03D,WR,3339Cyl,--->0    0125 3390   .0 B03E,WR,3339Cyl,--->0
>  0190 3390   .0 B03C,WR, 107Cyl,BUSY     0191 3390   .0 B03C,WR, 175Cyl,--->0
>  ...
>
> Please note that 190 is marked BUSY. It stays that way until I issue #CP IPL 
> CMS in user MAINT.
> I also tried an IPL 490 in user MAINT and that hangs as well.
> I copied MAINT 190 using DDR to another volume as minidisk A190 and issued 
> IPL A190 and that hangs as well.
> I then made this minidisk available to another VM-system, IPLed it, and that 
> works fine.
>
> Any ideas what's going on?
>
> Thanks,
> Geert.
>
> _____________________________
> Geert Dieltiens
> Systeembeheerder
> Informatica J. Van Breda & C°
>
>
DISCLAIMER

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify postmas...@vanbreda.be This 
footnote also confirms that this email has been checked for the presence of 
viruses.

Informatica J.Van Breda & Co NV BTW BE 0427 908 174

Reply via email to