Re: Passing Info to a trigger program

[Niels Liisberg <nli@xxxxxxxxxxxxxxxxx>]

<dieter>


*more flexible than environment var would be a SRVPGM with exported
getXXXand setXXX procedures. The application outside the trigger is using
setXXXand the trigger is using getXXX.*
</dieter>

.. isn't it just what putenv and getenv does?



On Wed, Aug 2, 2023 at 3:50 PM Dsternb <dieter.bender@xxxxxxxxxxxx> wrote:

> <Brian>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?
> </Brian>
>
> more flexible than environment var would be a SRVPGM with exported getXXX
> and setXXX procedures. The application outside the trigger is using setXXX
> and the trigger is using getXXX.
>
> D*B
>
> --
> 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.