Re: FEOD followed by Setll

["alan" <steelville@xxxxxxxxx>]

<snip>
Write file
FEOD
*hival Setll file
Read file
%eof is set immediately.
</end snip>

Martin,

I would suspect that the FEOD does indeed set the %eof
indicator, but that the SETLL does not. This makes sense to
me, and sounds to me like it *should* work this way. For
example in the following scenario (in a "normal"
ascending-order-keyed file):

keyfield setgt FileA

At this point, the program *should not* know whether it is
at the end of the file yet or not. But at the next attempt
at input in this scenario, the status of the file will be
set at %EOF.

It does make you do a double-take though.

But curiosity drives me to ask, Why do an FEOD and then
re-position the file?

- Alan

+++++++++++++++++++++
----- Original Message -----
From: "Saunders, Martin P" <martin.saunders@xxxxxxxx>

| Hi Booth,
|
| I read that bit in the manual ('you must reposition the
file'), I thought
| that is what the SETLL would do.
|
| BTW: to the other people who replied: thanks for the
suggestion but the
| reason I am using *HIVAL is because the file is keyed
descending.  Reading
| the file in this way in a separate program works fine.
|
| Thanks
|
| Martin