Author: Robert Sample
Subject: Reply to: Release quantity that was allocated via LIKE= subparm
Posted: Thu May 18, 2017 6:24 pm (GMT 5.5)
I suspect what you want to do is not possible unless you explicitly code the SPACE parameter in the job creating the new data set. From the JCL Reference manual (emphasis added by me):
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Subject: Reply to: Release quantity that was allocated via LIKE= subparm
Posted: Thu May 18, 2017 6:24 pm (GMT 5.5)
I suspect what you want to do is not possible unless you explicitly code the SPACE parameter in the job creating the new data set. From the JCL Reference manual (emphasis added by me):
| Quote: |
| Use the LIKE parameter to specify the allocation attributes of a new data set by copying the attributes of a model data set, which must be an existing cataloged data set and reside on a direct access volume. The following attributes are copied from the model data set to the new data set: Data set organization Record organization (RECORG) or Record format (RECFM) Record length (LRECL) Key length (KEYLEN) Key offset (KEYOFF) Type, PDS, PDSE, basic format, extended format, large format, or HFS (DSNTYPE) Space allocation (AVGREC and SPACE) Unless you explicitly code the SPACE parameter for the new data set, the system determines the space to be allocated for the new data set by adding up the space allocated in the first three extents of the model data set. Therefore, the space allocated for the new data set will generally not match the space that was specified for the model data set. Note that regardless of the units in which the model data set was allocated, the new data set will be allocated in tracks. This assumes that space was not specified on the JCL and is being picked up from the model data set. |
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth