"Emerson, Tom # El Monte" wrote:
>
> That header just about says it all: we have a system failure each day when a
> "cleanup" job hits a certain spoolfile -- fscheck dutifully indicates
> corruption in the file label, and the ";FIX" option seems to have no
> effect...
>
> [and yes, purging the file via fscheck ALSO crashes the system]
...
>> Now, the $64 question: how do I get rid of that file short of a reload?
> [there's another file that fscheck reports an error on as well, but it's not
> a spoolfile -- it's a data file in a test group/account, so would purging
> the group "clean up" this file or is it likely to trigger the failure as
> well?]
>

I hope you are on RC support, if not they may be able to
help you on a time & material basis.

A knowning engineer could dialin and mark the file label(s)
as un-used/free and then run FSCHECK to delete the relating
directory entry. Another reboot and all should be ok, then.
The disadvantage of this method is that you will 'loose' the
disc space that the extents of this file used. How bad that
is compared to rebuilding a volumeset depends on your own
judgement.

Good luck,
Götz.