Re: trigger programs

["Walden Leverich" <walden@xxxxxxxxxxxxxxx>]

We had the same problem at one of our clients. Specifically, some program
was changing the create date of an item record. We did use triggers to
capture the offending program by displaying the job to *PRINT whenever the
create date changed. This showed us not only the program that caused the
update, but the entire stack above it. Sometime the program that makes the
update is not the offending program, as it may have been passed bad data
from its caller. Please don't flame me about the poor performance of this
approach. We did this for a short period of time to find a program that was
corrupting our database and then removed that portion of the trigger.

To answer your question generically however, the only way I know of to
determine the program that caused the update is to send a message up the
program stack and then retrieve it and examine the program value in the time
stamp. To be exactly correct you should probably repeat this process going
up the stack until you find a "user" program (something that doesn't start
with a Q), however I have always sent the message up 2 levels (the 1st level
is guaranteed to be Q-something) and left it there. I have searched for an
API to view the program stack, but I cannot find one.

-Walden
-----Original Message-----
From: Saskia Hartley <shartley@fritzi.com>
To: midr <MIDRANGE-L@midrange.com>
Date: Tuesday, November 18, 1997 1:38 PM
Subject: trigger programs


>Hello everyone
>
>Have any of you experience with trigger programs?  Any specific helpful
>hints to offer?  We are trying to determine which program in our system is
>changing a specific field in a file.  Looking at the documentation on
>trigger programs, it appears to me that the name of the program is not
>captured in the buffer.  Is there some way I can get it?
>
>TIA
>saskia


+---
| 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 MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---