RE: Who pulled the trigger?

[Terry Richardson <RichardsonT@xxxxxxxxx>]

Ron-Actually, it's not all that messy.  There was an article in News/400
about a year or so called 'giving your trigger programs Caller ID' or
something similar.  We implemented trigger programs and found this method of
finding out who pulled the trigger to be fast and reliable.  Give it a shot,
it's not as bad as it first appears.
Terry Richardson
Sr. P/A
The Orvis Company, Inc.
802-362-8663


        -----Original Message-----
        From:   HwaRangRon@aol.com [SMTP:HwaRangRon@aol.com]
        Sent:   Friday, September 17, 1999 10:34 AM
        To:     MIDRANGE-L@midrange.com
        Subject:        Who pulled the trigger?

        We're just starting to use triggers to track changes in files.
(We've always 
        used journaling before.) I'm curious about the best method of
finding out who 
        pulled the trigger? Someone told me theres an API, but I've never
seen it. 
        The only way I know of is to get the job stack and back up, but this
is very 
        messy. There must be a simpler way.

        Anybody got any ideas?

        Ron
        +---
        | 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
        +---
+---
| 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
+---