Track management for non-SMS-managed volumes

The ADDVOL command has an optional keyword TRACKMANAGEDTHRESHOLD(high low).
  • Alias: TMT
  • TMT is only valid with the PRIMARY keyword
  • High and low are required parameters
TRACKMANAGEDTHRESHOLD can be used to define the high and low thresholds for the track-managed space of a non-SMS PRIMARY EAV. If TRACKMANAGEDTHRESHOLD is not specified, then the corresponding values for THRESHOLD will be used. If no threshold values are specified, then all threshold values will use the default values. If TRACKMANAGEDTHRESHOLD is specified for a non-EAV, the ADDVOL command will fail. For example: 
ADDVOL PRIM01 PRIMARY UNIT(3390) TRACKMANAGEDTHRESHOLD(80 40) THRESHOLD(85 60)

In the above example the parameter TRACKMANAGEDTHRESHOLD(80 40) defines a high track-managed threshold of 80 percent and low track-managed threshold of 40 percent. If TRACKMANAGEDTHRESHOLD is not specified, then the corresponding values for THRESHOLD will be used.

If no THRESHOLD keyword values are specified, then all threshold values will use the default values. The default high value is 100, and the default low value is 0. Therefore, a primary volume has no valid default thresholds in this case. If the attributes of a volume are being changed but track-managed space threshold values are not specified, the track-managed space thresholds are not changed. If, however, the new high track-managed threshold is less than or equal to the low track-managed threshold or is equal to 100, the volume threshold values will be used as track managed threshold values.

For more information, see TRACKMANAGEDTHRESHOLD: Specifying the high and low threshold for the track-managed space of a non-SMS level 0 extended address volume in ADDVOL command: Adding or changing DFSMShsm volumes.