Re: Passing Info to a trigger program

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Off the top of my head...I'd say this is a bad idea.

What other information?  Perhaps there's a better way to do it.

Especially since you're planning to change all the programs writing to the
table anyways.

But to answer your question, I'd rule out an SQL Global variable, since
there's only one instance.

For performance reasons, I'd rule out a table also.

I'd be looking at something unique to the job
 - *LDA
 - DTAARA in QTEMP

Or that could be accessed by key
 - Keyed DTAQ
 - User Index

I'd probably lean toward the keyed access.
If the data is to be (mostly) written once, and read multiple times, I'd
use an user index.
If the data is written then consumed, I'd use a Keyed DTAQ.

Charles



On Wed, Aug 2, 2023 at 7:02 AM Brian Garland via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

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