DSM/Tape Catalog User's Guide

Tape Library Control Path Configuration Guidelines
DSM/Tape Catalog User’s Guide 520233-008
7 - 6
Communicating With a Tape Library
4. Use the INFO TAPEDRIVE command to verify the location of the tape drives:
MC>INFO TAPEDRIVE
TapeDrive Name Device Type NL Check BLP Check LSM Drive ID
-------------- -------- --------- ------------------------
$TAPE MARATHON OFF ON Non-LSM Drive
$TAPE1 DAT OFF ON Non-LSM Drive
$SILO0 DLT4000 OFF ON (0,0,9,0)
$SILO1 DLT7000 OFF ON (0,0,9,1)
$SILO2 DLT7000 OFF ON (0,0,9,2)
$SILO3 DLT4000 OFF ON (0,0,9,3)
6 tape drives returned.
MC>
The INFO TAPEDRIVE command displays the LSM Drive ID for a tape drive after
you enter the LSM value using the MEDIACOM ALTER TAPEDRIVE command.
For tape libraries not using ACSLS, the tape drives are displayed as Non-LSM
drives.
5. If the wrong LSM DRIVEID is specified, rerun the ALTER TAPEDRIVE command
with the correct location.
6. Check if $ZSSI has any problems starting; for example, if TCP/IP is not up,
portmapper is not running, and so on. If so, $ZSSI generates EMS events
describing the failure. For more information on the Storage Server Interface and
the portmapper, see Section 8, Storage Server Interface (SSI) to the Tape Library
Control Path.
7. If you do not want an LSM DRIVEID for a tape drive, use the RESET LSM option
to remove any LSM assignment for a tape drive:
MC>ALTER TAPEDRIVE $TAPE, RESET LSM
1 tape drive altered.
MC>
8. After you have finished mapping the tape drive name to the physical location in the
tape library, exit MEDIACOM:
MC>EXIT
22>
Communicating With a Tape Library
For tape libraries using ACSLS, the Storage Server Interface process, $ZSSI, is started
on the NonStop Kernel system after the first tape drive name is mapped to the physical
location of the tape drive. $ZSSI, on the NonStop Kernel system, communicates with
the ACSLS library server. When $ZSSI starts, it generates EMS events logging that it
started.