|
Any Toolbox gurus out there?Do the cursor-positioning methods in the AS400File class, i.e., positionCursorBeforeFirst(), positionCursorToFirst(), and so forth, and the sequential reading methods, readFirst(), readNext(), and so forth, produce expected results if applied to a KeyedFile? Particularly a KeyedFile that's open on a physical file that is set to re-use deleted records?
Scenario:Records are constantly being added to a file, FOO, by any number of jobs throughout the system. This file is being polled continuously, and records are being read, in FIFO order, copied into another file, BAR, and deleted from FOO, as fast as the polling job, FROBOZZ, can process them. If FROBOZZ opens FOO with the SequentialFile class, then FOO cannot re-use its deleted records, because if FIFO order would not be guaranteed if at any point FOO contains more than one active record. Thus, FROBOZZ, and all the jobs pouring records into FOO, would have to be shut down periodically to do a RGZPFM on FOO, or FOO would eventually overflow.
FOO is, however, keyed uniquely on a rather long (i.e., 21-digit!) numeric field that is incremented with each write operation. If we open it using the KeyedFile class, would I be correct in assuming that the aforementioned AS400File methods give us sequential-by-key access?
-- JHHL
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
