3480, 3490, and 3490-E mainframe cartridge tape can be handled in a variety of ways. Most obviously, traditional physical channel-attached tape drives may be attached via the PCA. This is not covered in this chapter.
All other methods of handling mainframe cartridge tape involve the use of emulated control units of one of the following types
Emulated control units of these types can attach drives which utilize several software and hardware technologies:
Emulated control units of these types (3480, 3490) and their devices may be specified without regard to the technology of the tape device itself. The tape unit will automatically detect the type of device it is to be.
3480-style tape devices should not be specified in conjunction with 3420-style SCSI-attached devices. Doing so is very unlikely to work.
In the resource definition fragment below, an emulated 3490 control unit is defined and named "cu3490uw". It cannot be "cloned", since physical resources (3490-class SCSI-attached tape drives) are associated with its devices. It is defined to be on channel path (interface) 1, which is a local channel path (not a network channel path). It employs device special filename of a type appropriate for UnixWare. You must, of course, use device special filename appropriate for the tape drives on your system.
Four devices are defined on this controller. The first device is a SCSI-attached 3490 cartridge tape. The second device is a SCSI-attached 3490-E cartridge tape. The third device is a FLEX-ES emulated tape associated with the specified server disk file. The fourth device is defined to be an OFFLINE 3490. If it is to be used, a tape file name would be specified interactively via a CLI mount command. The file specified could be either a FakeTape file or a SCSI tape device special file.
cu3490uw: cu 3490 interface local(1) device(00) 3490 /dev/rmt/ctape1 device(01) 3490-E /dev/rmt/ctape2 device(02) 3490 /var/tapes/t1 device(03) 3490 OFFLINE # tape name filled in by CLI mount command end cu3490uw