Re: Avoiding redundant triggers?

Not sure what you mean about the One Trigger Per Slot rule - since there has never been such a restriction in DB2/400. But as I understand it, if you specify your own name when creating a trigger - rather than letting the system assign one for you - then the system will prevent such duplication. Say, you use a standard like BEFORE_UPD_MYTRIG, and always stick to that. But miskeys and nonadherence to standards will defeat this.

Your trigger program can do certain things, like setting DTAARA values et cetera but that'll slow you down and introduce tedium.

Probably the best bet is a regular audit of your triggers (PRTTRGRPT or similar).

"James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx> wrote:

Fellow geeks, geekettes, and gurus:

We recently discovered a situation in which data propagation triggers
were applied to several files *twice,* resulting in the data getting
propagated *twice.*

Now in this particular case, there are no other triggers on the
affected
files, so it's fairly straightforward to avoid this situation.

But what of the possibility that some other application has a trigger
in
the same slot? Is there a way to prevent redundant triggering, without
interfering with somebody else's triggers? I know about trigger names,
but I don't quite understand how they work, and the helptext and error
messages from my attempts to use them are rather unhelpful.

It was so much easier under the old "one trigger per slot" rule.

--
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.

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.