fscheck shouldn't be run while your network, processes, users etc are
     on the system because it would give a false indication of directory or
     label corruptions. You don't want to run commands like checkdirc,
     checklabel, checkextents and especially purgefile or unlockfile with
     other users still using those files.
 
     If you've got users on, you can still look for directory or volume
     corruptions by running checkdirc or checklabel with the ;IGNORE
     option. You would then wanna ignore those files with labels like
     $000000 since these are temporary files.
 
 
     ----
     YuHsin
 
 
______________________________ Reply Separator _________________________________
Subject: Spoolfile 'stuck' . No more!
Author:  Non-HP-HP3000-L ([log in to unmask]) at HP-Singapore,uugw30
Date:    7/27/96 5:22 AM
 
 
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???