There's no data on the invoking program that's passed to a trigger program. Thus, it requires additional programming on your behalf. Many customers have done this by using the OS/400 message-handling APIs: QMHSNDPM (Send Program Message) and QMHRCVPM (Receive Program Message). First, the trigger 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.
This was first published in December 2002