Following Chuck's logic that this just does not happen, (see separate post) AND following the POGO paradigm that the enemy is usually "Us."  I'd look for a nightly batch job that deleting old files.  Probably by written by the System Manager when he was reading a VESoft manual.  It could have been written years ago and now the age of the files has probably crossed the job's line.

I don't have a problem with such jobs, one just has to be careful where it deletes from and what it is deleting.

Tracy Johnson
Office 1-757-766-4318
[log in to unmask] 
 

> -----Original Message-----
> From: HP-3000 Systems Discussion 
> [mailto:[log in to unmask]] On Behalf Of John Bawden
> Sent: Tuesday, September 15, 2009 7:53 PM
> To: [log in to unmask]
> Subject: [HP3000-L] Running FSCHECK in a job
> 
> We are having some very strange problems with files just 
> randomly disappearing with absolutely no reason that we can 
> determine. It has been recommended that we run FSCHECK with 
> the CHECKALL option to see what it shows for a possible 
> explanation or to rule out some areas. The file structure is 
> very large and we would like to run FSCHECK in a job since 
> all users have to be off and this would have to run on a 
> weekend night. But we have heard that there can be problems 
> doing this, up to a system crash, but no further explanation. 
> I've run FSCHECK with the SYNCACCOUNTING option in job mode 
> for several years on another system with no problems at all. 
> Does anyone know what problems there might be that are 
> related to the CHECKALL or has anyone experienced problems.
> 
> TIA for nay advice pro and con.
>  John Bawden 
> Homestead3000 Consulting 
> MPE Forever 
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *