Specific example

   USERUNITTABLE(SPOUT,DPOUT,MIGOUT:RECIN,BACKUP:RECIN)

This example specifies five esoteric tape unit names. When you specify single esoteric tape unit names (without a colon, like SPOUT and DPOUT), any translations that occur are allocated to generic tape units. When you specify paired esoteric tape unit names (with colon separators, like MIGOUT:RECIN and BACKUP:RECIN), any translations that occur are to the specified tape unit name (RECIN in this case) and that is what will be used during later input allocations.

NOUSERUNITTABLE specifies that no esoteric tape unit names are identified to DFSMShsm. Any previously defined esoteric names are no longer known to DFSMShsm.

SMS relationship: Parameter differs in meaning when applied to SMS-managed or non-SMS-managed DASD volumes or data sets.

Tape Library Relationship: Translation can occur for SMS tapes. However, the ACS routines can modify the resulting tape devices used. Tapes are read back on drives available to the library where the tape is resident.

SETSYS default: None.

DFSMShsm default: If you do not specify this parameter on any SETSYS command, the DFSMShsm default is NOUSERUNITTABLE.
Note:
  1. If there is no unit online and available for the esoteric when the SETSYS USERUNITTABLE is issued, you will receive message ARC0103I indicating the USERUNITTABLE is invalid.
  2. For IBM® 3490 and 3590 tape devices, esoteric translation always occurs, regardless of the existence of cartridge loaders. If you specify a 3490 or 3590-1 esoteric unit name to direct output tape allocations, a translation of that esoteric unit name occurs. Subsequent input allocations use that translated unit name. Therefore for 3490 or 3590-1, if you specify an output esoteric unit name and want the same esoteric unit name to be used for that tape’s input allocations, you must specify a translation to itself. For example, SETSYS USERUNITTABLE(TAPE:TAPE).
  3. The 3490 control units (models A01, A02, A10, A20, D31, and D32) have the same read and write capabilities as the 3480X control unit.
  4. You must ensure that each tape unit belonging to the esoteric group you specify can read and write on any tape written by any other tape unit that belongs to the same esoteric group. If the esoteric group contains both 3480 and 3480X devices, DFSMShsm treats both types of devices as 3480s.
  5. If an esoteric group includes one set of the tape drives defined with compaction on and another set defined with compaction off, this latter group of drives will not be able to read compacted data by the first group. Thus, the esoteric is considered invalid and message ARC0103I will be received when the SETSYS USERUNITTABLE command is issued.
  6. You must define all esoteric tape unit names during system I/O generation. Do not remove from a subsequent system I/O generation those esoteric tape unit names DFSMShsm already has used during its tape processing. If you do, DFSMShsm cannot allocate the tape volume whose esoteric unit name you specified when you issued the ADDVOL command. Basically, by removing the esoteric name, you make the esoteric name an invalid unit name.
  7. DFSMShsm rejects mixed combinations of device names in an esoteric group, with the following exception: it allows the use of both 3480 and 3480X device names in a single group. Improved Data Recording Capability (IDRC), however, is not used with such a group because all devices in the group are treated as 3480s. If an esoteric group associated only with 3480Xs exists, 3480s should not be added to it, because the data already written using this esoteric tape unit name may create IDRC incompatibilities. 3592-1, 3592-2 and 3592-2E tape units are allowed into the same esoteric since they share common write formats. 3592-2, 3592-2E, and 3592-3E tape units are allowed into the same esoteric since they also share common write formats. 3592-3E and 3592-4E tape units are allowed into the same esoteric since they also share common write formats. It is up to the user to ensure the drives in the mixed esoteric will be used with a common recording technology write using the same recording technology. For example, if any 3592-1 drives are included, then all drives in the esoteric must use EMFT1 for output. If the esoteric mixes 3592-2 and 3592-2E drives, then all drives must be setup to use EFMT1 or EFMT2. If the esoteric contains mixed 3592-3E and 3592-2E tape units, then all drives must be set up to use EFMT2 or EEFMT2, the write formats they have in common. If the esoteric contains mixed 3592-4E and 3592-3E tape units, then all drives must be set up to use EFMT3 or EEFMT3, the write formats they have in common.

    If DFSMShsm rejects an esoteric tape unit name, it does not reject the rest of the valid esoteric names specified in the USERUNITTABLE command. Those names are now recognized by DFSMShsm as valid esoteric tape unit names. Each time you specify USERUNITTABLE, the valid esoteric tape unit names identified with this parameter replaces any esoteric tape unit names identified with a previous USERUNITTABLE parameter of the SETSYS command.

  8. If you define both 3592-E05 and 3592-J1A to the same esoteric group, the E05 must use the EFMT1 recording format.
  9. You can define a 3592-E05 or 3592-J1A to the 3590-1 generic group. If so, you must ensure drive compatibility or segregation when using the 3590-1 in a non-SMS environment.
  10. If an esoteric group includes a mixture of cartridge loader and non cartridge loader units, the esoteric name translation does not take place. It is important to note that for translation to occur, at least one unit associated with the esoteric tape unit name es2out must be varied online, and all online units associated with es2out must have cartridge loaders or be 3490s. The unit name used by DFSMShsm for input is described in "Implementing DFSMShsm tape environments" in z/OS DFSMShsm Implementation and Customization Guide.
  11. If you reenter a SETSYS USERUNITTABLE command be aware that the prior table is entirely deleted and a new one is built from the new command and the MVS™ esoteric definitions. This will likely necessitate that you also enter the SETSYS TAPEUTILIZATION command because defaults are again in use. If you have removed an esoteric that is used in a tape output restriction specification, such as SETSYS BACKUP(TAPE(es1)), then you will also need to change those specifications.
  12. To remove cartridge loader as a condition for device type 3480 esoteric unit name translation, refer to the topic "Tuning DFSMShsm" in z/OS DFSMShsm Implementation and Customization Guide.
  13. For a summary of esoteric translation results, refer to the topic "Summary of Esoteric Translation Results for Various Tape Devices" in z/OS DFSMShsm Implementation and Customization Guide.
  14. The esoteric values specified for certain SETSYS parameters cannot resolve to reel-type tapes. See Managing DFSMShsm media for details.
Parent topic: USERUNITTABLE and NOUSERUNITTABLE: Specifying esoteric tape unit names to DFSMShsm