You could also consider journaling those files of interest. A bit of an
overhead but may be worth it if it is important.

Jim.


-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx]
On Behalf Of Deon A von Blerk
Sent: Friday, January 27, 2012 11:27 AM
To: system21@xxxxxxxxxxxx
Subject: Re: [SYSTEM21] SYSTEM21 Digest, Vol 10, Issue 6

I agree with Geoff. Added to that is the fact that many of the S21 files
have no audit e.g. INP15.

Regards

Kit
www.ecofitonline.com


----------------------------------------------------------------------

message: 1
date: Fri, 27 Jan 2012 00:01:04 +0000
from: Geoff Boreland <gboreland@xxxxxxxxxxxxxxxxxxxxxxx>
subject: Re: [SYSTEM21] System21 - Time from Pick Note to Despatch
Note

You might also want to contemplate the use of database triggers to
ensure you capture all the information required.

A typical audit file is only ever going to be as useful as all of the
programs that write / update it. As soon as someone performs a write
or an update to the master file without including the audit file, then
the audit trail is compromised.

We have found that installing database triggers will ensure you
capture all database I/O's including SQL / DFU style updates, as the
I/O is performed at the operating system level and not within the program.

Regards
Geoff

_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list To post a message email:
SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/system21.


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].