On the contrary, since the journal can automatically log all files changes then it is not difficult to create a script that copies the changes to a permanent log file, on a daily basis say, that can be queried as necessary showing who when and how.
In fact we do this with a generic script which reads a list of files required to be logged and generates permanent logs of all changes. No triggers, no RPG, zero impact on existing apps.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Thursday, 31 October 2013 8:44 a.m.
To: Midrange Systems Technical Discussion
Subject: Log file of file changes
All,
We had an issue recently about how a couple of prices got changed. The salesrep (who has _some_ control over pricing) says he didn't do it, and no one in the office remembers doing it. In fact, it was the sales rep who brought it up wanting to know what the %#@* is going on? :) By looking at month end backups, I know it happened sometime in August. Nothing like bringing it to our attention on a timely basis, right?
Anyway, in discussing it, the buying VP suggested a log file of changes. I think it's a great idea and it seems to me to be an ideal use for a trigger. Whenever a record is added/updated/deleted, just have the trigger write the record to this log file. It can have the same record layout as the file in question, plus add a few fields such as user and timestamp.
Seem reasonable? I've never written a trigger before but I can figure it out.
The file is currently journaled, but that's not really what journaling is for, IMO.
Thanks for any ideas.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
#####################################################################################
This correspondence is for the named person's use only. It may contain confidential
or legally privileged information, or both. No confidentiality or privilege is waived
or lost by any mistransmission. If you receive this correspondence in error, please
immediately delete it from your system and notify the sender. You must not disclose,
copy or rely on any part of this correspondence if you are not the intended recipient.
Any views expressed in this message are those of the individual sender, except where
the sender expressly, and with authority, states them to be the views of Veda.
If you need assistance, please contact Veda on either :-
Australia 1300-762-207 or New Zealand +64 9 367 6200
midrange.com
