Re: Chain doesn't set %EOF

Duane,

The only reason to use the Chain is to avoid having to keep the same key
lists on the SetLL and ReadE statements.  An earlier discussion about DoW
and DoU loops had the same point about two ReadE statements.  I agree with
you that it's a coding style issue.  Tommy views it as verging on a bug.

In practice it's a minor annoyance when converting RPGIII code to Free
Format.  Trying to keep code changes to a minimum but still improve the
code.  Replacing the common work indicator with %EOF is the most
straightfoward but have to replace the Chain with SetLL/ReadE to use %EOF.

Paul

-- 
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333

"Christen, Duane J." wrote

> Paul;
>
> Here is the ANI Masters team at McLeodUSA.
>
> It is considered bad coding practice here because a Chain implies a single
> record fetch, where a SetLl/ReadE combination implies the start of a
looping
> condition. Saving one little SetLl line of code, to me, is not worth
losing
> the implied logic.
>
> I know that this is probably more of a "coding style" preference than
> anything else, but no one has been able to give me a reasonable argument
for
> using Chain in this case, and the developers on my team don't really care
> either way.
>
> Duane