For TSM to use a device, you must install the appropriate device driver.
To identify and work with removable media devices, TSM needs the device's special file name.
When a device configures successfully, a logical file name is returned in the form of opx, mtx, or lbx, where x is a numerical value that indicates the instance of a device for a particular class.
The configuration manager creates the device special file name. In
this table, x denotes any number from 0 to 9.
Special File Name | Description |
---|---|
/dev/mtx | Used by all TSM-supported tape drives (not supported by IBM hardware device drivers) |
/dev/lbx | Used by most TSM-supported SCSI libraries |
/dev/ropx | Used by all TSM-supported optical drives |
/dev/rmtx | Used by the GENERICTAPE device type |
/dev/smcx | Used by 3570 and 3575 libraries, and used to define the Automatic Cartridge Facility feature of the IBM 3590 B11 as a library |
/dev/lmcpx | Used by 349X automatic tape libraries |
The following are examples of special file names:
Table 5. Examples of Device Special File Names
If the logical file name is: | The device special file name is: |
---|---|
mt3 | /dev/mt3 |
lb0 | /dev/lb0 |
op1 | /dev/rop1 |
rmt1 | /dev/rmt1 |
rmt1 |
Medium changer: (3590 B11 ACF, 3570, and
3575)/dev/rmt1.smc
|
lmcp0 | /dev/lmcp0 |
Note: | You must know the device special file name when you use the DEFINE DRIVE or DEFINE LIBRARY commands. The special file name is the value that you specify with the DEVICE= parameter. You can use the SMIT tool to get the device special file. |
For IBM 3490, 3570, and 3590 devices, see IBM SCSI Device Drivers: Installation and User's Guide for how to install the device drivers.
After completing the procedure in the manual, you receive a message from the system:
rmtx Available
where x is a number. Note the value of x, which is assigned automatically by the system. Use this information to complete the Device Name field on the worksheet.
For example, if the message is rmt0 Available, the special file name for the device is /dev/rmt0. Enter /dev/rmt0 in the Device Name field for the drive on the worksheet. Always use the /dev/ prefix with the name provided by the system.
rmtx Available
Note the value of x, which is assigned automatically by the system. The special file name for the drive is /dev/rmtx. The special file name for the media changer device (what TSM considers a library) is /dev/smcx. (The filetype smc stands for SCSI media changer.)
For example, if the message is rmt0, enter /dev/rmt0 in the Device Name field for the drive. Enter /dev/smc0 in the Device Name field on the worksheet for the library's robotics. Always use the /dev/ prefix with the name provided by the system.
Note: | For multidrive devices (for example, IBM 3570 Model B12 or B22, or IBM 3575), you need only one smcx. Although you will receive a /dev/smcx for each rmt device in the library, you need only one smc for the TSM library on the worksheet. |
For an IBM 3494 or 3495 Tape Library Dataserver, refer to either IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers or IBM AIX Parallel and ESCON Channel Tape Attachment/6000 Installation and User's Guide.
After completing the procedure in the manual, you will receive a message (logical filename) of the form:
lmcpx Available
where x is a number assigned automatically by the system. Use this information to complete the Device Name field on your worksheet.
For example, if the message is lmcp0 Available, enter /dev/lmcp0 on the worksheet in the Device Name field for the library. Always use the /dev/ prefix with the name provided by the system.
Use the procedure in this section to configure TSM device drivers for autochangers and robot devices, excluding IBM 3494 and IBM 3495 tape libraries. See Installing Device Drivers for IBM 349X Libraries for the IBM 3494 and 3495 tape libraries.
The term robot is defined as a device that performs programmed operations or that operates by remote control.
Run the SMIT program to configure the device driver for each autochanger or robot:
For example, a connection address of 40 has a SCSI ID=4 and a LUN=0. If you are using AIX Version 4.1, then a connection address of 4,1 has a SCSI ID=4 and LUN=1. You need a comma (,) between the SCSI ID and the LUN.
You will receive a message (logical filename) of the form lbX Available. Note the value of X, which is a number assigned automatically by the system. Use this information to complete the Device Name field on your worksheet.
For example, if the message is lb0 Available, the Device Name field is /dev/lb0 on the worksheet. Always use the /dev/ prefix with the name provided by SMIT.
Use the procedure in this section to configure TSM device drivers for tape or optical drives, excluding IBM 3490, 3570, and 3590 tape drives. See Installing Device Drivers for IBM 3490, 3570, and 3590 Tape Drives.
Attention: TSM cannot write over tar or dd tapes, but tar or dd can write over TSM tapes.
Note: | Tape drives can be shared only when the drive is not defined to TSM or TSM is not started. The MKSYSB command will not work if both TSM and AIX are sharing the same drive or drives. To use the operating system's native tape device driver in conjunction with a SCSI drive, the device must be configured to AIX first and then configured to TSM. See your AIX documentation regarding these native device drivers. |
Run the SMIT program to configure the device driver for each drive (including drives in libraries) as follows:
For example, a connection address of 40 has a SCSI ID=4 and LUN=0. If you are using AIX Version 4.1, then a connection address of 4,1 has a SCSI ID=4 and LUN=1. You need a comma (,) between the SCSI ID and the LUN.
The message you receive next depends on whether you are configuring the device driver for a tape or an optical device:
For example, if the message is mt0 Available, the Device Name field is /dev/mt0 on the worksheet. Always use the /dev/ prefix with the name provided by SMIT.
For example, if the message is op0 Available, the Device Name field is /dev/rop0 on the worksheet. Always use the /dev/r prefix with the name provided by SMIT.
Removable file support includes ZIP drives, Iomega JAZ drives, and CD-ROM.
Support for removable file devices allows portability of media between UNIX systems. It also allows this media to be used to transfer data between systems that support the media. Removable file support allows TSM to read data from a FILE device class that is copied to removable file media through third-party software. The media is then usable as input media on a target TSM server that uses the REMOVABLEFILE device class for input.
Note: | Software for writing CD-ROMs may not work consistently across platforms. |
Use a MAXCAPACITY value that is less than one CD-ROM's usable space to allow for a one-to-one match between files from the FILE device class and copies that are on CD-ROM. Use the DEFINE DEVCLASS or UPDATE DEVCLASS commands to set the MAXCAPACITY parameter of the FILE device class to a value less than 650MB.
Use these steps as an example of TSM REMOVABLEFILE (CD-ROM) support. This example takes an export object and moves it from one server to another.
Server A
define devclass file devtype=file directory=/home/user1
export node user1 filedata=all devclass=file vol=cdr03
You can use software for writing CD-ROMs to create a CD with volume label CDR03 that contains a single file that is also named CDR03.
Server B
mount -r -v cdrfs /dev/cd0 /cdrom
Note: | CD-ROM drives lock while the file system is mounted. This prevents use of the eject button on the drive. |
define library cdrom libtype=manual
define drive cdrom cddrive device=/cdrom
define devclass cdrom devtype=removablefile library=cdrom
import node user1 filedata=all devclass=cdrom vol=cdr03
TSM does not provide utilities to format or label media for the REMOVABLEFILE device type. You must use another application to copy the FILE device class data to the CD-ROM to a file that has the same name as the volume label. This software also labels the removable media.
The label on the media must meet the following restrictions: