Although I haven’t done it, the answer is yes.
The trigger is a process of the database, since the ODBC is using the DB/2 software the trigger will be activated just as it would be for any other process.
The only problem you might have is with file authority. Normally an ODBC job is running under a genric user profile (Ex QUSER). The trigger program will fire but if you are updating files that the ODBC user does not have authority to, the trigger program could fail. We have trigger programs here that are created by a user profile with the correct authorities needed and has *OWNER authority on the program.
The problem I had was that the trigger, when activated by ODBC, does not have a library list that included our programs library. So, basically, when the trigger would try to run it could not find the program to execute, and would just fail to work. I solved this by putting the trigger program in the same library as the physical file. I know I also could have added the libraries I needed from within the program…but…I chose the quick solution. HTH.
Thanks to all replies. My trigger file is now set up in production.