Re: Passing Info to a trigger program

There have been many great answers.

One option I use is to write an entry to a data queue.

I have a batch monitor program that waits on the data queue and does what
ever is needed.

The advantage of the data queue is that it is fast to write to and that
allows the trigger to end quickly, then the monitor program can process
the requests and if it is a little behind that is not slowing things down.

If the activity on the table is so much the monitor gets too far behind,
or it is critical to get the additional information into the log then you
can have multiple monitors processing the same queue.

Just another option to consider

Cheers

Don





From: "Brian Garland via MIDRANGE-L" <midrange-l@xxxxxxxxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: "Brian Garland" <Brian.Garland@xxxxxxxxxx>
Date: 02/08/2023 11:02 PM
Subject: Passing Info to a trigger program
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



I would like to be able to provide additional information that is not
available in the trigger buffer.

This additional information would be set by application programs and used
in the trigger program to create a log of changes for the application.

I have considered a table, a data area, and an SQL global variable.

Are there other options? Which option would provide the best performance?

Thanks,
Brian