Re: File audit

-----Original Message-----
From: Dave Snyder <dsnyder@blcnet.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Wednesday, July 25, 2001 8:56 AM
Subject: File audit


>We had an update happen to a file yesterday that we do not know who did it.
Is there any audit trails with the AS400 that I can find out who did the
change? The file is not journaled.


Without journals, it's almost impossible to check. About the only thing
would be the job start and stop messages in the history log or a joblog from
the job itself, but in an interactive job, that's probably not much help.

If performance tools are running and collecting detail information, you may
be able to surmise the update from that, but it's unlikely that you would
actually be collecting details (transition data) during an update gone awry.
;-)

Just one more reason to journal. Remember, on other DB environments, it's
NOT an option, it's required and automatic. Hardware is cheap. Just add up
how much time and talent goes into exploring this problem.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - AS/400 Administrator
 -- IBM Certified Specialist - RPG IV Developer

"America is the land that fought for freedom and then
  began passing laws to get rid of it."

     - Alfred E. Neuman



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---