On Mon, 10 Sep 2007 17:38:05 -0400, Hooker, Don <[EMAIL PROTECTED]> w rote:
>It's been *so* long since I've seen users stuck in "Logoff/Force >Pending" state for any length of time that I thought it had been fixed. >We have a z/VSE guest stuck in that state since Sunday. > >Anybody else seen this on current levels of z/VM? > >Many years ago when it was a more frequent problem, I wrote an assembler >program that massaged some bits in the (then) VMBLOCK to free it up. I >did not take some things into account at the time, so sometimes it >worked, but then othertimes... <expletive deleted> > >Does anybody have any current tricks to free up a user in this state >(short of VM IPL). >======================== ========================= ========== ============= Yes, we had several hung users last week. ESASERVE & ESAWRITE & a nyone that issued CP MONITOR or VARY OFF. To quote my colleague, Dennis O'Brien: Could this problem be an occurrence of the problem described in VM64184? A dynamic HCD activation was done an hour or two before the problem started, and I believe the DASD ports were unblocked just before it started. I'm still waiting for confirmation on that. The HCD activation moved the 7000-77FF addresses from one DASD subsystem to another, and also changed some of the addresses from aliases to base volumes. After the activation, some of the responses from QUERY PAV are erroneous, e.g. "Device 7059 is an alias Parallel Access Volume device whose base device is 7059" We sent IBM a SNADUMP and they determined that Dennis was right, it was A PAR VM64184. We installed the PTF to z/VM 5.2.0 over the weekend and so far no recurrence . We have a long-standing policy of always attempting to document and repor t hung users to IBM. We think that has helped IBM improve the situation, and thank everyone el se who has done the same! I know of no good tricks in this case, only a VM IPL would clear the hung users. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
