• Subject: Re: Who pulled the trigger?
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Fri, 17 Sep 1999 10:08:25 -0500

I put the Program Status Data Structure into an externally defined 
data structure.  Then you can retrieve the user from that job.  The 
trigger runs under the same job as the job that made the change.

The only catch is jobs from Client Access.  Some of them buggers run 
under standard id's.





HwaRangRon@aol.com on 09/17/99 10:03:43 AM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.