Re: On Triggers and library lists.

<Craig>
I agree that as you say, once added, the trigger program is qualified it
will always be located when the trigger on the table fires.
I was really only asking about whether it's usual to force the trigger to
use files in the same library the file triggers from, and if there was a
simpler way in SQL triggers than doing what I'm doing with an RPGLE program
trigger - either overriding or qualifying all file access )
( for example, I wondered if the more SQL-Trigger savvy would start
shouting at me, something like: USE AN SQL TRIGGER AND SET SCHEMA YOU
MUPPET! )
So far that hasn't happened...

I can see that in general the problem is bigger than just the data - as you
point out - if the trigger program had a requirement to call other programs
then that would be an additional concern but thankfully in my case it is
not required.

So I guess your last sentence is the one that interests me the most - "use
SQL for all I/O operations and qualify in all statements"

Given that I will mostly ( I hope ) only be dealing with 4 or 5 files in
each trigger I think for safety I will qualify all file access.
</Craig>

Have in mind, that you can't controll the environment the trigger is running in!!!

you can't rely on naming SQL or SYS, you can't rely on current schema, curlib, libl; you don't know, wether OVRDBF was used outside, OVRSCOPE and ...

Don't make the qualify hardcoded, look at the PSDS from wich lib the trigger was called and use this lib as a qualifier.

D*B