Re: Trigger techniques

Jon Paris wrote:

Anyone care to share what they do to facilitate being able to bring a
new version of a trigger program into use.

For performance reasons we don't want to set on LR on each call - but
how do you make sure that it gets refreshed when a new version is
available? I can think of a number of options but each one I come up
seems to have its own issues.

Very simple.

If a trigger program is active, the job(s) in which it is active have a
lock on it.

Simply put, you CAN'T update it while it's active.

You could, however, set up a *DTAARA, and a check for it every time the
trigger is invoked, such that LR is set on whenever the trigger sees a
particular value in the *DTAARA.

Or you can just forcibly torpedo all jobs with a lock on the trigger
program.

Given that we use triggers for data propagation and for workflow
scripting, I know something about them.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.