Processing non-SMS-managed data sets

There are two differences in processing for non-SMS-managed data sets:

No storage class, management class, and data class are received.
Data sets are recalled to the volume specified.

The target unit type need not be specified if the volume has been added to DFSMShsm by an ADDVOL command.

For non-SMS-managed data sets, DFSMShsm migrates the data sets to an ML1 volume and then recalls them to the volume specified by volser2. If volser2 is not specified, DFSMShsm selects the level 0 volumes to recall the data sets to in the manner specified in Recall. If volser2 has not been identified to DFSMShsm, use unittype2 to specify the type of unit that volser2 can be mounted on. If volser1 has not been identified to DFSMShsm, use the UNIT(unittype1) parameter to specify the type of unit that volser1 can be mounted on. To prevent selection of the source volume as the target volume for the recall, you must do two things:

Specify the volume to DFSMShsm with NOAUTORECALL in the ADDVOL command
Remove the volume from any pools of which it is a member

With BDAM data sets, when you specify a target volume on a different device type during DASD conversion, DFSMShsm recalls the data set you specify if the data on a track of the source volume fits on a track of the target volume. However, you are responsible for data addressability.

DFSMShsm maintains the same number of tracks for BDAM data set space during DASD conversion to a different device type. There is no change in the number of records per track, so space is wasted when you convert a BDAM data set to a DASD with a larger track size. DFSMShsm assumes that any user program accessing BDAM data depends on having the same relative track address.

DFSMShsm does not compact data sets or migrate them to SDSP data sets when it does DASD conversion.

If you specify the CONVERT parameter in a direct-to-tape environment, the command fails.