Tried it, still went boom :( Does fixing this involve serious entanglement with the system debugger, or am I going to have to "bite the bullet" and arrange for a proper RELOAD? Ronald R Horner <[log in to unmask]> wrote in message news:8rv5ma021lu@enews4.newsguy.com... > A while back, I read something from this very listserver that using the POSIX rm > command would purge the file from your system. After reading it, I found a > corrupted file and followed the advice. It worked with out any system outage at > all. > > Later > > "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... [...] > > 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?]