DAOPTION: Selecting target volume track length

Explanation: DAOPTION(SAMETRK | RELTRK | RELBLK) are mutually exclusive, optional parameters specifying the type of data set accessing required (relative track or relative block) upon recall of a direct access data set. This, in turn, implies the allowable target volume device types.

Subparameter Explanation
SAMETRK If DFSMShsm is not directed to a volume by the VOLUME parameter, it selects a target volume having the same track length as the last L0 volume from which the data set was migrated. If DFSMShsm is directed to a specific volume by the VOLUME parameter, this volume must have the same track length as the last L0 volume from which the data set was migrated. Data will be moved as a track-to-track image, accessible for both relative track and relative block processing.
RELTRK If DFSMShsm is not directed to a volume by the VOLUME parameter, it attempts to select a target volume having the same track length as the last L0 volume from which the data set was migrated. If no volume of equal track length is available, the target volume selected may have a larger track length than the last L0 volume. If DFSMShsm is directed to a specific volume by the VOLUME parameter, this volume must have the same or greater track length than the last L0 volume from which the data set was migrated. Data is moved as a track-to-track image, accessible by relative track addressing.
RELBLK If DFSMShsm is not directed to a volume by the VOLUME parameter, it attempts to select a target volume having the same track length as the last L0 volume from which the data set was migrated. If no volume of equal track length is available, the target volume selected may have a larger or smaller track length than the last L0 volume. If DFSMShsm is directed to a specific volume by the VOLUME parameter, this volume can have any track length. Data will be moved to fill out the track, accessible by relative block addressing.

Defaults: If DAOPTION is not specified, the target volume selection is unchanged and data is moved as a track image, allowing for relative track addressing.

Note: Only basic direct access method (BDAM) data sets are supported by this option. Using DAOPTION to recall a data set as SMS-managed is not supported. If a data set would be SMS-managed after the recall, the FORCENONSMS parameter of RECALL must be used to force it to be non-SMS-managed.