Re: Passing Info to a trigger program

Several have suggested journaling. I know a journal is a log of changes
and we do use them in many ways now.

How would I tie the extra data not from the table to the journal entries?
It seems like I would have to go the route of adding a column to every
table and using a unique value in that column to tie it back to another
table with the extra information. We really want this to be as close to
real-time as possible and that seems a bit complicated with journals.

Brian

Original post:
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?

--
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or company to whom they are
addressed.
Do not disclose, distribute, or copy this email to others outside your
company. If you have received this email in error, please notify the
sender
immediately and delete this email from your system.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.