Re: Passing Info to a trigger program

[Brad Stone <bvstone@xxxxxxxxx>]

I've always done setters and getters when it's an application that, if
parameters were used instead, the interface would change often requiring a
headache.  So I use:

xx_setValue('valueName1':'value1');
xx_setValue('valueName2':'value2');

(in this case, xx is a descriptor for the application to make it unique for
this specific case... like fedEx_setValue() or ups_setValue() or
dhl_setValue()).

Internally I set up a DS that I can clear/copy to a DS internal to a
function (so it's not always dealing with global data), etc.  Each
setValue() mapes to a field in the DS.  (I only use a DS so that I can
clear all the values in one command when resetting everything).



On Wed, Aug 2, 2023 at 9:09 AM Dsternb <dieter.bender@xxxxxxxxxxxx> wrote:

> <Niels>
> <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?
> </Niels>
>
> set and get procedures could have parms, are not limited in type and
> amount
> of data and could contain additional functional code. further more logic
> could be placed where it belongs to.
>
> 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.