RE: DOU/DOW for READ Loops (My final word)

[Chris Bipes <rpg@xxxxxxxxxxxxxxx>]

<snip>
Anyway, the important thing is to fully understand both methods because we
all will inevitably see both.  Now that I've added myself to this silly
debate, I'll sign off and watch the flames fly!  <g>
<snip>

I could not agree with you more.  We have several applications that have
complex record selections joining data from multiple files.  90% thru the
code, (hundreds of lines and several file reads later), we reject the record
and do not post or print it.  This is where ITER comes in handy.  Oops I
just skipped the read of the next record coded at the end of the DOW...Dam
it anyhow.

I have been known to use the DOU when the code within the loop is simple and
straight forward.  I use what works best for the application at hand.

Now the procedure that reads the record in the loop control example has
great promise.

DOW   GetNextRecord(FileName)
(Notice No More Leave!)
>
.
.
If condition = *fails
Iter
EndIf
.
.
.
ENDDO


I am going to give it a try when I get a Chance.


Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---