- HELP
The Level 2R Exerciser for RC25 (EVRMD) is a "parallel" diagnostic
designed to verify the integrity of one or several drives under test,
and to detect faults at the functional level only. The Exerciser
should give a clear indication as to how an RC25 drive will perform
under stressful operating system conditions. EVRMD creates these
conditions by issuing a heavy load of logical I/O requests (VMS $QIOs)
to all units which are online and mounted under VMS, and ATTACHed and
SELECTed under the VAX-11 Diagnostic Supervisor. To accommodate these
I/O requests, the user account should have a direct I/O limit of at
least 50 and an AST limit of at least 50. The user can control many of
the I/O request parameters through the Manual Intervention Test
(/SEC:MANUAL) including function code (write only, read only, writes
and reads, write-with-data-checks, read-with-data-checks), disk block
selection (random vs. sequential), track number limits, and the
selection of data patterns.
This exerciser can test up to 4 LESI controllers (4 different IP
addresses), each controller having up to 2 drives (1 master and 1
slave), and each drive with 2 platters (RC25 removable and RCF25
fixed).
- DEVICES
EVRMD supports the following devices:
Device type Device name
----------- -----------
LESI - RC(F)25 controller DAa
RC25 - removable disk DAan
RCF25 - fixed disk DAan
where a = controller designation (A, B, etc.)
n = unit number (from unit plug)
- RUN
The RUN command normally combines the actions of the LOAD and START
commands. However, with revision 2.0 of EVRMD, the RUN command cannot
be used because all ATTACH and SELECT commands for units under test
must be issued AFTER the diagnostic has been LOADed into memory
(DS> LOAD EVRMD) but BEFORE the program has been STARTed.
- LOAD
The LOAD command causes the named diagnostic to be loaded into memory.
With revision 2.0 of EVRMD, the LOAD command must be issued before any
units to be tested are ATTACHed or SELECTed.
The proper sequence of commands is as follows:
DS> LOAD EVRMD
DS> (Issue all required ATTACH and SELECT commands)
DS> START
- ATTACH
With revision 2.0 of EVRMD, all ATTACH and SELECT commands for units
under test must be issued AFTER the diagnostic has been loaded into
memory (DS> LOAD EVRMD).
The ATTACH command is used for specifying descriptions of devices
existing on the system under test. A device cannot be accessed by
a diagnostic program unless it has first been attached. Attaching
a device generally consists of issuing a set of ATTACH commands so
that a series of links can be established from the processor to the
device. The link that is closest to the processor is a pseudo-
connection known as "HUB". All devices must be ultimately linked to
HUB. The format of the ATTACH command is as follows:
ATTACH dev-type dev-link generic-name [device-specific-info]
In order for EVRMD to exercise RC25 drive-units, the following
devices must first be ATTACHed:
UBA (UNIBUS adapter) - must be ATTACHed to the HUB
LESI (RC25 controller) - must be ATTACHed to the UBA
RC25 (removable disk) - must be ATTACHed to the LESI
RCF25 (fixed disk) - must be ATTACHed to the LESI
- UBA
DS> ATTACH
Device type? DW780 ( or ) DW750 ( or ) DW730
Device link? HUB HUB HUB
Device name? DW0 DW0 DW0
TR? 3 * *
BR? 4 5 *
* = not applicable for this model
- LESI
Example:
DS> ATTACH ! Attach
Device type? LESI ! the LESI controller
Device link? DW0 ! to the UNIBUS adapter
Device name? DAa ! a = controller designation (A, B, etc.)
IP? 772150 ! Typical IP address
VECTOR? 154 ! Typical vector address
BR? 5 ! Typical bus request level
- RC25
Example:
DS> ATTACH ! Attach the RC25 removable disk to its
Device type? RC25 ! LESI controller (DAa)
Device link? DAa ! a = controller designation (A, B, etc.)
Device name? DAan ! n = even unit number from unit plug
- RCF25
Example:
DS> ATTACH ! Attach the RCF25 fixed disk to its
Device type? RCF25 ! LESI controller (DAa)
Device link? DAa ! a = controller designation (A, B, etc.)
Device name? DAan ! n = odd unit number from unit plug
- SELECT
With revision 2.0 of EVRMD, all ATTACH and SELECT commands for units
under test must be issued AFTER the diagnostic has been loaded into
memory (DS> LOAD EVRMD).
The SELECT command selects devices for testing. A diagnostic program
will only test devices which have been SELECTed. Devices specified in
the SELECT command must have been previously ATTACHed. Multiple
devices may be specified in one command.
For EVRMD, all disks (RC25 and RCF25) to be exercised must be
SELECTed. SELECTing LESI controllers is optional and has no effect
on program operation.
General Format:
SELECT DAa, DAan [, DAan, ...]
Examples:
SELECT DAA, DAA0, DAA1
SELECT DAB4, DAB5
- EVENT
EVRMD does not support any user-alterable event flags.
- QUICK
EVRMD does not support use of the QUICK flag.
- SECTION
Defines the sections (/SECTION qualifier on RUN or START) which this
program supports. The RC25 Disk Exerciser (EVRMD) supports the MANUAL
program section in addition to the DEFAULT program section. The MANUAL
program section allows the user to change various program parameters
and options before any testing takes place.
- DEFAULT
This section will exercise all SELECTed RC25 (and RCF25) platters
using default program parameters and options.
To run this section, you must enter the following:
DS> LOAD EVRMD
DS> (Issue all required ATTACH and SELECT commands)
DS> START (or)
DS> START/SECTION:DEFAULT
- MANUAL
This section allows the operator to view and/or change various soft
parameters and options before any testing takes place. A series of
questions will be posed, along with the default answers and permissible
range of values. To select the default answer to any question, simply
type a carriage return. After all questions have been answered, the
program proceeds with testing in the normal manner.
To run this section, you must enter the following:
DS> LOAD EVRMD
DS> (Issue all required ATTACH and SELECT commands)
DS> START/SECTION:MANUAL
- SUMMARY
The SUMMARY command will cause the current exerciser statistics to
be printed on the console terminal. The following statistics are kept
on a per-unit basis:
* Number of read operations successfully completed
* Number of write operations successfully completed
* Number of megabytes read from the unit
* Number of megabytes written to the unit
* Number of hard errors experienced