Tom,
A little "HUNGUSER STD" file that I keep around for when such awful things
pop up. If I actually remember to use it, then we're one step ahead in
getting useful doc for IBM. This material is included in the session I
present at SHARE, called "z/VM Installation - It's Installed, NOW What?".
Suggestions welcome...
Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.
HUNGUSER STD Z1 F 80 Trunc=80 Size=63 Line=0 Col=1 Alt=0
====>
|...+....1....+....2....+....3....+....4....+....5....+....6....+....7...
* * * End of File * * *
When a userid becomes hung with LOGOFF/FORCE PENDING, the following
alternatives may be tried, some require more than class "G" privs:
- If you have the time, simply waiting 15 minutes for CP to perform
housecleaning chores might free the userid, completing the LOGOFF
or FORCE.
- Use the public domain utility "TRACK" to determine if the userid is
awaiting completion of an I/O to a particular unresponsive device.
Use the commands:
TRACK hungid DEV CLASS * IO PENDing
TRACK hungid DEV CLASS * IO ACTIVE
Note bene: As of June 2003 TRACK can be obtained from:
http//vm.marist.edu/track
- Sometimes a simple message frees up the "hungid" without further ado.
From a privclass A, B, or C userid, issue:
CP WNG hungid Hello
- If you can (consider communication time-outs which may occur that
could affect other users) before muddying the waters, get a current
system dump for IBM to diagnose later. From a privclass "A' user:
CP QUERY DUMP (then ensure that it is going to disk)
Then: CP WNG ALL This system may be non-responsive for a few minutes
while diagnostic information is obtained.
Then: CP SNAPDUMP
- If the ID was awaiting I/O to a terminal, simply connecting from a
working terminal may free the ID. From a free terminal, issue:
CP LOGON hungid HERE
- For users logged on via TELNET terminals, issue:
NETSTAT TELNET
Find the matching tn3270 connection, and issue:
NETSTAT DROP conn_num
- "CPHX" is reported to cancel pending CP commands: ATTACH, LOCATE,
LOCATEVM, and VARY ONLINE|OFFLINE (see HELP for more detail).
From a privclass "A" userid, issue:
CP CPHX hungid
- If TRACK (above) showed an active I/O which cannot be remedied
(e.g. by making a tape drive "Ready"), the I/O may be able to be
cancelled. From a privclass "A" userid, issue:
CP HALT rdev
Due to queued I/Os or recalcitrant devices, HALT may need to be issued
repeatedly until the following message is received:
Halt was not initiated to tape nnnn because the device as not active
- If nothing freed the hung user, open a Problem Management Report with
IBM, and provide the SNAPDUMP for analysis.
* * * End of File * * *
"Tom Duerbusch" <[EMAIL PROTECTED]>
Sent by: "VM/ESA and z/VM Discussions" <[email protected]>
12/19/2005 11:20 AM
Please respond to
"VM/ESA and z/VM Discussions" <[email protected]>
To
[email protected]
cc
Subject
forcing a user
Hopefully this won't get to any point where I have to take drastic
action....
We have an old VSE machine (VSE/ESA 2.3.2), which somehow got hung
this
weekend. My best guess is that it hung when one of our tape drives
broke, but I can't be sure it was using them.
I have the "forced logoff pending" stuff.
Yep, tried:
force guest
force guest logoff
force guest logoff immediate
force guest immediate
Tried logging on.
There are no tape drives currently attached to the system, but someone
may have detached them earlier.
My plan was to wait an hour and see if it clears up. Well, times up.
There was a method, in the old days, that you modified some bits in
some control block and you can free up the user. Does anyone have
that
procedure, updated for z/VM 5.1 (RSU 501)?
Any other advice would also be welcome.
Tom Duerbusch
THD Consulting
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient is strictly prohibited.
