RE: Log all PF changes?

Thanks,
Gary Monnier
IT Software Engineer CSM, CSPO


There's this...

1. Start journaling the table. I suggest omitting open and close entries.
2. Clone the source for the table in question; renaming it and adding any additional columns you desire: user altering the row,
action taken (insert, update, delete), timestamp for row creation and change if not there already.
3. Write a program that reads the journal entries, formats the entry specific data to the cloned table and writes records to it.
This can be a NEPs program.
4. Use the cloned table to report from.

Now you can let the table grow to whatever size you want. Saving the journals & their receivers provides to the ability rebuild the table if necessary.

You also have the data necessary to rebuild the original table if such a thing becomes necessary.

Hope this helps.

Gary

On Wed, Jan 6, 2016 at 1:21 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I need to keep a permanent log of all data changes in a particular PF.
I can think of two ways to accomplish this.

1. A DB2 journal with the receivers set to never expire.

2. A trigger that would write the before images to a separate PF.

I expect questions of "who changed what when" to be a weekly occurrence.

Either of those options sound better than the other? Anyone have a
door #3?
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related questions.