On Sep 24,  8:16am, Pete Crosby wrote:
>          Is their some reason why you can't just extract the current
> EOF from the GUFD? You are obviously following the PLFD/GDPD links to
> find the accessors if the file is open so why not just get the EOF
> from the GUFD if the file is open or from the file label if it is not?

Jeff Woods said the same thing, and I like this idea a lot.  What this means
to those of you that are not as familiar with our file system internal
data structures is: if the file is being accessed then LISTF,2 will report
the eof value in memory (not from the file label on disk).  If the file
is not being accessed at the time LISTF is executed then the eof value
will be obtained from the label on disk as is done now.

This seems to be the best of all alternatives.  We get the best performance
from LISTF and LISTF will never hang, plus you will be able to see accurate
eof values for the current LISTF (not the from the prior one).  I am
looking at the code now and will get back to you if this doesn't pan out.

Thanks for the feedback!

Jeff Vance, CSY

--