× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Changing triggers
  • From: John P Carr <jpcarr@xxxxxxxxxxxx>
  • Date: Mon, 27 Mar 2000 14:35:21 -0500



I would like to see how they accommodated the different buffer
layouts(Before/After image) based on the record length of each file evoking
the trigger.

John Carr
----------------------------------

One of the software vendors I work with has done this.

What they did was to build a generic trigger program, which they reference
on the ADDPFTRG command. The generic trigger when activiated writes it's
data to file.  A batch job waiting on the same file with an end of file
delay then refers to a table to determine which program(s) should be called
to re-signal the trigger.

Of course, the generic trigger program has to be well thought out, and
including extra program calls to re-signal the trigger does have a
performance penalty.  

AFAIK, these triggers are only *AFTER style triggers, just intended to let
another application or interface know that a record had been
added/changed/deleted.  

This setup was written in RPG III
Regards,
Rich
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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 thread ...

Follow-Ups:

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

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.