Re: %EOF, %FOUND and the infamous Dow loop

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Joe,

You wrote:
>The IF/DOU is very inelegant to me (an enddo followed by an endif for the
>same loop is quite unappealing), so I suspect I will be moving back to
>the SETLL/READE loops of yesteryear, as outlined by Martin in an earlier
>post.

Now that really is just a style choice.  Some languages won't let you
combine two different return codes in the manner allowed by RPG when using
indicators so you would have to do the IF/DOU style construct.  Checking
the return code from I/O operations immediately after that operation is no
different from consistently checking the return code from function calls.

However, either of the IF/DOU and the SETTLL/READE versions is nicer than
the
C       value   SETLL   file
C               DOW     (not(%EOF)
C               READE
C               IF      (%eof)
C               LEAVE
C               ENDIF
 *    process here
C               ENDDO
abomination.

Oh damn!  This is starting the DOU/DOW wars all over again.  Arrgghh!

Also, SETLL followed by READE for the same key is less efficient than a
CHAIN so ...

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------