← All Documents
VMS Software / Documentation / VSI Media Robot Utility Installation and User Guide

VSI Media Robot Utility Installation and User Guide

Publication Date:

Operating Systems:
VSI OpenVMS IA-64 Version 8.4-1H1 or higher
VSI OpenVMS Alpha Version 8.4-2L1 or higher
VSI OpenVMS x86-64 Version 9.2-3 or higher
Software Version:
VSI Media Robot Utility V1.9 or higher

1. Preface

1.1. About VSI

VMS Software, Inc. (VSI) is an independent software company licensed by Hewlett Packard Enterprise to develop and support the OpenVMS operating system.

1.2. Document Structure

This manual is organized as follows:

1.3. VSI Encourages Your Comments

You may send comments or suggestions regarding this manual or any VSI document by sending electronic mail to the following Internet address: . Users who have VSI OpenVMS support contracts through VSI can contact for help with this product.

1.4. OpenVMS Documentation

The full VSI OpenVMS documentation set can be found on the VMS Software Documentation webpage at https://docs.vmssoftware.com.

2. Media Robots and MRU Software

This section defines the key terminology and describes the purpose of the Media Robot Utility (MRU) software.

2.1. What Is a Media Robot?

A media robot, also commonly referred to as medium changer or automated tape library, is an enclosure that houses one or more tape drives, multiple cartridge storage slots, and a mechanical transport mechanism for moving cartridges between locations within the enclosure.

2.2. Mechanical Attributes of a Media Robot

According to the SCSI standard, media robots present four different objects (elements) to host systems: the transport, slots, drives, and ports.

Transport

This is the robot used to move tapes (media). The SCSI term for the transport is Medium Transport Element. Most media robot subsystems only have one robot, although there can be more.

Slot

This is the place where a medium is stored. For the robot subsystems qualified by the Media Robot Utility, the number of slots ranges from 4 to 1320. The SCSI term for a slot is Storage Element.

Drive

This is the tape. The robot has very little control over its drives and is often at a different SCSI address. Robot subsystems have at least one drive, whereas MSL libraries, for example, have multiple drives. The SCSI term for a drive is Data Transfer Element.

Ports

Some media robots have slots for storing many cartridges. Such robots also have ports which are used to place cartridges into the robot or remove them from the robot. Media loaders have no ports. Media libraries can have one or more ports. The SCSI terms for port are Import Export Element, Import Element, and Export Element, depending on the function of the port.

2.3. What Is Media Robot Utility Software?

Media Robot Utility (MRU) is a utility for controlling robotic medium changers. MRU allows users to perform remote hardware management operations: loading and unloading cartridges, and showing status and media robot attributes.

Note

Some commands may not be supported on all customer hardware platforms, depending on the available hardware features. References to legacy hardware have been retained where necessary, as these platforms remain deployed in certain environments and continue to be relevant for interpreting hardware-specific functionality and system behavior.

2.4. MRU Interfaces

The MRU software includes two interfaces. The command line interface allows for direct interaction with the MRU software and for the development of scripts for programmed operations. For information about the currently supported MRU commands, see Section 4, ''Media Robot Utility Command Reference''.

The graphical user interface (GUI) provides a simple way to operate a library or loader. By default, the GUI scans the system to provide access to all connected robots. To start the GUI, enter: 

$ XROBOT

To use the GUI to access particular robots, specify those robot devices in a list following the XROBOT command, as shown below:

$ XROBOT $2$GGA0:

The default system view window shows all libraries and loaders connected to the system. Double-click a library or loader to view it in the robot dialog window. Use it to perform operations with the robot and set robot-specific customizations, such as moving cartridges.

Online help is available through the Help pull down menu as well as through context-sensitive help.

3. Media Robot Utility Software for OpenVMS

This chapter describes the Media Robot Utility software variant for the OpenVMS system. It explains some important aspects of hardware installation, establishing the operating system connection, as well as installing the MRU software and the MRU operating environment.

3.1. Connecting the Media Robot Hardware

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

Warning

If the media robot has a hardware setting to enable or disable automatic inventory on startup, make sure that this option is enabled. If the automatic inventory on startup option is disabled, MRU may not work.

3.2. Direct Connect SCSI Devices (Alpha and IA-64 only)

An SCSI device that is directly connected to an OpenVMS system uses the SYS$SYSTEM:SYS$GKDRIVER.EXE driver to control the movement of the robotic mechanism. 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 robots 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 when creating tape robotic units.

3.3. Connecting Automated Tape Libraries (Alpha and IA-64 only)

Important

The information in this section applies to the classes of libraries listed at https://vmssoftware.com/products/supported-platforms/.

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

  • The name begins with the MK prefix for tape devices and the GK prefix for robotic devices.

  • The prefix is followed by a letter indicating the physical host system SCSI bus to which the device is connected. For devices connected to the first bus detected at boot time, the letter is A, for the second bus detected, the letter is B, etc.

  • The next part is a number corresponding to the SCSI target ID.

For fibre channel tape drives, the device name will always begin with $2$MGA. See the SYSMAN IO FIND_WWID command description in the VSI OpenVMS System Management Utilities Reference Manual, Volume II: M–Z for further information.

When installing a 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 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.

3.4. Creating a Tape Robot Unit (Alpha and IA-64 only)

For SCSI magazine loaders connected directly to an SCSI or SAS bus, enter the following command:

$ 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 to the GK string (allocation class or node-name$ prefix). For example, the tape drive name $1$MKA200: could use the robot device name GKA201:.

VSI recommends that you include any such commands in your system startup command procedure.

3.5. Configuring Media Robot on Fibre Channel

Media robot devices on Fibre Channel (FC) cannot be configured manually (i.e. the CONNECT command cannot be used), which means they will be configured automatically.

The naming scheme for Fibre Channel tapes and changers is 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 one will be named $2$MGA1:, etc. Likewise, the first medium changer detected on the Fibre Channel will be named $2$GGA0:, etc.

Important

Two non-clustered systems that share a common library through a FC switch have no knowledge of each other and may consequently assign two different names to the same tape drive. Note that there is no resource locking between non-clustered systems, which may result in conflicting allocation of the tape drives or robot, as well as potential damage to data and/or hardware/media. Within a cluster, the naming and allocation is controlled and consistent.

Example Device Configuration

  1. List all detected tapes and media robots along with their suggested names and worldwide identifiers (WWID) by using the following command:

    $ MCR SYSMAN IO FIND_WWID

    The output will be written to the file SYS$SYSTEM:SYS$DEVICES.DAT and will look similar to the following:

    %SYSMAN-I-OUTPUT, command execution on node MM2052
On port _FGB0:, the following tape WWIDs and their proposed device
names have been found but not yet configured:

[Device $2$MGA0]
WWID=02000008:5001-4380-271A-7704

[Device $2$MGA1]
WWID=02000008:5001-4380-271A-7701

[Device $2$GGA0]
WWID=02000008:5001-4380-271A-7700

Run SYSMAN IO AUTO to configure the above device(s).
  2. Optional: If you would like to change any of the suggested device names, perform the following steps:

    1. Edit the device names in the SYS$SYSTEM:SYS$DEVICES.DAT file.

    2. Execute DEASSIGN /TABLE=LNM$DEV_WWID_TABLE /EXECUTIVE /ALL to remove the previous device name association with logical names.

    If you are renaming a device in a cluster environment, refer to the Guidelines for OpenVMS Cluster Configurations manual.

  3. Use the following command to auto-configure the devices:

    $ MCR SYSMAN IO AUTOCONFIGURE/FULL/LOG

    The output should look similar to the following:

    %SYSMAN-I-OUTPUT, command execution on node MM2052
%IOGEN-I-PREFIX, searching for ICBM with prefix SYS$
%IOGEN-I-ACTIVATE, activating ICBM SYS$ICBM
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKA0
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKB0
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKC0
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKD0
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port FGA0
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port FGB0
%IOGEN-I-CONFIGURED, configured device MGA0
%IOGEN-I-CONFIGURED, configured device MGA1
%IOGEN-I-CONFIGURED, configured device GGA0

    Note

    If you rename a device after the MCR SYSMAN IO AUTOCONFIGURE command has been executed, you will need to reboot your system for the changes to take effect.

3.6. MRU Software Installation

This section describes the MRU installation procedure.

3.6.1. MRU Distribution Medium

MRU is currently available on the VSI Service Platform in the form of a PCSI kit, as well as on the OE LP CD1 for Alpha and on the OE DVD for IA-64.

3.6.2. Installing MRU

Perform the following procedure to install the software:

  1. Log in to the SYSTEM account.

  2. Verify that the current system disk backup copy is appropriate.

  3. Mount the media that contains the software kit.

  4. Invoke the VMSINSTAL procedure using the following command:

    $ @SYS$UPDATE:VMSINSTAL.COM MRU019 kit-location

    where kit-location is the name of the directory from which you are installing the kit.

  5. Confirm the state of the system disk.

  6. Select no additional options.

  7. Purge any previous MRU files.

  8. If you are upgrading MRU, you are likely to get a message from the VMSINSTAL procedure about version sequencing at this point. If you receive this message, select the option to replace the image that is currently installed.

  9. Run the Installation Verification Procedure (IVP).

3.6.3. Verifying the Installation

IVP searches the system for connected libraries and loaders. If IVP finds none, the installation finishes, but IVP fails. In this case, you must install the hardware and/or appropriate drivers and execute IVP again. To execute IVP, use the following command:

$ @SYS$TEST:ROBOT$IVP.COM

Refer to Appendix A, "Sample Installation Logs" for what the output should look like.

3.6.4. Updating the OpenVMS DCL Tables

If you installed MRU in a cluster environment, users will have to log out and log back in to be able to use MRU after the installation script finishes. This is due to the automatic update of the DCLTABLES performed during MRU software installation.

3.7. The OpenVMS Operating Environment

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.

Caution

Define logical names only within the context of a user process if you use any Storage Management Software product that includes the Media and Device Management Services (MDMS) software. If you use MDMS software and define any of these logical names so that they are set for any MDMS process (i.e. any group or system logical table accessible by MDMS), you could cause failures in MDMS operations. For more information, refer to the VSI ABS/MDMS User Guide.

3.7.1. Required Process Privileges

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

Table 1. Required Process Privileges

Privilege

Direct Connect SCSI (Alpha and IA-64 only)

FC Controller Connect

DSSI Connection (Alpha Only)

SYSPRV

Not required

Required

Not required

PHY_IO

Required

Required

Required

DIAG

Required

Required

Not required

READALL

Not required

Not required

Required

3.7.2. MRU Logical Names

MRU_LOG

MRU_LOG — Creates a log file of MRU operations named file-name in the current default directory. Deassign this logical if no log file is desired.

Format

DEFINE MRU_LOG file-name

MRU_VERBOSE

MRU_VERBOSE — Provides more detailed information in response to some MRU commands. When enabled, this option captures reports SCSI Sense Data. You must refer to the media robot hardware documentation to interpret this data. Deassign this logical to disable this feature.

Format

DEFINE MRU_VERBOSE 1

MRU_OLD_STATUS

MRU_OLD_STATUS — This causes MRU, Version 1.4-1 to exit using the Version 1.4 exit status behavior; success or failure.

Format

DEFINE MRU_OLD_STATUS 1

MRU_ROBOT

MRU_ROBOT — Defines a default robot against which all commands are executed, unless a different robot is specified as a parameter to a command. Deassign this logical if no default robot is needed.

Format

DEFINE MRU_ROBOT robot-name

MRU_WAIT

MRU_WAIT — Defines the number of seconds delay you can tolerate waiting for a current robot operation to finish before taking action on a command you enter. Deassign this logical if an indefinite wait is acceptable.

Format

DEFINE MRU_WAIT number-of-seconds

MRU_UNLOAD_DELAY

MRU_UNLOAD_DELAY — Defines the number of times that an unload operation is tried. The default value is 180 attempts. Define this logical if you want to change the number of unload attempts.

Format

DEFINE MRU_UNLOAD_DELAY number-of-seconds

MRU_READY_DELAY

MRU_READY_DELAY — Defines the amount of time you will take to place a cartridge into a TL820 class ATL in-port and close the in-port door, after you issue the READY command. If you fail to close the in-port door within the specified time, MRU may report an error on the following command. The default value is 65 seconds.

Format

DEFINE MRU_READY_DELAY n

MRU_CASE_SENSITIVE

MRU_CASE_SENSITIVE — When defined to any value, this causes the volume tag comparisons used with the CARTRIDGE keyword to be made in a case-sensitive manner.

Format

DEFINE MRU_CASE_SENSITIVE 1

MRU_OLD_STATUS

MRU_OLD_STATUS — When defined to any value, this causes the ROBOT command to revert to the exit status behavior present in MRU V1.2, i.e. a single success status and a single failure status.

Format

DEFINE MRU_OLD_STATUS 1

3.7.3. Logging Robot Operations

The MRU software allows you to save the results of robot operations into a log file. To do so, define the MRU_LOG logical name like so:

$ DEFINE MRU_LOG file-name

This command will create a log file in the current default directory. If you do not want to create a log file, deassign this logical name.

You can control the amount of information that will be logged. By default, the information that MRU supplies is rather brief. For a more detailed log, set the MRU_VERBOSE logical name to 1 like so:

$ 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.

3.7.4. Default Robot

By defining a default robot, you do not have to supply the 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. To set a default robot, enter the following command:

$ DEFINE MRU_ROBOT robot-name

3.7.5. Case-Sensitive Searches

The FIND command default search behavior matches cartridge labels without case sensitivity. If you need a case-sensitive search, set the MRU_CASE_SENSITIVE logical name to 1, like so:

$ DEFINE MRU_CASE_SENSITIVE 1

Note

MRU_CASE_SENSITIVE also affects the behavior of the graphic user interface Find feature.

3.7.6. Exit Status

MRU returns 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, set the MRU_OLD_STATUS logical name to 1 like so: 

$ DEFINE MRU_OLD_STATUS 1

With this logical name defined, the exit status will report either success or failure.

3.7.7. Waiting for the Robot

If you issue a command to a media robot while it is performing an operation, the MRU software will wait until the ongoing operation completes before attempting to execute the new command. By default, the MRU software waits up to approximately 18 hours for the operation to finish before failing the command. You can set this wait time (in seconds) by defining the MRU_WAIT logical name like so:

$ DEFINE MRU_WAIT value

The MRU utility also manages the delay period following an unload operation on legacy hardware. Because a tape can take up to three minutes to rewind after receiving an unload request, the MRU software is configured by default to retry the unload operation up to 180 times, or until it completes successfully. You can change this by specifying a value representing the number of retries with the MRU_UNLOAD_DELAY logical name like so:

$ DEFINE MRU_UNLOAD_DELAY value

The time required for a single unload retry can range from one to several seconds, depending on the media robot.

4. Media Robot Utility Command Reference

All MRU commands listed in this section are subcommands of the DCL command ROBOT on OpenVMS.

4.1. Command Parameters

MRU software uses these common commands parameters:

slot-number

An integer value indicating a physical slot in the media robot.

drv-number

An integer value indicating a physical drive in the media robot.

port-number

An integer value indicating a physical port in the media robot.

robot-name

The system name of the media robot being accessed. If none is specified, MRU will use the default robot name (to specify the default robot, refer to Section 3.7.4, ''Default Robot''). To override the default robot name, include the robot-name parameter in the command.

cartridge-name

The name of the cartridge as identified by its external label. Note that MRU treats cartridge names with case sensitivity.

Important

MRU slot, drive, and port numbering begins with 0, which means that the default value for slot-number, drv-number, and port-number is 0.

4.2. Commands for Operating a Media Robot

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. MRU verifies the barcode value before executing the command. If the specified barcode does not match the barcode at the source location, the command fails before any action is taken. If the media robot does not support barcode verification, the specified barcode value is ignored.

INJECT

INJECT — Moves a cartridge from a port to a slot.

Format

INJECT [PORT port-number] SLOT slot-number [ROBOT robot-name]

Parameters

port-number

An integer value indicating the robot port.

slot-number

An integer value indicating the robot slot.

robot-name

The name for the media robot.

Example

The following MRU example injects a cartridge from the in-port of media robot $1$DUA0 to slot 19:

$ ROBOT INJECT PORT 0 SLOT 19 ROBOT $1$DUA0:

EJECT

EJECT — Moves a cartridge from a slot or PTM to a port. The EJECT command also moves a cartridge from the PTM of a TL82n Automated Tape Library system. The EJECT command used this way does not include a slot specification.

Format

Format (slot to port)

EJECT SLOT slot-number [PORT port-number] [ROBOT robot-name]

Format (PTM to port)

EJECT [ROBOT robot-name] PORT port-number

Parameters

slot-number

An integer value indicating the robot slot.

port-number

An integer value indicating the robot port.

robot-name

The name for the media robot.

Example

  1. The following MRU example ejects a cartridge from slot 20 of a TL820 Automated Tape Library to the outport: 

    $ ROBOT EJECT SLOT 20 PORT 1 ROBOT $1$DUA0:

  2. The following example ejects a cartridge from the PTM of a TL820 Automated Tape Library to the outport: 

    $ ROBOT EJECT PORT 1 ROBOT $1$DUA0:

LOAD

LOAD — Moves a cartridge from a slot into a drive.

Format

LOAD SLOT slot-num [DRIVE drv-num] [ROBOT robot-name]

Parameters

slot-num

An integer value indicating the robot slot.

drv-num

An integer value indicating the physical drive in the robot.

robot-name

The name for the media robot.

Example

The following MRU example loads a cartridge from slot 1 to drive 0 in the robot device $2$GGA0:

$ ROROT LOAD SLOT 1 DRIVE 0 $2$GGA0:

UNLOAD

UNLOAD — Moves a cartridge from a drive into a slot.

Additional Information

To unload a cartridge from a drive in an MSL G3 Series Tape Library, you must first dismount the media before issuing the DISMOUNT command with the /UNLOAD qualifier.

Format

UNLOAD [DRIVE drv-number] SLOT slot-number [ROBOT robot-name]

Parameters

drv-number

An integer value indicating the physical drive in the robot.

slot-number

An integer value indicating the robot slot.

robot-name

The name for the media robot.

Examples

  1. The following example shows how to unload a cartridge from a drive in an MSL G3 Series library.

    $ DISMOUNT/UNLOAD $2$MGA1:
$ ROBOT UNLOAD DRIVE 1 SLOT 10 ROBOT $2$GGA0:

READY

READY — The READY command enables the inport door release button on the TL82n Automated Tape Library system. The READY command also allows you to place a cartridge into the inport prior to issuing the INJECT command.

Format

READY [port-number] [ROBOT robot-name]

Parameters

port-number

An integer value indicating the robot port.

robot-name

The name for the media robot.

Example

The following MRU example enables the inport of a TL820 Automated Tape Library: 

$ ROBOT READY PORT 0 ROBOT $1$DUA0:

LOCK

LOCK — Sends a SCSI Prevent Media Removal command to the media robot. Consult your hardware documentation for a description of the results of this command for your particular media robot.

Format

LOCK [ROBOT robot-name]

Parameter

robot-name

The name for the media robot.

Example

The following MRU example locks the door on a TLZ07 tape loader: 

$ ROBOT LOCK ROBOT GKA401:

UNLOCK

UNLOCK — Sends a SCSI Allow Media Removal command to the media robot. Consult your hardware documentation for a description of the results of this command for your particular media robot.

Format

UNLOCK [ROBOT robot-name]

Parameter

robot-name

The name for the media robot.

Example

The following MRU example unlocks the door on a TLZ07 tape loader: 

$ ROBOT UNLOCK ROBOT GKA401:

MOVE

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

Format

MOVE {SLOT slot-number | DRIVE drv-number | PORT port-number} {SLOT slot-number | DRIVE drv-number | PORT port-number} [ROBOT robot-name]

Parameters

slot-number

An integer value indicating the robot slot.

drv-number

An integer value indicating the physical drive in the robot.

port-number

An integer value indicating the robot port.

robot-name

The name for the media robot.

Example

The following MRU example moves a cartridge from a drive to the a slot of an MSL G3 Series tape library.

$ ROBOT MOVE DRIVE 1 SLOT 10 ROBOT $2$GGA0:

POSITION

POSITION — Positions the cartridge manipulation mechanism to the specified location.

Format

POSITION {SLOT slot-number | DRIVE drv-number | PORT port-number} [ROBOT robot-name]

Parameter

slot-number

An integer value indicating a physical slot in the media robot.

drv-number

An integer value indicating a physical drive in the media robot.

port-number

An integer value indicating a physical port in the media robot.

robot-name

The name for the media robot.

Example

The following MRU example positions the tape library mechanism at slot 23 in a tape library. 

$ ROBOT POSITION SLOT 23 ROBOT $2$GGA0:

HOME

HOME — Returns a cartridge from a specified location to its home (previous) location.

Additional Information

The home position varies across media robots. To determine the home location of your media robot, consult the hardware documentation or issue the command and observe where the mechanism is positioned.

Format

HOME [ROBOT robot-name] {DRIVE drv-number | SLOT slot-number | PORT port-number | TRANSPORT transport-number}

Parameter

robot-name

The name for the media robot.

Example

The following MRU example places the mechanism to the home position in a tape library. 

$ ROBOT HOME DRIVE 1 ROBOT $2$GGA0:

FIND_CARTRIDGE

FIND_CARTRIDGE — Locates a specified cartridge within a modern tape library. If the named cartridge resides in the media robot, MRU software returns its location.

Additional Information

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.

Format

FIND CARTRIDGE cartridge-name [ROBOT robot-name]

Parameter

cartridge-name

The name of the external label on the cartridge. The cartridge name parameter is case sensitive.

robot-name

The name for the media robot.

Examples

  1. The following MRU example locates cartridge OD5168 in the MSL G3 Series library.

    $ ROBOT FIND CARTRIDGE OD5168 ROBOT $2$GGA0:

  2. MRU allows wildcard names for this command. This example shows all elements that are full, namely:

    • slots

    • drives

    • transports

    • ports

    $ ROBOT FIND CARTRIDGE ?*

  3. The following command shows all slots, drives, transports and ports, irrespective of whether they are full or empty, showing all elements available in the library.

    $ ROBOT FIND CARTRIDGE *

RESERVE

RESERVE — Sends a SCSI Reserve command to a media robot for exclusive use.

Additional Information

The RESERVE command reserves the media robot for exclusive use on the host. This is useful in Fibre Channel environments where multiple hosts have access to the same media robot.

If a media robot is reserved on a host, all other hosts will be unable to issue SCSI commands and will receive a SCSI Reservation Conflict message.

Format

RESERVE [ROBOT robot-name]

Parameters

robot-name

The name for the media robot.

Example

The following MRU example reserves the media robot $2$GGA0: on the calling host for exclusive use in a Fibre Channel environment: 

$ ROBOT RESERVE ROBOT $2$GGA0:

RELEASE

RELEASE — Sends a SCSI Release command to the media robot.

Additional Information

The RELEASE command releases the media robot from exclusive use on the host. This command is used when a media robot has already been reserved and is issued from the same host that holds the reservation.

Format

RELEASE [ROBOT robot-name]

Parameters

robot-name

The name for the media robot.

Example

The following MRU example releases the media robot from exclusive use on the same host that reserved it: 

$ ROBOT RELEASE ROBOT $2$GGA0:

INITIALIZE

INITIALIZE — Inventories the robot and updates the MRU software's internal database of robot elements. The time it takes to complete the operation depends on the size of the robot. A small loader takes less time to inventory than a multitower robot.

Format

INITIALIZE [ROBOT robot-name]

Parameter

robot-name

The name for the media robot.

Example

The following MRU example inventories a tape loader:

$ ROBOT INITIALIZE ROBOT $2$GGA0:

4.3.  Media Robot Status Commands

The following descriptions outline the general syntax of each command.

SHOW ROBOT

SHOW ROBOT — Displays information about the specified robot.

Displayed Information

  • Robot name

  • Robot type

  • Vendor model and firmware version

  • Maximum number of cartridge storage locations

  • Maximum number of drives

  • Maximum number of ports

Format

SHOW ROBOT [ROBOT robot-name]

SHOW PORT

SHOW PORT — Displays information about a port.

Displayed Information

The output of the command includes the type of port and one of these possible states:

Full or barcode

The port contains a cartridge. The barcode value of the cartridge occupying the port appears if the media robot is capable of reading cartridge barcodes.

Empty

The port contains no cartridge and is available for use.

Unavailable

The port is unavailable for use.

Format

SHOW [ROBOT robot-name] PORT [[[port-number]|[port-number-port-number]],...]

SHOW SLOT

SHOW SLOT — Shows the status of slots.

Displayed Information

One of these possible states is reported:

Full or barcode

The slot contains a cartridge. The barcode value of the cartridge occupying the slot appears if the media robot is capable of reading cartridge barcodes.

Empty

The slot contains no cartridge and is available for use.

Unavailable

The slot is unavailable for use.

Format

SHOW [ROBOT robot-name] SLOT [[[slot-number]|[slot-number-slot-number]],...]

SHOW DRIVE

SHOW DRIVE — Shows the status of drives.

Displayed Information

One of these possible states is reported:

Full or barcode

The drive contains a cartridge. The barcode value of the cartridge occupying the drive appears if the media robot is capable of reading cartridge barcodes.

Empty

The drive contains no cartridge and is available for use.

Unavailable

The drive is unavailable for use.

Format

SHOW [ROBOT robot-name] DRIVE [[[drv-number]|[drv-number-drv-number]],...]

4.4. Other Commands

SHOW VERSION

SHOW VERSION — Displays the currently installed version of the Media Robot Utility software.

Format

SHOW VERSION

HELP

HELP — Displays the reference information about the Media Robot Utility commands.

Format

HELP

A. Sample Installation Logs

Example A.1. Installation Successful, IVP Successful

If both the installation procedure and the IVP finish successfully, your output will look similar to the following:

$ @SYS$UPDATE:VMSINSTAL.COM MRU019 $10$DKC0:[PACKS]


        OpenVMS  Software Product Installation Procedure V9.2-3


It is 7-JAN-2026 at 09:04.

Enter a question mark (?) at any time for help.

* Are you satisfied with the backup of your system disk [YES]?


The following products will be processed:

  MRU V1.9


        Beginning installation of MRU V1.9 at 09:04

    **********************************************************************
%VMSINSTAL-I-VALSIGN, Performing product kit validation of signed kits ...
Success
%VMSINSTAL-I-VALPASSED, validation of $10$DKC0:[PACKS]MRU019.A_VNC succeeded
Success
%VMSINSTAL-I-VALPASSED, validation of $10$DKC0:[PACKS]MRU019.B_VNC succeeded
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

        Media Robot Utility for OpenVMS V1.9-2 (MRU) Installation

© Copyright 2026 VMS Software, Inc. and Hewlett-Packard Enterprise Development LP

You are running OpenVMS Version V9.2-3

* Do you want to purge files replaced by this installation [YES]?
* Do you want to run the IVP after the installation [YES]?
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-I-SYSDIR, This product creates system specific directory [SYSHLP.EXAM
PLES.ROBOT].

    The Media Robot Utility (MRU) V1.9-2 has been installed.

    MRU is run with the following commands:

        ROBOT   command-line interface
        XROBOT  DECwindows interface

    Type $ HELP ROBOT or $ HELP XROBOT for more information on using MRU.

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

MRU V1.9-2 Installation Verification Procedure (IVP)
© Copyright 2026 VMS Software, Inc. and Hewlett-Packard Development Company, L.P.

The following HSx connected SCSI loaders and libraries were found :

The following Direct connected SCSI loaders and libraries were found :

The following Fibre Channel connected SCSI loaders and libraries were found :

Device                  Device           Error
Name                   Status           Count
$2$GGA0:                Online               0

The following DSSI connected loaders were found :

The following DSA connected loaders were found :

Please enter the robot name of a media loader or library [$2$GGA0:] :

Media Robot Utility V1.9-2


Robot Name: $2$gga0: Type: SCSI

Media Robot Identifier: HP      MSL G3 Series   9.60

Slots:          24
Drives:         2
Inports:        0
Outports:       0
Transports:     1

SHOW ONLY SLOTS 0-3:
SLOT:           0               Empty
SLOT:           1               OD5173
SLOT:           2               OD5167
SLOT:           3               Empty

SHOW ALL DRIVES:
DRIVE:          0               OD5174
DRIVE:          1               Empty

SHOW ALL PORTS:
No elements are available for SHOW Ports.
%ROBOT-E-NO_ELEMENTS, No element(s) found


    The IVP for MRU V1.9-2 has completed.
    Please confirm that the ROBOT commands were successful.

        Installation of MRU V1.9 completed at 09:04

    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

    Creating installation data file: VMI$ROOT:[SYSUPD]MRU019.VMI_DATA


        VMSINSTAL procedure done at 09:04
Example A.2. Installation Successful, IVP failed

If the installation finishes, but IVP fails, your output will look similar to the following:

@SYS$UPDATE:VMSINSTAL.COM MRU019 $10$DKC0:[PACKS]


        OpenVMS  Software Product Installation Procedure V9.2-3


It is 7-JAN-2026 at 21:36.

Enter a question mark (?) at any time for help.

* Are you satisfied with the backup of your system disk [YES]?


The following products will be processed:

  MRU V1.9


        Beginning installation of MRU V1.9 at 21:36

    **********************************************************************
%VMSINSTAL-I-VALSIGN, Performing product kit validation of signed kits ...
Success
%VMSINSTAL-I-VALPASSED, validation of $10$DKC0:[PACKS]MRU019.A_VNC succeeded
Success
%VMSINSTAL-I-VALPASSED, validation of $10$DKC0:[PACKS]MRU019.B_VNC succeeded
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

        Media Robot Utility for OpenVMS V1.9-2 (MRU) Installation

© Copyright 2026 VMS Software, Inc. and Hewlett-Packard Enterprise Development LP

You are running OpenVMS Version V9.2-3

* Do you want to purge files replaced by this installation [YES]?
* Do you want to run the IVP after the installation [YES]?
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-I-SYSDIR, This product creates system specific directory [SYSHLP.EXAM
PLES.ROBOT].

    The Media Robot Utility (MRU) V1.9-2 has been installed.

    MRU is run with the following commands:

        ROBOT   command-line interface
        XROBOT  DECwindows interface

    Type $ HELP ROBOT or $ HELP XROBOT for more information on using MRU.

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

MRU V1.9-2 Installation Verification Procedure (IVP)
© Copyright 2026 VMS Software, Inc. and Hewlett-Packard Development Company, L.P.

The following HSx connected SCSI loaders and libraries were found :

The following Direct connected SCSI loaders and libraries were found :

The following Fibre Channel connected SCSI loaders and libraries were found :

The following DSSI connected loaders were found :

The following DSA connected loaders were found :

Please enter the robot name of a media loader or library :

    No robot devices have been found.

    Please make sure:

      o  All robots are powered on
      o  Any Fibre Channel robots are configured with 'SYSMAN IO FIND_WWID'
          and 'SYSMAN IO AUTO' commands

    To run this IVP again, type  $ @SYS$TEST:ROBOT$IVP


    The IVP for MRU V1.9-2 has failed.


        Installation of MRU V1.9 completed at 21:37

    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

    Creating installation data file: VMI$ROOT:[SYSUPD]MRU019.VMI_DATA


        VMSINSTAL procedure done at 21:37