×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Can you update the existing record? That should avoid attempting to fire an
INSERT trigger.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Tucky
Sent: Monday, March 25, 2013 12:27 PM
To: Midrange Systems Technical Discussion
Subject: PF Trigger question

I'm working on a project where a shop floor device will use FTP to insert a
record into a PF file. The plan is to use a trigger to process the incoming
record, but the specs also call for the trigger to write a result record
into the same file.



For instance, the shop floor device might put a record in the file that says
"SERIAL#=12345678', then I need to write a result record, either
'SERIAL#=12345678 not found' or 'SERIAL#=12345678,PCS=100', or several other
replies



The trigger will fire again when we write the record. I've tried setting
the trigger to *DISABLED before I write my result record, but I'm still
getting RNX8888, RPG program TRIGGER was called recursively.



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?



Thanks, Jack



--
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.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2026 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.