Re: Trigger-happy

So,

I just ran a couple of tests and as suspected this will let you change the
program on the fly.

I ran some updates STRSQL and while still in there I recompiled the trigger
program.
Repeating the update statement in STRSQL picked up the new code.

Then I ran 3 update SQL statements inside an SQLRPGLE program which runs in
a named activation group.
Debugged the program
Sat on a breakpoint in the program while I recompiled the trigger.
Let the update program continue to the last update and it picked up the new
version of the trigger.

It was as we suspected because the call is via a variable name, however
it's good to prove it.

Nice one that seems like decent functionality for a small loss in
performance and not much effort.

On 27 February 2018 at 16:13, Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx>
wrote:

Actually *LIBL is the most common way here. Only when a client specific
medication to a standard trigger program is needed do we actually qualify
the library.

Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----

From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Craig Richards
Sent: Tuesday, February 27, 2018 9:38 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Trigger-happy

Just out of curiosity Kevin - do you ever put *LIBL as the Program

Library or is

it always a real library?

I haven't tried *LIBL and I'm not saying I think it's a good idea, but I

don't see

why it wouldn't work.

thanks,
Craig

On 27 February 2018 at 15:02, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 2/26/2018 5:38 PM, Craig Richards wrote:

One technique I’ve seen for triggers is to have the actual trigger

program

do nothing more than forward the trigger buffer data on to another

program.

-snip-

I’d be interested to find out if anyone else uses this as a general
approach?

Absolutely! Kevin uses a table, we use a data area to turn the actual
trigger processing 'off' for whatever reason. Don't need it often,
but when we do, it's been invaluable.

--
--buck

http://wiki.midrange.com
Your updates make it better!

--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To

subscribe,

unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD