Re: Who called me in Trigger

John,

My first choice is to update a data area in qtemp before any update, delete, or 
write.  The other option is to send a message up the stack and receive it back. 
 
Specify a message key on the send and receive. Walk up the stack passing a 
program queue of * and increment the level for each call. Receive the message 
after the send using the message key return from the send.
 
If you are using the API the sender is in the 300 format.  The copy source that 
describes this format is QMHRCVPM in QSYSINC.  For OPM programs 
QMHRPN will contain '*N' and the program will be in QMHRPGMN01. For ILE 
programs the procedure name will be found in QMHRPN.

I have heard that in some environments it will work to send the message 
directly to 
*CTLBDY with a level of 2.  I got this from the Midrange Computing ILE forum, 
but 
I haven't tried it myself.  I would guess this works if you are using a named 
activation 
group for your trigger.

David Morris
 
>>> "John Bussert" <jbussert@stecnet.com> 10/18 9:09 PM >>>
I know that this was answered at least once before, but if someone has it if
you could re-post it I would appreciate it.

What I need is the caller (or the program that created the event) that
caused the trigger to be called.  Also, if you have any idea or history of
the performance of doing this.  Usually, getting the invocation stack is a
pretty expensive operation.  I would hate to do it on every operation,
but...

Thanks

John

John Bussert
Swift Technologies, Inc.
jbussert@stecnet.com 


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---