Re: Track all records read from a table

Mark's provided you the answer.

However, let me point out that journaling every read could have significant
performance impact.

Let say for instance, you're dealing with credit card info in your customer
master. You may find it worthwhile to move the credit card info into it's
own file so that you can put the trigger on the CC info file and not the
customer master.

Charles

On Sat, Mar 19, 2016 at 12:05 PM, Mark S Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Hi, Mike:

Support for ADDPFTRG ... TRGTIME(*AFTER) TRGEVENT(*READ) ... was added in
V5R1, if I recall correctly.

Prompt the ADDPFTRG command, tab down to "Trigger event" and press
F4=Prompt, and you will see:

Trigger event . . . . . . . . . ________

*INSERT
*DELETE
*UPDATE
*READ

This support was added by IBM specifically to address the kind of
requirement you are talking about.

Hope that helps,

Mark S. Waterbury

On 3/19/2016 11:34 AM, Mike Cunningham wrote:

I know journaling can track file opens and database changes with before
and after images but I need to start tracking who might have viewed
individual records in some tables, even if no changes were made. Before I
build a custom solution I wanted to check to see if there is some way
journaling could do this. If I had to go the custom route it does not look
like a trigger would work since that does not appear to work with just a
read event. In my case I do have access to source code and could log every
request to view the records we need to track to this level within each
application that needs it. Is that my only option?

Thanks
Mike Cunningham

Sent from my iPad

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