RE: %EOF

[Chris Bipes <ChrisB@xxxxxxxxxxxxxxx>]

Have you ever had to skip a record and tried using "ITER" in your loop?  I
also use the:
"IF EOF LEAVE"  after the read at the top of the loop.  It is easier when
you have a lot of code within the loop to ITER than to skip with an IF/ENDIF
or, should I dare say, GOTO.  Agreed that having the initial read prior to
the loop and at the bottom of the loop gives the loop control to the loop
definition, but I like ITER/LEAVE myself.

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



-----Original Message-----
From: Stone, Brad V (TC OASIS) [mailto:bvstone@taylorcorp.com]
Sent: Friday, June 18, 1999 6:14 AM
To: 'RPG400-L@midrange.com'
Subject: RE: %EOF 


Key        SETLL    Filename
Key        READE    Filename
 
            DOW   not %EOF(Filename)
 
        (do some code here)
Key        READE    Filename
            Enddo
 
 Change it to this...  More structurally correct as well.

Bradley V. Stone 
BVS/Tools 
http://www.bvstools.com <http://www.bvstools.com/>  

-----Original Message-----
From: Nelson C. Smith [mailto:ncsmith@gate.net]
Sent: Thursday, June 17, 1999 8:04 PM
To: RPG400-L@midrange.com
Subject: %EOF 


Has anyone here had problems associating a filename with the %EOF bif?  I've
been experiencing intermittent problems which seem to be occuring only in
service programs.  When I pull the code out to a separate program to try to
isolate it, it works fine (naturally).  Here's what I'm seeing:
 
Key        SETLL    Filename
 
            DOU    %EOF(Filename)
Key        READE    Filename
 
             If          %EOF(Filename)
                Leave
            Endif
 
            If            %EOF
                Leave
            Endif
 
        (do some code here)
            Enddo
 
When executing this code against an empty file, the first LEAVE does not
execute, but the second one does.  When I put a numeric indicator on the
READE, it comes on normally.  This is the entire code in a procedure in a
service program (second LEAVE was added in testing) and, as I say, when
pulled out into a test program it works fine.  Does anyone know how the
filename gets associated with the %EOF and what might disrupt that
association?  There is no code between the READE and the first IF.  I'm on
V4R3.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *