On Mon, 14 Jan 2013 15:05:47 -0600, Paul Gilmartin wrote:
>
>>I've never used BPXWDYN, but I do know that the ancient practice of
>>FREEing a file that is not currently allocated educes a message to that
>>effect. On the other hand, ALLOCATing with REUSE works 'cleanly' whether
>>or not the file is already allocated. ...
>>
>False for TSO ALLOCATE.
>
I'm delighted to correct myself on this. While
Title: z/OS V1R13.0 TSO/E Command Reference
Document Number: SA22-7782-14
... the description of the PATH operand of ALLOCATE implies that REUSE
must not be used with PATH, and this used to be enforced (until which
release?), I find that at 1.12 the combination is accepted. RCF time.
>I've never understood the whole subject of reusing allocations, and marking
>allocations eligible for reuse. Is there some horrendous overhead this
>avoids? was this true only historically, or does it remain a concern nowadays?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
