DFSMShsm selects 3592 Model E05 tape drives for output in SMS and
non-SMS tape environments. DFSMShsm performs all of its allocation
requests through these standard dynamic allocation interfaces:
- Non-SMS-managed output tape selection: If
multiple types of tape drives are installed that emulate the 3590
device type, you must define an esoteric name for each model that
DFSMShsm uses. You must then define the esoteric names to DFSMShsm
by using the SETSYS USERUNITTABLE(esoteric1:esoteric1,esoteric2:esoteric2,...) command.
You must also specify the esoteric names as the unit names for the
desired DFSMShsm functions. If a single type of tape drive is installed
that emulates the 3590 device type, or there is a mix of 3592 Model
E05 and J1A drives and the E05 drives are set-up to use EFMT1, you
do not have to define an esoteric name; instead, you can specify the
3590-1 generic name for the desired DFSMShsm functions.
- SMS-managed output tape selection: DFSMShsm
performs a non-specific allocation; it then finds an acceptable output
tape for the already allocated drive. If you use a 3590-1 generic
that contains mixed devices, see APAR OW57282 for information about
disabling the 3590-1 mixed device checking and the corresponding ARC0030I
failure message.