Re: Track all records read from a table

If performance is a concern when doing the save, you can disable the
trigger just before the save using the CHGPFTRG command:
Trigger state . . . . . . . . . STATE > *DISABLED
then after the save
Trigger state . . . . . . . . . STATE > *ENABLED


Jeff Young
Sr. Programmer Analyst

On Tue, Mar 22, 2016 at 12:57 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I agree. However, it won't help the OP with the performance hit caused

by

read triggers.

Seems rather odd to me that database I/O is cached by default. But you have
to license that feature for journals.

Regarding the performance hit on read triggers, I think Jim hit the nail on
the head by suggesting an asynchronous process and using a data queue. We
use a similar process. Except we use shared memory between the trigger
program and an external JOB which we call a database event handler to pass
record buffers, which is even faster than a data queue.
--
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.