Re: Triggers and programs that can be dismissed using them

As the name of the program that caused the trigger to fire is not included
in the trigger parameters you need some other method to determine which
program called the trigger program (a call that is automatic based on the
database update).

If the system is on V7R4 there is an SQL service (QSYS2.STACK_INFO) that
will give you this information.

On previous releases it is a bit more fiddly but an API exists where you can
extract information from the program call stack. (QWVRCSTK).

On behalf of a friend of mine, I am going to ask this:

He says he built a trigger for a table, say, table T1. He has like 10

programs that affect that table and >>of course activate the trigger. But
now he says he doesn't want that 2 particular programs out of >>those 10,
actually complete the trigger task.

I understand that the trigger receives two buffers as parameters: the

"before" and the "after" image >>of the row being affected. This way you
have the option to take the action on the NEW or OLD >>version of that
action.

Is it possible to do an inspection of the affecting program so that the

trigger actually won't do what's >>supposed to do based on a decision that's
coded within the trigger?

This is more or less like "hey, if this is program A, don't do anything".

TIA

Javier Sanchez.