5190/5194 Modular Tape Subsystem Manual

Installing the Modular Tape Subsystem
5190/5194 Modular Tape Subsystem Manual—426878-002
3-45
Starting and Testing the Tape Drives (NonStop
Himalaya K-Series Servers)
Starting and Testing the Tape Drives (NonStop
Himalaya K-Series Servers)
This subsection describes the COUP, PUP, and TMDS commands you can use to start
and test your tape devices after the modular tape subsystem is installed.
Starting a Tape Device
You can use either the COUP START command or the PUP UP command to start a
tape device after the modular tape subsystem has been installed.
The following is an example of a COUP START command:
For more on the COUP START command, see Example 4: Starting a Tape Drive on
page 2-11 or refer to the Dynamic System Configuration (DSC) Manual.
The following is an example of a PUP UP command:
>PUP UP $TAPE0
For more on the PUP UP command, see Bringing Up a Cartridge Tape Drive on
page 4-33 or refer to the Peripheral Utility Program (PUP) Reference Manual.
Testing a Tape Device
Once the modular tape subsystem has been installed, you can test a tape device that
has been started by using the TMDS TEST and EXERCISE commands.
The TMDS TEST command executes various tests on the tape device and tape
controller. The basic TEST command has the following syntax:
TEST [DRIVE] $drive [, [TESTNAME] testname]
Because there is no default test name for the 5190 and 5194 tape drives, you must
specify a value for testname. The following is an example of a TEST command that
runs the BEB-LPBK test, which performs BEB loopback tests:
TAPE> TEST DRIVE $TAPE7, TESTNAME BEB-LPBK
For a list of possible values for testname, see the TMDS Reference Manual.
The TMDS EXERCISE command verifies a tape device’s read and write capability,
checks the tape motion, and verifies the tape hardware after repairs and during
installation. The basic EXERCISE command has the following syntax:
EXERCISE [DRIVE] $drive
11) START $TAPE0
IOP for device $TAPE0 successfully started in CPU 0.
IOP for device $TAPE0 successfully started in CPU 1.
Device $TAPE0 has been successfully started.