RE: Trigger question

The trigger runs in the job that does the insert (or whatever trips the
trigger), so it ought to be a simple matter of working up the call
stack.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Wednesday, September 03, 2008 8:34 PM
To: Midrange Systems Technical Discussion
Subject: Re: Trigger question

Pete Hall wrote:

Maybe this isn't why you need to know the program name: A while back I

needed to know if a certain program was updating a file because I
needed the trigger to do nothing in order to avoid a circular update.
Don't remember exactly why. I used a user space in QTEMP. If the user
space didn't exist, or the space didn't contain an expected value,
fire normally. If it did exist, and contained the expected value,
don't do anything.

Actually, in this case, we need to know what program tripped the trigger
because it's designed to veto updates unless either the user, the job,
or THE PROGRAM is on a pre-approved list.

--
James H. H. Lampert
Touchtone Corporation

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.