Just a minor point about logging, Keven eluded to it.
System log events 105 and 160, report a file closure. So if the process was closed with a disposition to purge the file, it can be seen in the log files.
However, if someone logs on to the command prompt and simply purges the file, I doubt there will be any trace in the system logs.
-Craig
--- On Wed, 9/16/09, Legault, Raymond D <[log in to unmask]> wrote:
> From: Legault, Raymond D <[log in to unmask]>
> Subject: files just randomly disappearing
> To: [log in to unmask]
> Date: Wednesday, September 16, 2009, 7:44 AM
> Do you have system logging
> turned on for file close?
>
> Allegro has a program that will allow you to toggle the log
> file settings.
>
> http://www.allegro.com/software/hp3000/allegro.html
>
> The also have Filerpt.
>
> FILERPT is a log file analyzer. It has since been
> superceded by the REDWOOD Tool, but this version is free.
> Its main focus is on "File Close" records.(LZW), (std),
> (Plain text information.)
>
> I also have a program that can read the log files searching
> for job or session number, or
> Filename or logon or console. Is this program we should the
> file disposition. A 4 means purge.
> So if you know the file name and time period that is was
> purged, this can show you what program and
> Session purged the file. If you want my LOGXL program, let
> me know what format you need it in? ( Wrq, Std )
>
> Logxl
>
> B.C.S. MPE-XL Y2K Logfile Analyzer Version 1.4 WED,
> SEP 16, 2009, 5:39 AM
>
> Enter Group.Acct for Log Files (Return=Pub.Sys)?
> How do you want to access the Logfile? by:
>
>
> 1. Session/Job Number.
>
> 2. Logon.
>
> 3. File Name.
>
> 4. Console.
>
> Enter your choice by Number.
>
>
> Ray
>
> -----Original Message-----
> From: John Bawden [mailto:[log in to unmask]]
>
> Sent: Tuesday, September 15, 2009 4:53 PM
> Subject: 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 *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
