As for the method of freeing the userid, the trick was to change the userid in the hung VMBLOCK. That method quit working when hashing was introduced. I think that was done with VM/XA. If you try it on a modern system, you are almost guaranteed that you will experience an unplanned outage.
-----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Monday, December 19, 2005 9:21 AM To: [email protected] 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
