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



>Having seen repeated recommendations to
>isolate the trigger program from
>the actual processing program, doesn't
>this therefore imply the use of a
>never-ending program ? ;)

Not at all, Evan.  My setup looks like this:

addpftrg ... pgm(generic)

pgm generic
*entry plist
   (trigger buffer definitions)

thisFile chain triggerControl
if triggerActive
  call thisFileTrigger
  parm (trigger buffer definitions)
endif

    pgm thisFileTrigger
    *entry plist
       (trigger buffer definitions)
    * perform actual trigger functionality here.

Make all the programs actgrp(*caller).

To replace the actual trigger program, just recompile thisFileTrigger.  You
can also turn the trigger off by setting the proper flag in the control
file.  Never having to actually do a rmvpftrg.
  --buck


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.