Audit trail of masterfile changes

[Jim Hamer]

Clifford,

We use the plain ordinary Audit files. The layout of the Audit file is an
exact duplicate of the master file, with four additional fields: Date and
Time stamp, Function and User name. The Audit file is also indexed.

The Quick program, that shows the users the Audit changes, reads the
records for the given key. There is lots of ugly code that compares the
pervious record, field by field, to determine which field has changed. Then
the changes are shown via a cluster, and there is lots more ugly code to
control the cluster so that there is an occurrence of the cluster for each
field that has changed, showing the before image and after image of the field.

One last point. The Audit file had to be populated with initial records.
This is necessary so that there is a before image.

I think that the concept an on-line auditing is not widely embraced. I
agree that it would have been much more useful to store the before image,
so that you could compare the audit record with the master file record. It
would be great if you could specify which image. 

Jim

At 12:11 PM 99/05/07 +0200, you wrote:
>Anyone have a low maintenance method of writing audit trail records to a
>file when users update masterfile records.
>We want to keep the following info on a file so the users can see it:
>user
>date
>time
>masterfile name
>masterfile field
>changed from
>changed to
>
>We currently call a cobol program in the pre-update procedure passing the
>masterfile record.
>The cobol program reads the original record and compares all the fields one
>by one writing 
>the audit trail records. It works but is a lot of work to maintain as our
>masterfiles are
>constantly changing.
>
>The audit file option doesn't seem to help as it only stores an after image
>of all the fields changed.
>Anyone have a better, preferably low maintenance way of doing this...
>
>PH 7.29.C5 on MPE/iX
>
>Thanks
>Clifford Art
>cart@metropolitan.co.za
>
>= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
>Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
>powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
>This list is closed, thus to post to the list, you must be a subscriber.
>
>

Thanks,

Jim
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.