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



Shane,

What I think you're missing is that the READx opcodes do not set the %FOUND flag. For file I/O, CHAIN and SETxx opcodes do. READx opcodes (amongst others) set the %EOF flag.

-mark

On 11/11/2019 1:49 PM, SReeves@xxxxxxxxxxxxxxxxxx wrote:
So this bug came up in a pretty old program that I'm surprised that it
hasn't been an issue before today. My question is, when DOU %EOF and If
NOT %FOUND is used, without specifying a file, is always just using the
last read file?
Below is most the relevant code. The previous programmer didn't specify
the filename on the commands. Adding 'FILE1' to them fixed the issue, so
it is technically solved, but I just want to better understand myself why
it wasn't working.

In this case FILE1 had two matching records for the key. The first record
processed okay, it goes down to the end of the DO loop and the next record
is read. *(I ran it in debug so I know the program found it. It
immedially went back up to the top of the do loop, and then on 'IF NOT
%FOUND' it came up as not found, which surprised me as FILE1 was the last
file to be read and it did find the next record. Am I misunderstanding
something? Again, the program worked fine adding the proper file to the
command.


C KEY1 SETLL FILE1
C KEY1 READE FILE1
C DOU %EOF
C IF NOT %FOUND
...
C ELSE
...
C KEY2 CHAIN FILE2
...
C KEY3 SETLL KEY3
C KEY3 READE KEY3
...
C ELSE
C KEY1 READE FILE1
C ENDDO



Shane


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.