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



"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 04/07/2016 11:25:39
AM:
Reviewing several examples of trigger programs online, I noticed that
all
of them turned on the LR indicator. For testing, I no-op'd the EVAL
*INLR=*ON so the program would compile, but never have LR turned on.
Duplicating the previous test cycle, without a trigger, the 10 runs
averaged 3.6 seconds. With a trigger, the 10 runs averaged 11.8
seconds.
Yeah, about 16 times faster than when turning LR on.

We opted to write to a data queue to minimize any actual file I/O
in our trigger program. We then have a separate subsystem we created with
long-running listeners for the multiple data queues involved in our
environment (about 588 of them). We also have a monitor job which keeps
track of all these listeners and data queues to manage them and keep them
all in line -- keeping us informed by email of any issues along the way.

At the time I originally wrote the trigger program we weren't
doing this, but now our model is to use the MAIN keyword to specify our
own main procedure and totally eliminate all of the RPG cycle code that
you don't know is being executed under the covers each time your program
is called and terminated. In this model, the *INLR indicator no longer
does anything and if we have any F-specs (or DCL-F) we code them as
*USRCTL -- but we mostly use embedded SQL now.

Sincerely,

Dave Clark
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331



*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************

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.