A media robot is an enclosure that houses one or more tape drives and multiple slots for storing cartridges, and a mechanical transport for moving cartridges between locations in the enclosure. Another term for media robot is medium changer.

SCSI robotic medium changers present four different objects to host systems; the transport, slots, drives, and ports. These are collectively called “elements” by the SCSI-2 specification.

The Media Robot Utility (MRU) is a multiplatform utility for controlling robotic medium changers. MRU allows users to control operations at a very low level: injecting and ejecting cartridges, loading and unloading cartridges, and showing status and media robot attributes.

MRU software runs on computers under Microsoft Windows 2000/Windows XP, Tru64 UNIX, and OpenVMS. All of these systems are capable of communicating with media robots. On each system, MRU offers both a command line operating environment and a graphic user environment. Each interface environment offers access to the software and to online information.

The command line interface allows users with character cell terminals to access MRU. The MRU command line interface uses a common syntax across all three platforms. Case sensitivity, however, is an issue on Tru64 UNIX systems, as is the rule with all UNIX systems.

Online help is available for character cell terminal users. See the operating system specific information for instructions on how to access the online information.

The graphic user interface provides allows users with Motif, the Common Desktop Environment (CDE) or Windows 2000/Windows XP systems to access MRU. The MRU graphic user interface provides a similar look and feel across all platforms. Although there are some minor differences, they all offer similar features.

Online help is available through the Help pull down menu as well as through context sensitive help. See the operating system specific information for instructions on how to access online help.

Refer to the documentation that comes with your media robot hardware for information about connecting to the computer system. When you configure the hardware for installation, you select the SCSI coordinates (the SCSI bus, target ID, and LUN). Make a note of the SCSI coordinates as you set them on the hardware.

MRU uses special routines for communicating with the changer in a media robot. These routines use the pass-through SCSI driver built into the Windows 2000/ Windows XP system. MRU derives the name of the medium changer device (not the tape device) from its SCSI port, bus, target and LUN. This name lets you know which device you control with MRU.

For instance, a medium changer connected to SCSI port 3, bus 0, target ID 2, LUN 1 would be named by MRU software as Scsi3:B0T2L1.

If your system is already connected to media robot, you can find the SCSI coordinates through Windows 2000/Windows XP Control Panel. Write down the target ID, LUN, SCSI Port, and bus numbers and apply them to the convention described above to relate the MRU device name to the media robot.

Use the “SCSI Adapters” control panel to help identify the port, bus, target, and lun numbers. On the “Devices” tab, expand the host adapter entry to show its devices. Highlight the medium changer, and click on the “Properties” button. The pop-up window has a “Settings” tab which displays the,

This section describes the installation prerequisite tasks and information, the installation procedure, and some follow up information.

The distribution CDROM contains the Windows 2000/Windows XP Media Robot Utility software in the ISO 9660 format.

By default, the MRU installation procedure creates its own subdirectory under the system drive and places the software and help files into it.

For example, if your system drive is C, the MRU installation creates the subdirectory

C:\Program Files\MRU 

You have the option of placing the files into a different directory during installation. Follow these steps to install MRU software:

Use the following procedure to verify the MRU installation:

Before you use the MRU software, you should get to know the logging features and learn how to select a media robot for operation.

MRU software allows you to capture results of robot operations in a log file. To do so, set the MRU_LOG environment variable.

set MRU_LOG=logfile

Where logfile is the full path and file name of the file in which you want to audit activities.

Remove this environment variable if no log file is desired.

You can control the amount of information captured. By default, MRU software supplies brief information. For more information, you can enable the verbose option with the MRU_VERBOSE environment variable.

set MRU_VERBOSE=1 

Remove this environment variable to disable this feature. Refer to the media robot hardware information to interpret SCSI sense data returned when this option is enabled.

By defining a default robot, you do not have to supply a robot name parameter with MRU commands you execute. This is especially useful in the command line and batch file environment. The default robot is the implicit target for any command which does not include the ROBOT robot_name parameter.

set MRU_ROBOT=SCSIp:BbTtLl

Where:

For instance, the default robot parameter for a medium changer connected to SCSI port 3, bus 0, target ID 2, LUN 1 would be named by MRU software as Scsi3:B0T2L1

The FIND command default search behavior matches cartridge labels without case sensitivity. If you need a case sensitive search, then use the MRU_CASE_SENSITIVE environment variable.

set MRU_CASE_SENSITIVE=1

This environment variable also affects the behavior of the graphic user interface find feature.

You can use MRU to verify a successful Multi-Unit, Single LUN (MUSL) configuration. Use the SHOW ROBOT command to get information about the configuration:

robot show robot Scsi2:B0T2L2
Robot Name : Scsi2:B0T2L2 Type: SCSI 

Media  Robot   Identifier:    DEC    TL820    (C)     DEC2A5A 
Slots:          176
Drives:         6
Inports:        1
Outports:       1
Transports:     2

MUSL control is available on firmware 2A5A or higher. This information appears on the Media Robot Identifier line of the SHOW ROBOT output.

When MUSL is activated, the combined hardware units respond to a single medium changer unit. MRU shows this with a Transport count greater than 1.

The MRU command line interface runs under Tru64 UNIX Version V4.0F and above and Version 5.1, 5.1A, and 5.1B. The graphic user interface runs under Tru64 UNIX V4.0F and later and Version 5.1, 5.1A, 5.1B and requires Motif Version 1.2.3 or later.

The following table identifies the required versions of the SCSI CLC.

Go through the documentation that comes with your media robot hardware for information about connecting to the computer system. This section includes information about creating special device files for the media robot changers.

TLZ7L and TL820 libraries may have some problems with Tru64 Unix V5.0 and above.

You cannot connect a TL820 changer on the AHA1740 EISA adapter. A workaround for this case would be to connect the changer to a different SCSI adapter and leave the drive connected to the AHA1740 EISA adapter.

You cannot connect a TL82n robotic library running firmware below the 1G revision to the KFTIA adapter. If you have a TL82n robotic library running a firmware below the 1G revision, contact your service representative for information on the firmware upgrade.

MRU software qualifies locally connected medium changers and also medium changers in Tru Cluster environment with Tru64 Unix 5.1A Patch kit-0002 from all nodes in the Tru Cluster. Before you can use the Media Robot Utility software on a UNIX system, you must create special device files for the medium changers. This is not the same as creating special device files for tape drives.

There are two types of medium changers to consider:

Each of these types of robots imposes special rules for naming the robot (changer) device name. The MRU software uses the robot device name as the target for MRU commands. Some restrictions apply to the kinds of connections you can between a robot and a host system.

Determine the device name for the media changer, then use the name in the command to create the special device file. For more information, see the mc(7) manual page.

Tape loaders of the DLT and DAT variety treat their robotic devices and tape devices as logical units of the device target ID. The are four parts to the naming convention with this type of medium changer:

The following example shows how to construct a device name for a desktop TZ media changer. The media changer is on bus 2, target ID of 5, logical unit 1.

#  /sbin/scu  show  edt  bus  2
Bus:  2, Target:  5, Lun:  0, Device Type:  Sequential Access
Bus:  2, Target:  5, Lun:  1, Device Type:  Changer
Bus:  2, Target:  5, Lun:  2, Device Type:  (not present)
Bus:  2, Target:  5, Lun:  3, Device Type:  (not present)
Bus:  2, Target:  5, Lun:  4, Device Type:  (not present)

The name of the device for the media changer would be calculated by multiplying 2 by 8 and adding 5, and concatenating the letter b, providing a name of mc21b. The commands for creating the special device would be:

# cd /dev ;./MAKEDEV.MC mc21b

To determine the device name for the media changer in a TL8nn automated tape library, use the following procedure:

The following example shows how to construct a device name for a TL810 media changer with two drives. The media changer is on bus 4, target ID of 0, logical unit 0.

#  /sbin/scu  show  edt  bus  4
Bus:  4, Target:  0, Lun:  0, Device Type:  Changer
Bus:  4, Target:  1, Lun:  0, Device Type:  Sequential Access
Bus:  4, Target:  2, Lun:  0, Device Type:  Sequential Access
Bus:  4, Target:  3, Lun:  0, Device Type:  Sequential Access

The name of the device for the media changer would be calculated by multiplying 4 by 8 and adding 0, providing a name of mc32. The commands for creating the special device would be:

# cd /dev ; ./MAKEDEV.MC mc32 

When installing a TL8nn medium changer system, you need to keep track of the device file names for the drives serviced by the particular robotic transport device. MRU software cannot unload a cartridge from a drive in a TL8nn medium changer system without first taking the drive offline. MRU software has no way of associating the drives with the robotic transport device. You must supply the device file name before unloading a cartridge.

MRU software now runs on Tru64 UNIX V5.1 & above. It qualifies locally connected medium changers and also medium changers in Tru Cluster environment with Tru64 Unix 5.1A Patch kit-0002 from all nodes in the Tru Cluster. Before you can use the Media Robot Utility software on a Tru64 UNIX V5.1 system, you must ensure that the Media Changer Drivers are installed and configured.

The following steps will help you check for installation and configuration.

For more information you can access manual pages using:

# man hwmgr (8)
# man dsfmgr (8)

You can run the CLI robot command after specifying robot name as:

/dev/changer/mcnn

xrobot Command

#xrobot /dev/changer/mcnn 

Where mcnn is the number assigned to the device. Users can specify more than one changer device on the command line as follows:

#xrobot /dev/changer/mcn1 /dev/changer/mcn2 /dev/changer/mcn3

Or you can create a hard link between /dev/changer/mcnn and /dev/mcnn for xrobot to find media changer devices by itself, then you need not to give changer device name with xrobot command.

Referencing Changer Devices in the API

Application programs should reference changer devices by the naming convention described above. These devices can be viewed by the hwmgr command.

The distribution CDROM contains the Tru64 UNIX Media Robot Utility software in the ISO 9660 format.

# setenv LANG en_US.ISO8859-1 

Before you use the MRU software, you need to know the required privilege level to execute the software. You should also understand the logging features, and understand the implicit and explicit selection of a media robot for any operation.

 # setenv MRU_LOG logfile

# MRU_LOG=logfile ; export MRU_LOG

# setenv MRU_VERBOSE

# MRU_VERBOSE= ; export MRU_VERBOSE

# setenv MRU_ROBOT /dev/changer/mc32 

# MRU_ROBOT=/dev/changer/mc32 ; export MRU_ROBOT 

# setenv MRU_CASE_SENSITIVE 

# MRU_CASE_SENSITIVE= ; export MRU_CASE_SENSITIVE 

# setenv MRU_OLD_STATUS 

# MRU_OLD_STATUS= ; export MRU_OLD_STATUS 

# man robot 

# xrobot 

# xrobot /dev/changer/mc32 /dev/changer/mc48 /dev/changer/mc19b 

robot  show  robot  /dev/changer/mc48
Robot  Name  : mc48  Type:  SCSI
Media  Robot  Identifier:  DEC     TL820    (C)    DEC2A5A

Slots:             176
Drives:            6
Inports:           1
Outports:          1
Transports:        2

The MRU command line interface runs on OpenVMS VAX Version 7.3, OpenVMS Alpha Versions 7.3-2 and 8.2 and OpenVMS I64 Versions 8.2 and 8.2-1.

The graphic user interface(GUI) runs on OpenVMS VAX Version 7.3, OpenVMS Alpha Versions 7.3-2 and 8.2, and I64 Versions 8.2 and 8.2-1. On OpenVMS VAX Version 7.3, OpenVMS Alpha Versions 7.3-2 and 8.2, and I64 Versions 8.2 and 8.2- 1, the GUI requires Motif Version 1.2.5.

Refer to the documentation that comes with your media robot hardware for information about connecting to the computer system.

A SCSI device that is directly connected to a VAX or Alpha system uses the GKDRIVER software to control the movement of the robotics. (The tape devices use tape device drivers.) The GKDRIVER is a standard OpenVMS device driver and does not require a separate installation. However, you must first create a tape robot unit to use the robotic features on tape jukeboxes directly connected through a SCSI bus. The tape robot unit is named such that it describes the physical SCSI connection.

There are two categories of medium changers to consider, and each uses a different naming convention for its drive and changer devices because of the manner in which it is configured and physically connected to the SCSI bus. Keep these conventions in mind as you configure your systems, especially for creating tape robotic units.

DLT, DAT, and TSL10000 tape loaders treat their robotic devices and tape devices as logical units of the device target ID. The are four parts to the naming convention with this type of robotic loader:

MKA400 is the name of a tape device connected to the first SCSI bus seen at boot time, at target ID 4. GKA401 is the name of the robotic device and the name of the robotic unit corresponding to the tape device MKA400.

With TL8nn, ESL9nnn, SSL2nnn, MSL5nnn tape libraries, the drives and robot units are separate. There are three parts to the naming convention for a tape library:

For example, for a TL810 library system with the robotic unit connected to the second bus detected at boot time at target ID 5, the name would be GKB500.

When installing a TL8nn, ESL9nnn, SSL2nnn, MSL5nnn medium changer system, you need to keep track of the device names for the drives serviced by the particular robotic transport device. MRU software cannot unload a cartridge from a drive in a TL8nn medium changer system without the OpenVMS system first dismounting the cartridge. MRU software has no way of associating the drives with the robotic transport device. You must correlate the device and device name before unloading a cartridge.

For SCSI magazine loaders connected directly to a SCSI bus, enter the SYSGEN or SYSMAN command in the appropriate format:

VAX system:

$ MCR SYSGEN CONNECT GKannn:/DRIVER=GKDRIVER/NOADAPTER

Alpha/I64 system:

$ MCR SYSMAN IO CONNECT GKannn:/DRIVER=SYS$GKDRIVER -
$_ /NOADAPTER

Where: GKannn: is the robot device name. With media loaders, the robot device name is always the same as the tape drive name incremented by one, and without any prefixes (allocation class or NODE$ prefix) to the GK string. For example, a tape drive name of $1$MKA200: could use a robot device name of GKA201:.

VSI recommends that you include the SYSGEN commands in your system startup command procedure.

When connecting a media robot to an HSJnn or HSDnn controller, you must associate the loader name with an internal passthrough name. After installing the media robot hardware, and connecting the cables between host, controller, and media robot, you can make the association at the controller console terminal.

This example shows the commands for connecting a TL810 Automated Tape Library systme loader. The SCSI port is 5, Target ID is 4, and LUN is 0.

CLI> ADD LOADER TL810A 5 4 0
CLI> ADD PASSTHROUGH P810A TL810A
CLI> ADD UNIT D810 P810A

Media Changer devices on Fibre Channel (FC) will be auto configured. As the device name of a Media Changer on Fibre Channel does not imply to its physical address, so FC connected Media Changers cannot be configured manually (i.e. the CONNECT command is not used). For FC connected device the naming scheme is mentioned below:

The Fibre Channel tapes and changers will be named by a scheme similar to the one implemented on Fibre Channel disks. A Fibre Channel tape name will be of the form $2$MGAn, where n is a number chosen by OpenVMS. The letter chosen for the controller will always be 'A', with the prefix $2$. In general the name creation algorithm chooses the first free unit number starting with 0, so the first tape discovered on the Fibre Channel will be named $2$MGA0. The next will be $2$MGA1 and so on. Likewise, the first medium changer detected on the Fibre Channel will be named $2$GGA0, and so on.

$ mcr sysman io find_wwid 

[Device $2$GGA0]

WWID=04100024:"DEC      TL800       (C)      DEC3G9CCR82A017"

[Device $2$MGA0]

WWID=04100022:"DEC      TZ89        (C)      DECCX939S2777"

[Device $2$MGA1]

WWID=04100022:"DEC      TZ89        (C)      DECCX942S6295"

$ mcr sysman io auto/log

%SYSMAN-I-OUTPUT, command execution on node BOLERO

%IOGEN-I-PREFIX, searching for ICBM with prefix SYS$

%IOGEN-I-PREFIX, searching for ICBM with prefix DECW$

%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKA0

%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKB0

%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port PGA0

%IOGEN-I-CONFIGURED, configured device GGA0

%IOGEN-I-CONFIGURED, configured device MGA0

%IOGEN-I-CONFIGURED, configured device MGA1

$

This section describes the installation prerequisite tasks and information, the installation procedure, and some follow up information.

The distribution CDROM contains the OpenVMS Media Robot Utility software in the Files11 format.

Use the following procedure for preinstallation:

Use the following procedure to install the software:

The IVP searches the system for connected libraries and loaders and any it finds are presented to you for selection. If the IVP finds none, the installation finishes, but the IVP fails. In this case, you must install the hardware and/or appropriate drivers and execute the IVP. Use this command line to execute the IVP:

$ @SYS$COMMON:[SYSTEST]ROBOT$IVP.COM 

If you installed MRU on a VMScluster system, users will have to log out and log in again to use MRU. This is due to the automatic update of the DCLTABLES performed during MRU software installation.

Before you use the MRU software, you need to know the required privileges to execute the software. You should also understand the logging features, and understand how to select a media robot for operation.

Privileges required to operate MRU software depend on the robot connection to the host. The table below lists the privileges required for each of three different kinds of connections.

MRU software allows you to capture results of robot operations in a log file. To do so, define the MRU_LOG logical in the process running MRU software.

This command creates a log file named file_name in the current default directory:

$ DEFINE MRU_LOG file_name

Deassign this logical if no log file is desired.

You can control the amount of information captured. By default, MRU software supplies brief information. For more information, you can enable the verbose option with the MRU_VERBOSE logical.

This command enables verbose logging:

$ DEFINE MRU_VERBOSE 1 

Deassign this logical to disable this feature. Refer to the media robot hardware information to interpret SCSI sense data returned when this option is enabled.

By defining a default robot, you do not have to supply a robot name parameter with MRU commands you execute. The default robot is the implicit target for any command that does not include the robot_name parameter.

This command sets the default robot to robot_name:

$ DEFINE MRU_ROBOT robot_name

You can override the default robot by explicitly including the ROBOT robot_name parameter in an MRU command. Deassign this logical if no default robot is needed.

The FIND command default search behavior matches cartridge labels without case sensitivity. If you need a case sensitive search, then use the MRU_CASE_SENSITIVE logical.

$ DEFINE MRU_CASE_SENSITIVE 1 

This environment LOGICAL also affects the behavior of the graphic user interface find feature.

Starting with this version, MRU returns operating system specific status messages to programs written against the application programming interface.

If you want to continue using scripts and programs written against previous versions of MRU, then use the MRU_OLD_STATUS logical.

$ DEFINE MRU_OLD_STATUS 1 

With this logical defined, exit status reports either success or failure.

The MRU_READY_DELAY logical defines the amount of time you will take to place a cartridge into a TL820 class ATL inport and close the inport door, after you issue the READY command. If you fail to close the inport door within the specified time, MRU may report an error on subsequent commands.

The default value is 65 seconds.

This logical definition sets the time to two minutes.

$DEFINE MRU_READY_DELAY 120

If you issue a command to a media robot while it is performing an ongoing operation, the MRU software waits until the ongoing operation completes before attempting the execute the command. By default, the MRU software waits up to approximately 18 hours for the operation to finish before failing the command. If you, or a scripted procedure, cannot tolerate a long delay, you can specify number of seconds delay you can tolerate with the MRU_WAIT logical.

This command sets the longest wait period to two minutes:

$ DEFINE MRU_WAIT 120

Another feature of MRU software controls the amount of time it waits after an unload operation is initiated on a DLT media robot. It can take up to about three minutes for a tape to rewind in response to an unload request. By default, MRU software will attempt to perform an unload up to 180 times, until the unload is successful. You can change this by specifying an unload retry value with the MRU_UNLOAD_DELAY logical. The amount of time taken to retry a single unload operation can take from one to approximately seven seconds depending on the particular media robot.

This command sets the number of unload retries to 10:

$ DEFINE MRU_UNLOAD_DELAY 10

MRU software includes two interfaces. The MRU command line interface allows for direct interaction with the MRU software, and for the development of scripts for programmed operations. A help file contains information about MRU software for OpenVMS systems. You can access the information in the help file with this command:

$ HELP ROBOT

The MRU system now includes a GUI which runs on the following: OpenVMS I64 Versions 8.2 and 8.2-1, OpenVMS Alpha Versions 7.3-2 and 8.2, OpenVMS VAX Version 7.3, and Motif Version 1.2.5. This interface provides a simple way to operate a library or loader. By default, the graphic user interface scans the system to provide access to all connected robots. To start the graphic user interface, enter:

$ XROBOT 

To use the graphic user interface to access particular robots, specify the robot devices in a list following the XROBOT command. The following command example shows this feature:

$ XROBOT $1$DUA812: GKA2: $1$MIA4:

The system view window shows all libraries and loaders connected to the system. Select the library or loader you want from the system view window by placing the pointer on the robot icon and double clicking MB1.

The robot dialog represents the selected library or loader. Use it to conduct operations with the robot, and set robot- specific customizations.

Move cartridges by either drag and drop operation with MB1, or use point and click operations on cartridge source and destination locations. Cartridges can be moved from any location to any other location as allowed by the media robot hardware (except for the explicit dismount/offline operation required by drives in the TL8nn automated tape libraries).

The online help provides detailed information on using the graphic user interface and, operating your media robot.

You can use MRU to verify a successful Multi-Unit, Single LUN (MUSL) configuration. Use the SHOW ROBOT command to get information about the configuration:

$ROBOT   SHOW   ROBOT   $1$DUA560:
Robot Name  :  $1$DUA560:  Type:  SCSI

Media   Robot   Identifier: DEC   TL820   (C)   DEC2A5A

Slots:                176
Drives:               6
Inports:              1
Outports:             1
Transports:           2

MUSL control is available on firmware 2A5A or higher. This information appears on the Media Robot Identifier line of the SHOW ROBOT output.

When MUSL is activated, the combined hardware units respond to a single medium changer unit. MRU shows this with a Transport count greater than 1.

MRU software uses these common parameters in its commands:

MRU drive, slot, and port numbering begins with 0. The default value supplied by MRU for DRIVE, SLOT, and PORT is 0.

The following command descriptions show the general command syntax.

For commands that involve cartridges, such as LOAD and MOVE, you can optionally specify the cartridge name as it appears on the barcode. If the media robot has a vision capability, MRU can determine the bar code value before actually executing the command. If the specified bar code is not the bar code value at the source, the comand fails before processing any farther. If the media robot does not qualify bar codes, the bar code value is ignored.

Consult your online information for examples and detailed descriptions of commands for your operating system.

INJECT

The INJECT command moves a cartridge from a port to a slot.

INJECT [ PORT port_number ] { SLOT slot_number }
 [ ROBOT robot_name ][ CART cartridge-name ]

EJECT

This EJECT command moves a cartridge from a slot to a port.

EJECT SLOT { SLOT slot_number } [ PORT port_number ]
{ ROBOT robot_name } [ CART cartridge_name ]

This EJECT command moves a cartridge from the PTM of a TL82n Automated Tape Library System to a port.

EJECT [ ROBOT robot_name ] { PORT } [ port_number ]
[ CART cartridge_name ] 

LOAD

The LOAD command moves a cartridge from a slot into a drive.

LOAD { SLOT slot_number } [ DRIVE drive_number ] [ ROBOT robot_name ] 
[ CART cartridge_name ] 

UNLOAD

The UNLOAD command moves the cartridge from a drive into a slot.

UNLOAD [ DRIVE drive_number ] { SLOT slot_number } 
[ ROBOT robot_name ] [ CART cartridge_name ] 

READY

The READY command enables the inport door release button on the TL82n Automated Tape Library System.

READY { PORT port_name } [ ROBOT robot_name ] 

LOCK

The LOCK command sends a SCSI Prevent Media Removal command to the media robot. Refer to your hardware documentation for a description of the result of issuing this SCSI command.

LOCK [ ROBOT robot_name]

UNLOCK

The UNLOCK command sends a SCSI Allow Media Removal command to the media robot. Refer to your hardware documentation for a description of the result of issuing this SCSI command.

UNLOCK [ ROBOT robot_name ] 

MOVE

The MOVE command moves a cartridge from a source location to a destination. Allowable actions with the MOVE command are determined by the specific library or loader system.

MOVE {PORT port_number | SLOT slot_number | DRIVE DRIVE_NUMBER } 
{ PORT port_number | SLOT slot_number | DRIVE drive_number }
[ ROBOT robot_name ] [ CART cartridge_name ] 

POSITION

The POSITION command positions the cartridge manipulation mechanism to the specified location.

POSITION { Port port_number | SLOT slot_number | drive drive_number } 
[ ROBOT robot_name ] 

HOME

The HOME command returns a cartridge from the specified location to its home (previous) location.

The home position varies between different media robots. To find out the home location on your media robot, consult your hardware documentation, or issue the command and observe the placement of the mechanism.

HOME [ ROBOT robot_name ] { PORT port_number | SLOT slot_number |
DRIVE drive_number | TRANSPORT transport_number } 

FIND CARTRIDGE

The FIND CARTRIDGE command locates a named cartridge in any media robot which includes a vision system. If the named cartridge resides in the media robot, MRU software returns its location.

This command uses the name on the external label affixed to the cartridge, it DOES NOT use the name of the recorded label on the medium.

FIND CARTRIDGE { cartridge_name } [ ROBOT robot_name ] 

MRU V1.4 or higher allows wildcard names for this command as in the following examples:

FIND CARTRIDGE {"?*"} 

this command shows all elements namely:

that are full.

FIND CARTRIDGE {"*"}

this command shows all slots, drives, transports and ports.

Irrespective of whether they are full or empty this command shows all the elements available in the library.

INITIALIZE

The INITIALIZE command inventories the robot and updates the robot’s internal element status. The time it takes to complete the operation depends on the size of the robot. A small loader takes less time to inventory than does a multitower robot.

INITIALIZE [ ROBOT robot_name ]

The following command descriptions show the general command syntax. Consult your online information for examples and detailed descriptions of commands for your operating system.

SHOW ROBOT

The SHOW ROBOT command shows the status of the specified robot.

SHOW ROBOT [ ROBOT robot_name ]

SHOW PORT

The SHOW PORT command shows the status of the specified ports. For a description of the results, review the online information.

SHOW PORT [ ROBOT robot_name ] { PORT } 

SHOW SLOT

The SHOW SLOT command shows the status of the specified slots. For a description of the results, review the online information.

SHOW SLOT [ ROBOT robot_name ] { SLOT }
[[ slot_number | slot_number-slot_number ],... ]

SHOW DRIVE

The SHOW DRIVE command shows the status of the specified drives. For a description of the results, review the online information.

SHOW DRIVE [ ROBOT robot_name ] { DRIVE }
[[ drive_number | drive_number-drive_number ],... ]

SHOW VERSION

The SHOW VERSION command displays the current version of the Media Robot Utility software

SHOW VERSION

HELP

The HELP command displays information about MRU commands.

HELP