× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Excellent point. (I do think you meant firing trigger rather than
journaling will slow it down though)

Additionally to mitigate the effect of the trigger, when your read trigger
fires, have it do nothing but enqueue a data queue entry with the needed
information then quit. That way it's very fast, and any database activity
would not be impacted. Your program that reads the data queue and does
whatever it has to do can then do it in a more leisurely way.

--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Monday, March 21, 2016 7:54 AM
To: Midrange Systems Technical Discussion
Subject: 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.

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.