× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Repeat after me NO INDICATOR IS EVER NEEDED ON I/O OPERATIONS <evil grin>.

Since you’re changing the code anyway why not get rid of the fixed form and indicator rubbish and do it right with the appropriate BIFS. In this case %Equal and %EOF.

But if you insist on sticking to RPG III code then the answer is Yes - you need to detect EOF on the READE or you can never terminate the loop.


Jon (Still feeling crabby) Paris

www.partner400.com
www.SystemiDeveloper.com

On Mar 4, 2016, at 12:51 PM, Hoteltravelfundotcom <hoteltravelfun@xxxxxxxxx> wrote:

Do I need an Indicator here on the READE?
I haven't coded this in a very long time.

c *in90 doweq *off
c poh setll srbpoh 90
c *in90 ifeq *off
c poh reade srbpoh
c ohords iflt 30
c eval ohsrom = whs
c update orphe
c endif
c endif
c Enddo

c parms plist
c parm ponum 1200
c parm whs 3
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.