Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!TWSUVM.BITNET!ANDREWS
From: ANDREWS@TWSUVM.BITNET (Chris Andrews)
Newsgroups: comp.lang.asm370
Subject: Re: DMKnia361E LOGOFF/FORCE pending for user CACZ0200
Message-ID: <9002161600.AA03406@lilac.berkeley.edu>
Date: 16 Feb 90 15:19:11 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.bitnet@lilac.berkeley.edu>
Distribution: inet
Organization: The Internet
Lines: 18

You're right. This is probably not the right list for this, but ...

You can be left in the FORCE/PENDING state for many reasons,
such as a pending i/o when your machine was logged off (or forced).

There are programs out on the network that will "unhang" a stuck user.
Have your system programmer get the "UNHANG" package from one of the
VM-UTIL listservers.  It can only be run from a privileged machine, and
your system programmer may be leery of using the package to unhang you
with only two days until an IPL. The program makes changes in the real
system, and although I've never crashed the system using it, there is
always the possibility that using this could bring you down (but then
your signon would be free, wouldn't it ?).


Chris Andrews
Systems Programmer - VM, VTAM
(The) Wichita State University