|
> We read the file and stop on a specific record. The > RRN is returned to the calling program. At another time, > the program is called with the keys and the RRN again. > We need to start at the record where we stopped before > and continue reading. If the file is dynamically updated whilst you are 'stopped' then the saved RRN might point to a deleted record, or worse, past a record you haven't read yet. That is one thing to consider. If we posit that the database will remain static between calls, then why not open the file SHARE(*YES)? Then you won't need to pass an RRN back and forth; program B can pick up right where program A left off and vice versa. This won't completely overcome the 'file was updated between program calls' scenario; only a complete re-read can do that. --buck
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.