- 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. This concept is
illustrated by the example below.
Format:
ATTACH uut-type link-name generic-name [device-specific]
- 780
DS> ATTACH
Device type? DW780
Device link? HUB
Device name? DW0
TR? 3
BR? 4
DS> ATTACH
Device type? LESI
Device link? DW0
Device name? DAA
IP? 772150
Vector? 154
Br? 5
DS> ATTACH
Device type? RC25
Device link? DAA
Device name? DAA0
DS> ATTACH
Device type? RCF25
Device link? DAA
Device name? DAA1
- 750
DS> ATTACH
Device type? DW750
Device link? HUB
Device name? DW0
DS> ATTACH
Device type? LESI
Device link? DW0
Device name? DAA
IP? 772150
Vector? 154
Br? 5
DS> ATTACH
Device type? RC25
Device link? DAA
Device name? DAA0
DS> ATTACH
Device type? RCF25
Device link? DAA
Device name? DAA1
- 730
DS> ATTACH
Device type? DW730
Device link? HUB
Device name? DW0
DS> ATTACH
Device type? LESI
Device link? DW0
Device name? DAA
IP? 772150
Vector? 154
Br? 5
DS> ATTACH
Device type? RC25
Device link? DAA
Device name? DAA0
DS> ATTACH
Device type? RCF25
Device link? DAA
Device name? DAA1
- 725
DS> ATTACH
Device type? DW730
Device link? HUB
Device name? DW0
DS> ATTACH
Device type? LESI
Device link? DW0
Device name? DAA
IP? 772150
Vector? 154
Br? 5
DS> ATTACH
Device type? RC25
Device link? DAA
Device name? DAA0
DS> ATTACH
Device type? RCF25
Device link? DAA
Device name? DAA1
- MicroVax
DS> ATTACH
Device type? LESI
Device link? HUB
Device name? DAA
UDAIP? 772150
Vector? 154
Br? 5
Burst_Rate? 2
DS> ATTACH
Device type? RC25
Device link? DAA
Device name? DAA0
DS> ATTACH
Device type? RCF25
Device link? DAA
Device name? DAA1
- 8200
DS> ATTACH
Device type? DWBUA
Device link? HUB
Device name? DW0
Node? 0
BR? 4
DS> ATTACH
Device type? LESI
Device link? DW0
Device name? DAA
UDAIP? 772150
Vector? 154
Br? 5
DS> ATTACH
Device type? RC25
Device link? DAA
Device name? DAA0
DS> ATTACH
Device type? RCF25
Device link? DAA
Device name? DAA1
- SELECT
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.
Format:
SELECT DAA, DAA0, DAA1
- DEVICES
EVRMB supports DA devices
- EVENT
If event flag 2 is set, then the operator will be prompted
for number of retries and whether to continue the test or
abort the program and also questions to include area tested
in some tests.
- HELP
The RC25 front end host diagnostic (EVRMB) is designed to test the
RC25 disk drive subsystem. Tests are performed to verify that:
a) The processor can properly communicate with the controller thru
the adapter card.
b) The RC25 drive can seek and head select properly.
c) The RC25 conforms to the specified seek and rotational times.
d) The RC25 controller can perform certain basic functions in
response to MSCP commands.
For each of the folowing parameters, type "HELP EVRMB parameter"
- QUICK
There is no quick flag usage employed by this program.
- SECTION
Defines the formatter sections (/SECTION qualifier on RUN or START)
which this formatter supports. This formatter host code supports
only the DEFAULT program section.
- UNIT
One RC25 unit (UUT) is defined as a single platter. There are two
platters on one spindle in an RC25 drive. The RC25 controller may
have either one or two drives (two or four platters). The unit
number for the RC25 platters come in pairs. The removable media
has an even number and the fixed media has the sequentially following
odd number. A maximum of 16 units can be tested in sequence.
- DEFAULT
This section will run all tests with the exception of manual test.
To run this section type:
RUN EVRMB or
RUN EVRMB/SECTION:DEFAULT or
or you can type:
LOAD EVRMB then
START or
START/SECTION:DEFAULT or
- CRD
This section will run tests intended for CRD.
To run this section type:
RUN EVRMB/SECTION:CRD
or you can type:
LOAD EVRMB
START/SECTION:CRD
- MANUAL
This section will run operator intervention test. This test is not
implemented in this revision.
- SUMMARY
EVRMB does not give summary report.