| Subparameter | Explanation |
|---|---|
| DATASSETSIZE(dssize) | Specifies the minimum size, in K
bytes, of the data set for which an ML1 OVERFLOW volume is preferred
for migration or backup. This includes invoking inline backup,
the HBACKDS or BACKDS commands, or the ARCHBACK macro.
SMS relationship: Parameter has the same meaning when applied to SMS-managed or non-SMS-managed DASD volumes or data sets. SETSYS default: 2000000 K bytes. DFSMShsm default: If you do not specify this parameter on any SETSYS command, DFSMShsm will use the value of 2000000 K bytes. If the calculated size of a data set being backed up or migrated is equal to or greater than dssize, DFSMShsm prefers the OVERFLOW ML1 volume with the least amount of free space that still has enough remaining space for the data set. If the calculated size of the data set is less than the minimum size specified in dssize, DFSMShsm prefers the NOOVERFLOW ML1 volume with the maximum amount of free space and least number of users. |
| THRESHOLD(threshold) | Specifies the percent of occupied
space in the ML1 OVERFLOW volume before migration of data sets to
ML2 volumes during automatic secondary space management. DFSMShsm
calculates the percentage of occupied space for each ML1 OVERFLOW
volume and then compares the average value with the specified threshold.
If the average of the ML1 OVERFLOW volume pool has an occupancy that
is equal to or greater than the threshold, then secondary space management
is started and moves data from ML1 to ML2.
SMS relationship: Parameter has the same meaning when applied to SMS-managed or non-SMS-managed DASD volumes or data sets. SETSYS default: 80%. DFSMShsm default: If you do not specify this parameter on any SETSYS command, DFSMShsm will use the value of 80%. |