|
You could walk the program stack by sending a message to the *PRV of *CALLER, then RCVMSG with format *LONG. Sorry but cannot give you the exact position, but *Somewhere* in the received message string is the program name ( both sender and receiver ). Narayanan Pillai ps: Just keep in mind the fact that the immediate caller of the trigger will be a QDB* program, you need it's caller. On Monday 11 August 2003 12:58, g man wrote: > I am working on a Change Log application - I have a trigger on a file, > > is there a way to find out what program caused the trigger to be > activated...i.e RPG, DFU whatever ?? > > any help /pointers would be appreciated... > > thanks > > > > > ____________________________________________________________ > Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail! > http://login.mail.lycos.com/r/referral?aid=27005 > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.