RE: Track all records read from a table

On March 22, 2016 at 4:12 PM Mike Cunningham <mike.cunningham@xxxxxxx> wrote:


Thanks to everyone who has added to this thread. The backup issue could be a
problem for me as the file I need to do this on is one of our largest with
2.5M records. It gets backed up nightly so have 2.5M read triggers fire could
cause a problem. My trigger could ignore that job and not journal (or data
queue) that read but the trigger processing overhead would still take place. I
could also remove the trigger just before backup starts and then put it back
after backup ends but that's something I don't like to do as it could lead to
problems someday when adding it back fails and the error is hidden deep in the
backup joblog.

My other option is change code in the apps that read this data and presents it
do a user (all in-house source code) and have each app journal the read.

And since I first asked this question nothing I do is going to meet the need
100%. I remembered that we send the data I need to read journal off to a could
service that one of our offices use and the user can view the data that needs
tracked from that service. I have no way to monitor or control access to the
data once its sent.

Mike Cunningham

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth
Martin
Sent: Monday, March 21, 2016 8:07 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Track all records read from a table

As I understand it, a read trigger is pulled with CPYF and normal back-up.
That could be a serious impact on some files and would be a big concern that
should not be ignored. In my opinion.

On 3/21/2016 8:03 AM, Jim Oberholtzer wrote:

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

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