- ATTACH
ATT DW780 HUB DWn ! attaches the DW780
or
ATT DW750 HUB DWn ! attaches the DW750
or
ATT DW730 HUB DWn ! attaches the DW730
* ATT TK50 DW0 MUA0 774500 260 5 ! attaches the TK50
... MUB0 760444 320 5
... MUC0 760450 324 5
... MUD0 760454 328 5
- DEVICES
EVMDA supports up to 4 TK50 Controllers with 1 TK50 streaming tape
drive per controller.
- TK50
Device: TK50
Link: DWxn OR HUB
Generic name: MUxn
x = alpha character, designating a unique TK50 in a system.
n = numeric character, designating a unique TK50 in a system.
Additional information:
CSR : [octal 760000-777774] <774500,760444>
VECTOR: [octal 4-774] <260,320>
BR: [decimal 4-7] <5>
- SECTION
Defines the diagnostic program sections (/SECTION qualifier on RUN or
START) which program supports.
- DEFAULT
Evoked by typing: ST <return>
RUN EVMDA <return>
Runs default tests (Tests 1-3, Acceptance, Qualification, and Multi-Unit).
- MEDIA
Evoked by typing: ST/SEC:MEDIA <return>
RUN EVMDA/SEC:MEDIA <return>
Runs MEDIA section test (Test 4).
- CONVERSATION
Evoked by typing: ST/SEC:CONVERSATION <return>
RUN EVMDA/SEC:CONVERSATION <return>
Runs the Conversation Mode Test (Test 5).
This section enables the operator to create a unique
test sequence from the terminal.
- HELP
EVMDA is a Level 2R Data Reliability Exerciser for the TK50 TAPE SUBSYSTEM
Of the 5 tests, Test 1 through Test 3 can be run by DEFAULT.
Test 4 is in the MEDIA section, and is the Read Interchange test.
Test 5 is in the CONVERSATION section and allows running any specified
user input test sequence.
- SELECT
SEL MUxn ! selects the controller/drive to test
Example: Sel MUA0
- EVENT_FLAGS
There are 6 user event flags available for user options. They
are as follows:
1) Event Flag 4 - when set, performs data comparisons 100% of time.
2) Event Flag 5 - When set, inhibits all data comparisons.
NOTE: The default is for both event flags 4 and 5 to be reset, which
will allow data comparisons x% of the time, test dependent. Default
(x) = test 1 is 25%, test 2 is 4%, test 3 is 11% of the time. These
ratios exist to optimize streaming operations for all default tests.
3) Event Flag 6 - when set, will inhibit autodrop of a unit under test
due to excessive HARD errors. When reset, will permit autodrop of
a unit under test due to excessive hard errors. (Greater than 15
hard errors / pass.)
4) Event flag 7 - when set, will inhibit autoadd of a unit under test,
after it has been dropped due to excessive hard errors. When reset,
will enable auto add at the beginning of each new pass of the program.
5) Event Flag 8 - when set, will permit a user specified end of pass
limit in total bytes transferred for write operations. When reset,
the program will use the default end of pass limits.
6) Event Flag 9 - when set, will inhibit soft error messages. When
reset, will enable soft error messages.
- DATA_PATTERNS
Conversation mode testing permits the user selection of a data
pattern. The data patterns used in EVMDA are as follows:
Pattern 0 = all data patterns, selected sequentially
Pattern 1 = all zeros pattern
Pattern 2 = all ones pattern
Pattern 3 = alternating zeros and ones pattern
Pattern 4 = 2 bytes ones, two bytes zeros - peak shift pattern
Pattern 5 = 4 bytes ones, four bytes zeros
Pattern 6 = 3 bytes zeros, one byte ones.
Pattern 7 = 16 words of user selected data (Conversation Mode Test)
Pattern 8 = 256 bytes of incrementing data from 0 through 255
Pattern 9 = 256 bytes of random data
Pattern 10 = 10 bytes - worst case flux reversal
Pattern 11 = 32 bytes - worst case flux reversal 2
Pattern 12 = 4 bytes - peak shift (hex 6c, ff, 43, 0)
Pattern 13 = 32 bytes - floating ones pattern
Pattern 14 = 32 bytes - floating zeros pattern
Pattern 15 = 2 bytes - alternating bit pattern
Pattern 16 = 2 bytes - square pattern (hex ca, 35)
Pattern 17 = 32 bytes - individual peak shift pattern
Note: All patterns are used by default, and are reproduced the
required number of times to fill a large buffer. For example, if
pattern 8 is selected for use in a buffer of 1024 bytes in length,
it will be reproduced 4 times.
- SUMMARY
Summary data is maintained throughout the program execution. It
is NOT continuously updated. It is ONLY updated at the end of each
PASS or after a user issues an ABORT command to the Diagnostic
Supervisor. If a summary report is requested between passes, without
being preceded by an ABORT command, the performance data accumulated
up to the last end of pass will be reported. If the user wants the
performance data on the current pass to be included in the summary
report, than an ABORT command must precede the SUMMARY command.
* NOTE: If you are using 2 unibuses, ie DW0 and DW1, and you are
putting one tk50 on each, then the CSR address for MUB0
is not 760444. Instead it would be CSR=774500,vector=260
BR=5.