× 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.



Well, so far as I know, when a file is defined in a subprocedure, basically you have a fresh open when the SP is called, and a close when it exits - nothing is maintained between calls.

USROPN gets the same behavior - again, so far as I know.

Vern

On 10/8/2021 7:38 PM, James H. H. Lampert via RPG400-L wrote:
On 10/8/21 5:27 PM, Vern Hamberg wrote:
Now are maybe there issues of maintaining the position where you left off in one of the files?

Of course there are. The record contents can be thrown out (the recursion is very close to strict tail-recursion), but the position and the EOF state can't. That is the whole point of the question, and why opening it locally to the procedure invocation appears to be the only way, short of caching the entire contents of the file.

And performance is not an issue. The file to be opened locally has an absolute maximum of 55 records, and an absolute maximum of 49 records that would satisfy the key conditions.

So far, in my tests, it appears that (at least at V6), simply moving the F-spec to procedure level requires me to treat the file as program-described, and define a structure to receive the record, but treating externally-described files as program-described is old hat around here. Apparently scatter-gather doesn't work for files declared at procedure level?

--
JHHL


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.