Re: Data Audits

["Carl Pitcher" <cpitcher@xxxxxxxxxxxxxxxxx>]

While journalling has it's place, I find it a cumbersome tool for monitoring
changes to files.  However, triggers are, in my experience, a good method to
direct before/after, inserts and delete information to an "audit" file for
additional reports or inquiries.  My technique has been to create an audit
file that includes all of the "important" fields that I need to track plus
the trigger insert, change or delete code, user id, timestamp, etc.  It
works quite well for tracking changes to our customer, item and pricing
files.  If you need the actual code, let me know and I'll zip you a copy.

----- Original Message -----
From: Mark Bennett <mbennett@clover.co.za>
To: <RPG400-L@midrange.com>
Sent: Wednesday, September 22, 1999 10:04 AM
Subject: Data Audits


> Hi,
>
> This is not specifically RPG400 related, however, does anyone have a
pratical
> method of monitoring data changes (before and after, with user info etc)
in
> AS400 DB files, other than journalling and triggers. ?????
>
> Thanks
>
>
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>

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