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



If the SQL is run from one server, you may look at the Dynamic Expanded SQL
API (QSQPRCED).

This lets you prepare an SQL statement in advance and store the details in
an SQL Package. Those SQL Packages cannot be distributed, they are local.
Each SQL statement has a statement name (max 18 characters, IIRC) and is
called by that name.
You have to set up and use SQLDA to pass parameters to the statement
(parameter markers).
Records are also fetched via the SQLDA.

Just a thought.

With regards,
Carel Teijgeler

*********** REPLY SEPARATOR ***********

On 21-10-2008 at 13:32 Vern Hamberg wrote:

We see this with some customers - I have so far attributed it to paging
out of memory when a program has not been used in a while. Loading SQL
is always a fairly intensive process.

But if someone has a solution, we have customers that would love you!

profound wrote:
I have a number of RGPLE CGI programs running in persistent mode, some
using dynamic SQL. I have noticed 2 problems

1. When a program containing SQL is first called, it takes a
significant time to run (sometimes up to 14 seconds). Any subsequent
call to the same program will run normally in less than a second.

2. When running non-SQL programs, and the user stops using the system
for approx 30 minutes, the first program takes a very long time to run
when the user resumes using the system again ( sometime up to 20
seconds).




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.