I see:
16.6.2 "z/OS V1R7.0 MVS JCL Reference"
___________________________________________________________________
16.6 DYNAMNBR Parameter
16.6.2 Subparameter Definition
n
Specifies a value used to calculate the maximum number of data
set allocations that the system can hold in anticipation of
reuse. Specify n as a decimal number from 0 through 3273 minus
the number of DD statements in the step.
...
But I just successfully ran a job step with DYNAMNBR=120 which
allocated 340 DDNAMEs without freeing any. But a similar job
with about 1000 allocations failed.
Certainly I don't understand the significance of "hold in anticipation
of reuse". Is it possible that the bulk of my allocations (to Unix
files) were not so held? The UG, cited later on the page doesn't
help much.
What's really happening? Would I be able to do my 1000 allocations
(subject to TIOT limitations) if I specified DYNAMNBR=1000?
Thanks,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
