Re: IF NOT %FOUND

[John Yeung <gallium.arsenide@xxxxxxxxx>]

On Tue, Nov 12, 2019 at 10:37 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
> Always prefer this approach because EOF on the first read represents a different condition (unexpected/error) whereas EOF on the second and subsequent reads is expected - in fact positively desirable!

EOF means the same thing regardless of where it happens. It can just
as easily be that you don't really expect any records on the first
read, or that you specifically expect multiple records.

If it is truly a different condition the first time around, then you
should be checking %EQUAL immediately after the SETLL and handling
your "error" without even attempting the read.

John Y.

> > On Nov 11, 2019, at 11:08 PM, Roger Harman <roger.harman@xxxxxxxxxxx> wrote:
> >
> > Well, not trying to (re)start the top/middle-tested loop argument, but I've always preferred this...
> >
> > setll (field1: field2) file1;
> > reade (field1: field2) file1;
> > dow NOT %eof(file1);
> >
> >   if someConditionIsMet;
> >       ...doStuff();
> >   endif;
> >
> >   reade (field1: field2) file1;
> > enddo;