There are many examples where data is consumed as it is read and you
can't go back and read it again. E.g. network socket, pipe, terminal or
(historically) card reader. Datasets, where you can read them multiple
times, are more the exception than the rule here.
FREE=CLOSE sounds like good API design because it signals that the
DDNAME is only intended to be read once, and attempts to close and
reopen it should fail. Finding a way to override FREE=CLOSE doesn't seem
like a good idea, because even if it works in testing you are breaking
an implied contract in the API and there is no guarantee that it will
always work. You might find that there are circumstances where you get
totally different data, or it fails completely.
Andrew Rowley
Black Hill Software
+61 413 302 386
On 21/11/2015 6:41, Paul Gilmartin wrote:
I shouldn't have implied "caller" The DDNAME was "passed" in a reply
from the SDSF API. So I wish there were an option to suppress "FREE=CLOSE.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
