- 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.
- 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
BI Node Number? 0
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
- 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 DAA0, DAA1
- DEVICES
EVRMC supports DA devices
- EVENT
Event flag number 21 is used by the operator to select one of the
two host operating modes. EFN_21 state definition is as follows:
EFN_21 = 0 : UN-ATTENDED reformat mode
-------------------------
This is the hosts default operating mode. When
efn_21 is cleared the host will first prompt
the operator for the date. The host will then
automatically instruct the DM formatter to do
a REFORMAT on all sub-systems devices selected
by the operator.
EFN_21 = 1 : ATTENDED format mode
--------------------
If the operator wishes to select a formatting
mode other than a REFORMAT mode, he/she must
set efn_21. When set the operater has the
responsibility to anwser all DM formatter
software parameter questions.
- HELP
This program will prepare RC25 media for use as addressable storage by
providing headers and replacing of bad blocks. This formatter will be
composed of two sections; a host-resident section, and a
controller-resident DM code section.
The host section will serially format up to sixteen RC25 subsystems by
downline-loading the DM code, and monitor the task. The downline
section will consist of overlays of DM code. The first of these will be
down-line loaded to the drive itself,and accomplish the actual business
of formatting,calling in additional overlays as needed, asking software
parameters questions and printing formatter error and informational
messages.
There are three general modes of DM formatter operation and they are:
o REFORMAT - This mode is used to format a medium which has been
previously formatted, and is being reformatted to clear
existing data or to change the mode of the medium to 512 bytes
per sector. It assumes that the FCT is still intact.
o RESTORE - This mode will only be run by DIGITAL Manufacturing
personnel. It uses an external copy of the FCT produced when
the disk was manufactured and is stored offline to the RC25
formatter.
o RECONSTRUCT - This mode is used when none of the other modes
is possible. It detects bad blocks by performing repetitive
read checks of each sector. For this reason, a RECONSTRUCT
run takes considerably longer than the other modes.
There are two general modes of HOST operation and they are:
o ATTENDED MODE- This is where an operator must be present at the
console terminal to respond to DM formatter software parameter
questions. In this HOST mode the operator can choose any of the
three DM formatting modes.
o UN-ATTENDED MODE- This is where the HOST will automaticaly answer
DM formatter software parameter questions to perform a REFORMAT
mode to all units selected units via the hardware P_Tables.
********************************************************************
* WARNING *
* ------- *
* Media formatting is considered to be an atomic operation *
* *
* - ONCE STARTED IT CANNOT BE STOPPED - *
* *
* Aborting a format will leave media UNUSABLE *
* *
********************************************************************
For each of the folowing parameters, type "HELP EVRMC parameter"
- QUICK
There is no quick flag usage employed by this host formatter code.
- SECTION
Program sections are used within the $DS_BGNTEST macro to show which
section a test belongs to. This Host code has one test defined and
its section name is AZHOST.
To run this program type:
RUN EVRMC or
RUN EVRMC/SECTION:AZHOST or
or you can type:
LOAD EVRMC then
START or
START/SECTION:AZHOST or
- SUMMARY
All summary report coding is remote DM program driven. Upon normal
completion the formatter issues the following messages. All but the
last are sent as DUP informational messages. The last is sent as a
DUP termination message.
1. "format completed"
2. "n revectored LBNs"
Where n is the number of LBNs revectored in the user data
area.
3. "n primary revectored LBNs"
Where n is the number of LBNs in message #2 which were
primary revectors.
4. "n secondary/tertiary revectored LBNs"
Where n is the number of the LBNs in message #2 which were
secondary or tertiary revectors.
5. "n bad blocks in the RCT area due to data errors"
Where n is the number of blocks in the total RCT area which
were bad due to errors in the data portion of their sectors.
6. "n bad blocks in the RCT due to header or timing errors"
Where n is the number of blocks in the total RCT area which
were bad due to errors in the header or timing areas of
their sectors.
7. "n bad blocks in the DBN area due to data errors"
Where n is the number of blocks in the DBN area which were
bad due to errors in the data area of their sectors.
8. "n bad blocks in the DBN area due to header or timing
errors"
Where n is the number of blocks in the DBN area which were
bad due to errors in the header or timing area of their
sectors.
9. "n bad blocks in the XBN area due to data errors"
Where n is the number of blocks in the XBN area which were
bad due to errors in the data area of their sectors.
10. "n bad blocks in the XBN area due to header or timing
errors"
Where n is the number of blocks in the XBN area which were
bad due to errors in the header or timing area of their
sectors.
11. "n bad RBNS"
Where n is the number of blocks in the RBN area which were
bad due to errors in the data area of their sectors.
12. "n blocks retried on the check pass"
Where n is the number of blocks which had an error on the
first read attempt after formatting.
13. "FCT used successfully" or
14. "FCT was not used"
Depending on the answers to the start-up questions and the
availability of the bad block information (FCT). This
message has the DUP termination message code.