I got E37 space abend for one of the LOADLIBs. When checked %usage was 99% with 3 extent. Compressing this PDS did not release space. I allocated larger LOADLIB with increased PRIM, SEC and directory blocks. This created a PDS with 20% free space. However, overnight additional space was released and next day same dataset was showing 99% used. I think as part of DFHSM process this free space would have been released.
Can someone help in allocating a space where free space will not be released either by DFHSM housekeeping process or weekend volume defragmentation job.
Joined: 28 Aug 2007 Posts: 1647 Location: The Good Place
You could check if the management class the dataset allocated has PARTIAL RELEASE set to YES. And ask your storage management guys the management class which does not have PARTIAL RELEASE.
You could see this in ISMF.
PARTIAL The value in the PARTIAL RELEASE data column shows whether or
RELEASE not unused space can be automatically released for the data sets
----(6)---- in this management class. Partial Release applies only to VSAM
YES data sets in extended format, or non-VSAM data sets.
YES Release unused space automatically during the
Space Management cycle.
CONDITIONAL Unused space can be released automatically only
if a secondary allocation exists for the data set.
YES IMMED Release unused space when a data set is closed or during
the Space Management cycle, whichever comes first.
COND IMMED Unused space for data sets with secondary allocation is
released either when a data set is closed or during the
Space Management cycle, whichever comes first.
NO Do not release unused space.
Note that for Extended VSAM data sets, CONDITIONAL or COND IMMED is
treated the same as YES or YES IMMED.
The following special characters may appear in this data column:
??????????? The value cannot be displayed because of a data