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



Probably a question more appropriate for the RPG list...

But I'd want more info about the "clearing and writing to these tables" ...

While writing to a Db2 table is expensive compared to memory, I wound't
expect it to be significant in the kind of process you describe.

Charles

On Tue, Feb 27, 2024 at 7:02 AM Brian Garland via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

This is sort of a best practice question.

We have an RPGLE based web service that prices an order. Since we already
had pricing routines that worked off database tables containing order
information we take what comes into the web service and create a QTEMP
version of the tables with the order and run our existing pricing
routines.

This has proven to be fairly slow so we started analysing where. Currently
the largest chunk of time is spent clearing and writing to these tables.
We do build them once per job which makes a difference. We also include
some indexing. Our initial thought is that if we could keep the
information in memory and modify our pricing routine to work off that
memory we could improve the performance. The fallout from this would be
updating our routine that runs off tables to copy the info needed into
memory before pricing and the update the tables afterward. That is to
avoid having two routines that do the same thing. This bit of extra time
on that process is okay.

So, the question is what is the best way to pass that chuck of memory
between programs so that several programs can each update their part?

Brian

--
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or company to whom they are
addressed.
Do not disclose, distribute, or copy this email to others outside your
company. If you have received this email in error, please notify the
sender
immediately and delete this email from your system.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.