I use a variation on Brad's idea by storing information in uniquely named user spaces. It is very quick if you can use that method.
Rich Loeber
Kisco Systems LLC
https://www.kisco.com
________________________________
On 2/27/2024 9:11 AM, Brad Stone wrote:
I would always use some sort of unique ID to pass and then go to the file
and get the data required using that unique ID.
On Tue, Feb 27, 2024 at 8:02 AM Brian Garland via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx<mailto: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<mailto: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<mailto: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<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.
midrange.com
