|
On 07/03/2006, at 12:23 PM, James H H Lampert wrote:
1. Be lighter than a temporary database file, preferably living in memory, instead of on disk, and having less overhead than a file, 2. Yet still be capable of expanding to contain whatever data records are put into it, 3. While rejecting duplicate records?
Why do you think the file is the bottle-neck?Investigate *USRIDX objects. These are persistent objects and so exist on DISK in the same way files do but they are lighter. Note that objects in use are probably in main storage anyway therefore physical I/O (i.e., DISK I/O) will be reduced. Investigate SETOBJACC to load the file completely into main storage. Investigate blocking to load multiple records into your program buffer.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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
