Re: Loop code

Sorry jt, but I think this makes perfect sense.

If a CHAIN is successful, it means you got a record, so you are not at EOF,
so %EOF(filename) is set off.

If a CHAIN is unsuccessful, the file pointer is left where it was, so
%EOF(filename) is unchanged.

An unsuccessful chain does not position the file pointer at EOF - so why
would it set on %EOF?

Paul Tuohy

----- Original Message -----
From: "jt" <jt@xxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Friday, March 26, 2004 7:35 PM
Subject: RE: Loop code


> This part seems ENTIRELY UNintuitive.  Is there some benefit or Reason WHY
> it would NOT change??  What logic went into this decision, if I may ask?
> (Obviously, I may ask, but it might never get posted nor answered, of
> course...;-)
>
> | -----Original Message-----
> | [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Paul Tuohy
> | Sent: Friday, March 26, 2004 12:37 PM
>
> | "The following operations, if successful, set %EOF(fielname) off. If the
> | operation is not successful, %EOF(filename) is not changed."