Natasa,
>in order to prevent releasing of unused space for some datasets, I
allocated it
>yesterday with MC that has Partial release parameter set to 'No'.
However,
>today when I look at some of those datasets, they look like the space
was
>first released (primary extent is 1 cyl, allocated was 200), and then
as the
>data was loaded it took 11 secondary extents. This is exactly what I
wanted
>to prevent. Can someone explain to me how this happened?
Is it possible that the data set was migrated/recalled before loading?
>From DFSMShsm Storage Administration Guide:
2. The PARTIAL RELEASE attribute does not apply to normal migration and
recall processing.
Related reading: For more information about migration and recall space
allocation, see "Additional Space Management during Migration and Recall
When DFSMShsm Is the Data Mover" in topic 2.1.21.7.
Regards,
Hermann
----------------------------------------------------------------------
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
