The information gleaned from my post for assistance earlier this month is
filed away for future use in my sql triggers folder, thank you verry much!
The project objective started out muddy, but finally got boiled down to
this (my words)
If any of 3 people, change any of 10ish files which exist in 3
environments, by any method, the upper up(s) want to know about it on at
least a weekly basis."
(method [Program/DBU/STRSQL]-- was not a dealbreaker -- just nice to have)
A trigger(s) was my original thought on how to get the results, but
research, reading, help from the group, and some coding it started to seem
like a trigger was kind of a longhand way of going about getting what i
needed. A co-worker then re-suggested journaling.
So after a lot of googling and searching midrange-l i found some
links/threads which became my big timesaver.
First was a link in the group to an article by Dan Riehl
Forensic Analysis - Easily Track Changes to your Database:
http://www.securemyi.com/nl/articles/databaseaudit.html
(also in this article, a good reason(s) to choose journaling over
triggers)
This link showed me what a pita it was going to be to manage my own
journals etc AND write something to make the IBM generated report from
CMPJRNIMG more executive friendly.
(i didn't take much of a look at doing it thru navigator)
Second thing was more reading and searches which led me to this
Log all PF changes?:
https://archive.midrange.com/midrange-l/201601/msg00099.html
It's a long thread but worth the read (aren't they all).
Along with the good stuff in there -- was list of 5 or 6 3rd party
providers of file auditing/journaling software.
Somewhere in that thread or a different thread was a price mention of one
of the vendors software.
I honestly landed with that vendor because the price was in the 'i think
i can talk them into buying this' realm.
After trying it out it seems like it's going to work for what we need and
i am moving forward with setting it up now.
ps I have nothing against triggers (external) or anything else written in
rpg. :-)
John
<br />
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful.
midrange.com
