File I/O BIFs

We have been getting strange results using the Opcode extender
'E' on I/O opcodes and the file I/O BIFs (%EOF & %FOUND).

We have the standard where you use the 'E' on I/O opcodes.
Then when using the BIFs, you specify the filename after it.
Just a way to further define just exactly what the BIF is working on.

The problem is that on occasions the BIF will not work correctly.
It will return the wrong value.  A load DOW will loop because of
this.  When we change the BIF to an indicator, everything works
fine.   If we do NOT specify the filename after the BIF it will work
right.

This problem will not happen in all cases. Can't really track down 
a pattern to it.

Has anybody else experienced this problem??  Is there
a fix available?

--  THANKS
------------------------------------------------------
Scott P. Johnson
Programmer/Analyst
IBM Certified Specialist - AS/400 RPG Programmer
Highsmith Inc.
W5527 Hwy 106, PO BOX 800
Fort Atkinson, WI 53538-0800
TEL:  920-563-9571                FAX:  920-563-7395
sjohnson@highsmith.com
www.highsmith.com
------------------------------------------------------

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---