DEC VAXmate Service Manual page 203

IIIII
Test Descriptions
15 SYSTEM INTERACTION TEST
This Test initiates several processes at the same time to create a worst case
condition for system operation. This test ensures that each hardware subsys-
tem is being allocated the appropriate CPU time and completes its process
within a certain time. The system configuration is checked
to
determine what
processes may be started up on the system under test. The processes are
initiated in the following order.
Options (modem, 80287, and hard disk)
Main board (CPU, event timer, and mouse)
I/O board (communications, printer, diskette, and network)
The test begins by displaying the system configuration necessary for testing,
followed by a warning about diskette data being destroyed. All loopback con-
nectors and a scratch diskette are needed for this test. The system Interaction
Execution Menu is then displayed. The menu lists each process with a
description of what that process does. The description is only present for
options that are found to be present. The word ACTIVE is displayed on the
screen for each process that is currently running. This ACTIVE indication
should be used to determine what hardware was currently running when an
error occurs, indicating what hardware was involved in the interaction prob-
lem. Note that testing stops after the first error is detected, since it is impos-
sible to resume operation from the error.
A PROCESS PROGRESS error message indicates that one of the hardware sub-
systems did not receive the expected amount of CPU time. The intermediate
progress of all processes is checked about every 2 minutes. The test takes
about 10 minutes to complete.
You can abort the test by pressing the Ctrl and PF3 keys at the same time.
Note that since the keyboard is running a process of its own, you might get
an error attributed to breaking out of the test.
NOTE
Since many of the errors in this test are caused by the interaction of
one or more hardware subsystems, replacing the designated FRU may
not eliminate the problem. Therefore, it is up to the service
technician to judge what FRU or FRUs can be causing the problem.
The circuitry experiencing the interaction problem is listed in the
error description.
B-JO