Re: Trigger-happy

Please see.my trigger mediator at www.think400.dk/downloads.htm. same
concept but much more sophisticated and the concept solves your new version
problem.

There is a user space which contains a timestamp. When the database is
updated, it updates the timestamp in the user space.The trigger program
captures the timestamp when it starts up. If you request an update, all the
instances are cleared and everything reloaded including a new version of
the service program. Concept can be used for anything.
.

On Feb 26, 2018 2:38 PM, "Craig Richards" <craig@xxxxxxxxxxxxxxxx> 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.

That way the logic can be changed without having to remove the trigger
program from the file which requires exclusive access.

( I know this doesn’t solve the issue of currently running jobs continuing
to access the old object )

One part of my application won’t like this but I could resolve my
particular problem by putting the program in the same library as the file (
which IBM recommend anyway ) but I’d be interested to find out if anyone
else uses this as a general approach?

Thanks,
Craig
--
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