On Tue, 11 Sep 2007 10:56:21 -0400, Hooker, Don <[EMAIL PROTECTED]>
wrote:
>And Alan, I guess I'm glad to know we're not alone. I will look up
>VM64184.
>It is for z/VM 5.2?
Both z/VM 5.2 and 5.3.
APAR Identifier .. VM64184 Last Changed 07/08/30
HUNG USER AFTER VARY ON C
Thanks for the replies. And thanks for the TRACK commands, Mike. I use
TRACK all the time but mostly for viewing consoles. TRACK shows an
active I/O to a VSWITCH connected to an OSAX. I am reluctant to do a
HALT on that device as I do not know if it would impact other users of
the VSWITCH.
And
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
A "Logoff/Force Pending" state means that something unexpected happened. For years whenever a new
cause was discovered IBM has added a test for that condition and does something about it. That is
why they have gotten fewer and fewer. Apparently you found another unexpected condition. So call IBM
e the SNAPDUMP for analysis.
.cm Last updated 2007/01/04 mrw
"Hooker, Don" <[EMAIL PROTECTED]>
Sent by: "The IBM z/VM Operating System"
09/10/2007 04:38 PM
Please respond to
"The IBM z/VM Operating System"
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
&qu
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
