User`s guide

Error reports identify logical units, and also may identify physical devices.
Therefore, if errors occur while running against a unit, its storageset should
be reconfigured as individual devices, and then DILX run again, against the
individual devices.
There are no limitations on the number of units DILX may test at one time.
However, Digital recommends only using DILX when no host activity is present.
If you must run DILX during a live host connection, you should limit your
testing to no more than half of any controller’s units at one time. This conserves
controller resources and minimizes performance degradation on the live units you
are not testing.
DILX and the tape inline exerciser (TILX) may run concurrently with one
exerciser initiated from a maintenance terminal and the other from a virtual
terminal connection. If you have a dual-redundant controller configuration,
you can run DILX from a maintenace terminal connected to one controller, and
run TILX from another maintenance terminal connected to the other controller.
Digital recommends however, that both exercisers not be run while normal I/O
operations are in progress, as system performance will degrade due to the heavy
load the exercisers impose on the controller.
7.3.1.1 Invoking DILX
Note
Before running DILX, be sure that all units that you wish to test have
been dismounted from the host.
The following describes how to invoke DILX from a maintenance terminal at the
CLI> prompt, from a VCS, or from a virtual terminal through a DUP connection.
To invoke DILX from a maintenance terminal, enter the following command at
the CLI> prompt (or HSx> prompt, if set):
CLI> RUN DILX
To invoke DILX from the maintenance terminal port using a VCS, enter the
following command at the CLI> prompt:
CLI> VCS CONNECT device_name
Where device_name is the controller’s SCS node name.
Consult the VAXcluster Console System User’s Guide for complete details on using
VCS.
Note
The device_name must be specified for a VCS.
To invoke DILX from a virtual terminal using a DUP connection, enter the
command (for the OpenVMS operating system):
$ SET HOST/DUP/SERVER=MSCP$DUP/TASK=DILX SCS_nodename
Specify the controller’s SCS node-name to indicate where DILX will execute (for
HSJ and HSD30 array controllers only).
Diagnostics and Utilities 7–3