RE: Log all PF changes?

Agreed. Why roll your own when the OS/DB will handle it for you?

Brian May
Solutions Architect
Profound Logic Software
http://www.profoundlogic.com
937-439-7925 Phone
877-224-7768 Toll Free
  

The IBM i Modernization Experts
www.profoundlogic.com
             


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, January 6, 2016 12:42 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Log all PF changes?

+1 for journalling.

DB2 doesn't have this
http://archive.midrange.com/midrange-l/201505/msg00150.html


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/06/2016 01:28 PM
Subject: Re: Log all PF changes?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Journaling, that's what it's there fore! It's also better because you
cannot tamper with it. Any log written by your own program (such as a
trigger) is suspect because you could ignore certain changes or mess
with the log afterword with DBU etc etc.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 1/6/2016 1:21 PM, Justin Taylor 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?