I am looking at who called the trigger, but I don't get a chance to ignore
the events before the trigger is called recursively.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Douglas Handy
Sent: Monday, March 25, 2013 3:50 PM
To: Midrange Systems Technical Discussion
Subject: Re: PF Trigger question
I'm not sure that the shop floor device could receive the result
transactions in a different file. Is there a way for the trigger to
ignore certain events?
Do it with logic in your code. That is, let the trigger file but then just
don't do anything when the "certain events" happen.
For example, you may be able to recognize from the record contents that you
want to ignore it (perhaps scanning for "not found" or ",PCS=" or other
monikers). Or perhaps by retrieving the name of the program which fired the
trigger and if it matches the trigger program itself, avoid doing another
write. Do a search on finding a trigger program caller and you should find
plenty of code examples for getting the name of the program which caused the
trigger event.
Doug
--
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.
As an Amazon Associate we earn from qualifying purchases.