Subject: | |
From: | |
Reply To: | |
Date: | Wed, 18 Aug 1999 16:51:24 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Nick Watson wrote:
> I have had a user stuck logged on since last Thursday. I have tried aborting
> the session and aborting everyone at osops.live but this user below still
> shows as it is logged on.
> #S5807 EXEC 84 84 THU 8:01A AW647,OSOPS.LIVE
Another possibility: perhaps the files the user has open are waiting for
some other process to complete before they will let the abortjob
proceed.
Doing a SHOWPROC JOB=#S5807 is probably pointless once the abort process
has started, because the 'parent' process has been killed and the system
is just waiting for the now orphaned 'child' process(es) to die before
logging off. You'll get back a message like this:
No processes matched any specification. (CIERR 11504)
However, there's more than one way to skin a cat, and *if the session
still has files open*, and you have MPEX, you should be able to see
this. Try:
:MPEX.PUB.VESOFT
%SHOWPROC #S5807;FORMAT=FILES
This will show you all files still opened by this session, their PIN
numbers, and lots of other useful info about the state of the files in
question. If you do a LISTFILE,9 on all the files listed, you *may* find
the culprit. Otherwise, if you're desperate (and extremely daring), you
could try using Allegro's free XCLOSE utility, which you can download
from their web site at <http://www.allegro.com/software>. *Warning*
XCLOSE could crash your system (according to the documentation).
HTH,
Patrick
--
Patrick Santucci
Technical Services Analyst
KVI, a division of Seabury & Smith, Inc.
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Alcohol and calculus don't mix. Never drink and derive.
~ Anonymous (but sounds like Wirt Atmar)
|
|
|