I've already tried the Halt on all of our tape drives. No change. And I can't IML the tape controller due to one of the drives being used for log tapes.
Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 12/19/2005 11:27 AM >>> Tom, Try issuing a CP HALT to the *real* tape drive addresses that "broke" from your first level system. My guess is that there is a pending I/O for the VSE guest to one of the broken tape drive that is preventing the guest from being FORCED/LOGGED OFF ... JR Imler JR (Steven) Imler Computer Associates Senior Software Engineer Work: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] [EMAIL PROTECTED] -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Monday, December 19, 2005 12:21 PM 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
