Re: CHAIN not found and subsequent READ - docs wrong?

On Fri, Dec 18, 2015 at 9:47 AM, Kurt Anderson
<Kurt.Anderson@xxxxxxxxxxxx> wrote:

I see what you're saying, but I think the documentation is speaking to a very specific situation wherein you did not do a Read before your Chain that is chaining out to the very same record. In that case success would position the file to where you Chain'd to, and a failed chain wouldn't reposition the file, but in your scenario the position of the file is already there.

Kurt, the reason that I disagree with your reading of the docs is that
they would have phrased things differently if they really meant what
you are saying. The docs would have read:

<hypothetical quote>
When the CHAIN operation is not completed successfully (for example,
an error occurs or no record is found), the file specified in name is
not repositioned.
</hypothetical quote>

Given how thorough the docs are, they probably also would have gone on
to specifically say that if the file has already been positioned by a
previous operation, then a subsequent read would proceed from that
position, but if the file has not yet been positioned, then a
subsequent read operation would be unsuccessful.

John Y.