Paul,
 
What I've been told by HP is that :FSCHECK's potentially destructive
commands - purgefile, checkdirc, checkextents, etc. - should never be
done on an active system.  Your session should be the only one, plus no
jobs, user logging processes, network processes, etc., should be
active.
 
The 'syncaccounting' command in :FSCHECK is supposedly the only piece
which may be used while the system is active - in fact, the RC did this
after installing an :FSCHECK patch via :DEBUG to fix a 'syncaccounting'
bug two weeks ago on both our systems.
 
We've used :FSCHECK frequently under these conditions, and have never
run into any problems except for the aforementioned 'syncaccounting'
problem.
 
Lee Gunter      503-375-4498        [log in to unmask]
HMO Oregon      503-375-4401  fax
==========================================================
The opinions expressed, here, are mine and mine alone, and do not
necessarily reflect those of my employer.
 
______________________________ Reply Separator _________________________________
Subject: Spoolfile 'stuck' . No more!
Author:  "Paul H. Christidis" <[log in to unmask]> at ~INTERNET
Date:    7/26/96 1:22 PM
 
 
Thanks to all who replied.
 
I tried your suggestions (all except calling a priest) but nothing worked.
The RC indicated that the only way to delete it was using 'fscheck' and do
it while there were *no* other processes on the system (something about
'fscheck' causing more corruption if not executing 'stand alone').
 
Well it turned out that we needed to install some tape drives on the system
yesterday and thus I used the RCs recomendation, and indeed the spoolfile
'is no more' thanks to the 'purgefile' command of 'fscheck'.
 
Thanks again
 
Regards
 
Paul H. Christidis
 
P.S.  Is 'fscheck' as 'dangerous' as the RC says???