- HELP
The Level 2R Generic MSCP Exerciser (EVRAE) is an online, user mode,
"parallel" diagnostic designed to verify the integrity of one or
several MSCP (DSA) drives under test, and to detect faults at the
functional level. The Exerciser should give a clear indication as to
how drives will perform under stressful operating system conditions.
EVRAE 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.
In order to make effective use of this tool, the user account should
have a direct I/O limit of at least 30 and an AST limit of at least 30.
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, disk block selection (random vs.
sequential), LBN limits on a per-disk basis, and the selection of data
patterns. Writes are never performed on a disk unless the user
explicitly requests so.
When an operator is present (ie. the OPERATOR flag is set) writes to
volumns are performed only if the operator explicitly requests to do
so. When running in "UNattended mode" (ie. the OPERATOR flag is clear)
EVRAE will DEFAULT write/reading to volumns labeled SCRATCH and reading
only to volumns labeled other than SCRATCH.
This exerciser can test up to 10 MSCP disk drives simultaneously.
- DEVICES
EVRAE supports the following devices:
Device type Device name
----------- -----------
RA60 removable disk DJan
RA80 fixed disk DUan
RA81 fixed disk DUan
RC25 removable disk DAan
RCF25 fixed disk DAan
RX50 flexible disk DUan
RD51 fixed disk DUan
RD52 fixed disk DUan
RD53 fixed disk DUan
where a = controller designation (A, B, etc.)
n = unit number (0, 1, etc.)
All units to be exercised by this program must be online and MOUNTed
under VMS (before invoking the VAX Diagnostic Supervisor) and ATTACHed
and SELECTed under the Diagnostic Supervisor.
- RUN
The RUN command combines the actions of the LOAD and START commands.
Use of the RUN command with EVRAE will cause the program to be loaded
into memory followed by its immediate execution. The proper sequence
of commands is as follows:
DS> (Issue all required ATTACH commands)
DS> (Issue all required SELECT commands)
DS> RUN EVRAE
- LOAD
The LOAD command causes the named diagnostic to be loaded into memory,
but not executed. The LOAD command can be used in conjuction with the
START command as a two-step equivalent to the RUN command.
Assuming that the test units have been ATTACHed and SELECTed at some
point before the START command, EVRAE can be run as follows:
DS> LOAD EVRAE
DS> START
- START
The START command causes the most recently LOADed diagnostic to be
executed. The START command is generally used in conjuction with the
LOAD command as a two-step equivalent to the RUN command.
Assuming that the test units have been ATTACHed and SELECTed at some
point before the START command, EVRAE can be run as follows:
DS> LOAD EVRAE
DS> START
- ATTACH
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 EVRAE to exercise MSCP drive-units, the following adapters
and controllers must first be ATTACHed:
* The RDBX1 controller (for any RX50, RD51, RD52, or RD53)
must be ATTACHed to the HUB
* For all other disk types, either the UBA (UNIBUS adapter) or
* The BUA (BI-to-UNIBUS adapter) must be ATTACHed to the HUB
* The UDA50 controller (for any RA60, RA80, or RA81) must be
ATTACHed to the UBA or BUA
* The LESI controller (for any RC25 or RCF25) must be ATTACHed
to the UBA or BUA
- KDB50
DS> ATTACH
Device type? KDB50 !Controller name
Device Link? HUB !Link
Device Name? DUn !Where n = VMS Adapter letter
BI Node Number (HEX)? 6 !Node number
BR? 5
- RDBX1
Example:
DS> ATTACH ! Attach
Device type? RDBX1 ! the RDBX1 controller
Device link? HUB ! to the HUB
Device name? DUa ! a = controller designation (A, B, etc.)
BI Node Number? 4 ! Typical node ID
- UBA
DS> ATTACH
Device type? DW780 ( or ) DW750 ( or ) DW730
Device link? HUB HUB HUB
Device name? DW0 DW0 DW0
TR? 3 * *
BR? 4 * *
* = not applicable for this model
- BUA
Example:
DS> ATTACH ! Attach
Device type? DWBUA ! the BI-to-UNIBUS adapter
Device link? HUB ! to the HUB
Device name? DW0
NODE_ID? 7 ! Typical node number
BR? 5 ! Interrupt level for BUS ERROR interrupts
- UDA50
Example:
DS> ATTACH ! Attach
Device type? UDA50 ! the UDA50 controller
Device link? DW0 ! to the UBA or BUA
Device name? DUa ! a = controller designation (A, B, etc.)
IP? 772150 ! Typical IP address
VECTOR? 154 ! Typical vector address
BR? 5 ! Bus request level
Burst_rate? 2
- LESI
Example:
DS> ATTACH ! Attach
Device type? LESI ! the LESI controller
Device link? DW0 ! to the UBA or BUA
Device name? DAa ! a = controller designation (A, B, etc.)
IP? 760354 ! Typical IP address
VECTOR? 310 ! Typical vector address
BR? 5 ! Bus request level
- RX50
Example:
DS> ATTACH ! Attach the RX50 floppy disk to its
Device type? RX50 ! RDBX1 controller (DUa)
Device link? DUa ! a = controller designation (A, B, etc.)
Device name? DUan ! n = unit number (0, 1, etc.)
- RD51
Example:
DS> ATTACH ! Attach the RD51 fixed disk to its
Device type? RD51 ! RDBX1 controller (DUa)
Device link? DUa ! a = controller designation (A, B, etc.)
Device name? DUan ! n = unit number (0, 1, etc.)
- RD52
Example:
DS> ATTACH ! Attach the RD52 fixed disk to its
Device type? RD52 ! RDBX1 controller (DUa)
Device link? DUa ! a = controller designation (A, B, etc.)
Device name? DUan ! n = unit number (0, 1, etc.)
- RD53
Example:
DS> ATTACH ! Attach the RD53 fixed disk to its
Device type? RD53 ! RDBX1 controller (DUa)
Device link? DUa ! a = controller designation (A, B, etc.)
Device name? DUan ! n = unit number (0, 1, etc.)
- RA60
Example:
DS> ATTACH ! Attach the RA60 removable disk to its
Device type? RA60 ! UDA50 controller (DUa)
Device link? DUa ! a = controller designation (A, B, etc.)
Device name? DJan ! n = unit number (0, 1, etc.)
- RA80
Example:
DS> ATTACH ! Attach the RA80 fixed disk to its
Device type? RA80 ! UDA50 controller (DUa)
Device link? DUa ! a = controller designation (A, B, etc.)
Device name? DUan ! n = unit number (0, 1, etc.)
- RA81
Example:
DS> ATTACH ! Attach the RA81 fixed disk to its
Device type? RA81 ! UDA50 controller (DUa)
Device link? DUa ! a = controller designation (A, B, etc.)
Device name? DUan ! n = unit number (0, 1, etc.)
- 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
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 EVRAE, all disks to be exercised must be SELECTed with the
/NOALLOCATE qualifier. Since the disks have already been mounted
(and, by implication, allocated), this qualifier prevents the
Diagnostic Supervisor from attempting a second allocate to the device.
Examples:
SELECT/NOALLOCATE DUA0
SELECT/NOALLOCATE DAA0, DAA1, DUA0
SELECT/NOALLOCATE DAB3, DUB2, DJA1
- EVENT
EVRAE does not support any user-alterable event flags.
- OPERATOR
If the program is being run in attended mode (i.e., OPERATOR flag
is set), then the program will prompt the user for the write-protect
status of each disk selected for testing. These questions will appear
immediately after the program is started, before any testing takes
place:
FOR UNIT _DAan, VOLUME "volume name" ...
ALLOW WRITES TO CUSTOMER DATA AREA ON THIS PLATTER [(No), Yes]
If the operator answers YES, the program prints a warning, followed by a
confirmation prompt:
** WARNING - CUSTOMER DATA WILL BE OVERWRITTEN! ... CONFIRM [(No), Yes]
A NO answer to either question will protect the customer LBNs.
If the program is run in UNattended mode (i.e., OPERATOR flag is clear),
then these questions will not appear, and EVRAE will DEFAULT
write/reading to volumns labeled SCRATCH and reading only to volumns
labeled other than SCRATCH.
- QUICK
Using the QUICK flag with EVRAE reduces the time to execute one pass
from 10 minutes to 1 minute. (The pass time limit can also be set by
the user if the Manual (/SECTION:MANUAL) program section is run).
To set the QUICK flag, type the following command before starting
EVRAE:
DS> SET FLAG QUICK
To clear the QUICK flag, type:
DS> CLEAR FLAG QUICK
- SECTION
Defines the sections (/SECTION qualifier on RUN or START) which this
program supports. The Level 2R Generic MSCP Disk Exerciser (EVRAE)
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 MSCP disks using default
program parameters and options.
Assuming that the test units have been ATTACHed and SELECTed, this
section may be run in a variety of ways:
DS> LOAD EVRAE
DS> START (or)
DS> START/SECTION:DEFAULT
- OR -
DS> RUN EVRAE (or)
DS> RUN EVRAE/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.
Assuming that the test units have been ATTACHed and SELECTed, this
section may be run in one of two ways:
DS> LOAD EVRAE
DS> START/SECTION:MANUAL
- OR -
DS> RUN EVRAE/SECTION:MANUAL
- SUMMARY
The SUMMARY command will cause the current exerciser statistics to
be printed on the console terminal. In addition to the elasped time
of exerciser activity, 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