Audit trail of file changes

Dear James, < vendor >

The solution for your audit trail project has already been invented:
http://www.unbeatenpath.com/software/sit/Stitch-in-Time.pdf
It's a bulls-eye vis-a-vis your requirements.

Our methodology does include journalling. We figured out a way to
overcome the hard drive consumption problems associated with
journal receivers. It's got a free demo.

Warm regards,

Milt Habeck
Founder
Unbeaten Path International

www.unbeatenpath.com/compass
(888) 874-8008


</vendor>








From: James Rich
To: midrange-l
Sent: Thursday, May 21, 2009 4:42 PM
Subject: Audit trail of file changes


Hi everyone,

I have an assignment to keep track of all changes that occur to a physical
file for auditing purposes. Since we have to be certain we get changes
from any source, whether via a logical file, DFU, SQL, or RPG program,
journaling seemed like the best way to go. But I don't have experience
journaling files so I need a bit of help.

The audit log of changes must be kept indefinitely and reported
semi-monthly. For each change they want to know what the record looked
like before and after. I don't anticipate an enormous number of changes
per reporting period, at most 186 (that is the number of records in the
file). I created a journal receiver with CRTJRNRCV and set the THRESHOLD
parameter to *NONE. Is there a problem with using *NONE there? It has
been suggested to me to detach the journal and save the receiver at each
reporting period. Is that necessary and if so why? What would you
recommend as a good procedure to fill these requirements?

James Rich