|
At 06:11 PM 1/9/98 -0600, Srinivas Rao wrote: > Tim, > > You rightly said it..trigger will be a better solution. But I have a > question.. How can we find out, within the trigger program, which > program is triggering the change ? Is there anyway we can retreive > that value ? > > srini Srini, The trigger runs within the job that contains the program in question, so you could materialize the program stack or send/receive a message using a relative invocation level (see the SNDPGMMSG command). Other than that, a hard coded value from each program that could potentially change the file is a very good crude but effective low overhead solution that would certainly be my choice for troubleshooting. Pete Pete Hall peteh@inwave.com http://www.inwave.com/~peteh/ +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@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 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.