Re: IF NOT %FOUND -- RPG400-L

Subject: Re: IF NOT %FOUND
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Mon, 11 Nov 2019 13:21:16 -0600
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@lists.midrange.com?subject=help>
List-id: RPG programming on IBM i <rpg400-l.lists.midrange.com>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

On 11/11/2019 1:06 PM, mlazarus wrote:

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

This ^^^^ x1000.

This was one of the hardest things in the world to train myself on. I lost a lot of hours trying to figure out why some loops didn't work until I broke myself of the habit. And it's not like I didn't know, I just had a brain-cramp (usually moving from a CHAIN to a READE), wrote %FOUND instead of %EOF, and then couldn't see why it wasn't working.

It gets even trickier when you use the %FOUND vs. %EQUAL on SETxx.

Ugh.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.