Re: READE question

�
Hi, Hoteltravelfundotcom, I hope it's not your real name :). As I see in
this code you don�t need use any indicators for reade, also you can use
simply read. May be if you shift dow to other place my answer will be
different. You always read only first record in you block of data. And if
you find such record it is endless cycle except you change key field.

Best regards, Alex.
� � � 05.03.2016, 01:23, "Jerry Adams" <midrange@xxxxxxxx>:

Evil : Crabby? It's all in the eye of the beholder.
But, seriously, what's Susan's take on it? .-)

Jerry C. Adams
I'd like to offer moral support, but I have questionable morals.
IBM i Programmer/Analyst

--
NMM&D
615-832-2730

-----Original Message-----
From: RPG400-L [mailto:[1]rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jon Paris
Sent: Friday, March 04, 2016 12:04 PM
To: Rpg400 Rpg400-L
Subject: Re: READE question

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

[2]www.partner400.com
[3]www.SystemiDeveloper.com

�On Mar 4, 2016, at 12:51 PM, Hoteltravelfundotcom
<[4]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:
[5]RPG400-L@xxxxxxxxxxxx
�To subscribe, unsubscribe, or change list options,
�visit: [6]http://lists.midrange.com/mailman/listinfo/rpg400-l
�or email: [7]RPG400-L-request@xxxxxxxxxxxx Before posting, please
take a
�moment to review the archives at
[8]http://archive.midrange.com/rpg400-l.

�Please contact [9]support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: [10]RPG400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: [11]http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [12]RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[13]http://archive.midrange.com/rpg400-l.

Please contact [14]support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: [15]RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [16]http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [17]RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [18]http://archive.midrange.com/rpg400-l.

Please contact [19]support@xxxxxxxxxxxx for any subscription related
questions.

References

Visible links
1. mailto:rpg400-l-bounces@xxxxxxxxxxxx
2. http://www.partner400.com/
3. http://www.systemideveloper.com/
4. mailto:hoteltravelfun@xxxxxxxxx
5. mailto:RPG400-L@xxxxxxxxxxxx
6. http://lists.midrange.com/mailman/listinfo/rpg400-l
7. mailto:RPG400-L-request@xxxxxxxxxxxx
8. http://archive.midrange.com/rpg400-l
9. mailto:support@xxxxxxxxxxxx
10. mailto:RPG400-L@xxxxxxxxxxxx
11. http://lists.midrange.com/mailman/listinfo/rpg400-l
12. mailto:RPG400-L-request@xxxxxxxxxxxx
13. http://archive.midrange.com/rpg400-l
14. mailto:support@xxxxxxxxxxxx
15. mailto:RPG400-L@xxxxxxxxxxxx
16. http://lists.midrange.com/mailman/listinfo/rpg400-l
17. mailto:RPG400-L-request@xxxxxxxxxxxx
18. http://archive.midrange.com/rpg400-l
19. mailto:support@xxxxxxxxxxxx