If you have the *INLR = *on; code in a place that never gets executed and
don't have return at the end of the program that may be the problem. One
or the other must happen or the RPG cycle will cause what you are
describing, It's happened to me.

Alan Shore <AlanShore@xxxxxxxx>
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
08/14/2008 03:12 PM
Re: READE in Free form, and dow not %eof

Hi Booth
I'm not sure if this will make a difference, but change the %eof to
compile and test

Alan Shore
Programmer/Analyst, Direct Response
P:(631) 244-2000 ext. 5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

rpg400-l-bounces@xxxxxxxxxxxx wrote on 08/14/2008 03:26:31 PM:

READE in Free form, and dow not %eof

Something is not working the way I expected.

I have a file with three keys. I want to read all records (53 of them)
where key1 = the value in XX1 and key2 = 11.

Here's what I think I have done:
FXXFILE if e k disk
XX1 = 'O';
// Retrieve XXFILE record:
setll (XX1: 11) XXFILE;
reade (XX1: 11) XXFILE;
dow not %eof;
... stuff
reade (XX1: 11) XXFILE;

This all works as I expect in debug *except* that once the 53 records
are retrieved nothing more that I can see happens. It acts like an
endless loop, but I just don't know what is happening.

Any suggestions would be most welcome.

Booth Martin

This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

This thread ...


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

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