How can I identify the 'calling event' (program, SQL, ODBC, etc.) that launches a trigger program?
DB2 UDB does not provide any components in it's trigger to determine this. Some iSeries programmers have used the Send & Receive Message APIs (QMHSNDPM & QMHRCVPM) where the program uses API QMHSNDPM to send a message to the message queue of the changing program's call-stack entry. API QMHRCVPM then retrieves the message from the message queue, obtaining the name of the program associated with that entry in the process.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this online event, Getting the Most out of SQL & DB2 UDB for the iSeries.
Dig deeper on Oracle on iSeries
Related Q&A from Kent Milligan
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ...continue reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ...continue reading
When developing tables in a parent-child relationship, use a primary key and a foreign key along with a unique ID to make your database easier to ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.