× 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: Trigger
  • From: "Alex Moore" <alexm@xxxxxxxxxxxxxxxx>
  • Date: Mon, 4 Dec 2000 06:29:05 -0500
  • Importance: Normal

We use triggers extensively.  Our experience has led us to the following
standards:

a)      All trigger programs are written in CL and do nothing but pass the
trigger parameters over to the "real" trigger program.  This allows
modifying the "real" trigger without having to have an exclusive lock on the
file.

b)      Do minimal (or essential) logic in the trigger program, especially
avoiding the use of other files, except where necessary (like for timing).
The job that fires the trigger must wait while the trigger program runs.
After minimal, if any, logic, the trigger program passes the buffers over to
a data queue.

c)      Have a never ending program process the entries off of the data queue in
batch.

Alex Moore

> can anyone help in using trigger the right way. Every trigger program I
> use takes such a lot of performance, so I have to inactivate the
> trigger.
> Is this a general trigger problem, or are there some things I have to
> pay attention to ? Thanks.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-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 ...

Replies:

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.