×
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.
Like John, for this sort of thing I _often_ use a 'cache' array which is local to the procedure. It's up to you how many records you cache - 1, 10, 20, 500...
In some cases, if the entire file is small and the data in it is unlikely to change ( because it's 'control' data), I may even load the entire file into an array the first time my procedure is called, and simply retrieve from the array on subsequent calls. A small 'hit' up-front is offset by the improvement in performance later, since a LOOKUP is quicker than a CHAIN.
Rory
--- Original Message ---
From:"John McKay" <jmckay@xxxxxxxxxxxxxxxx>
Sent:Thu 4/23/09 7:43 am
To:"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Subj:Re: Externalizing Data Access - Reducing Disk I/O
You could use a multiple-occurring data structure or an array data structure
to store the last, say, 100, unique reads.
You could also use a user index to store a large data set.
Regards,
John McKay
www.mckaysoftware.ie
www.rpglanguage.com
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
