| 
 | 
| 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. | 
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.