System Initialization and Acceptance Testing (Normal Operation)
4.3 CPU ROM-Based Diagnostics
4.3.2 Scripts
Most of the tests shown by utility 9E are arranged into scripts. A
script
is
a data structure that points to various tests and defines the order in which
they are run. Scripts should be thought of as diagnostic tables—these tables
do not contain the actual diagnostic tests themselves, instead scripts simply
define what tests or scripts should be run, the order in which the tests or
scripts should be run, and any input parameters to be parsed by the Diagnostic
Executive.
Different scripts can run the same set of tests, but in a different order and
/or with different parameters and flags. A script also contains the following
information:
• The parameters and flags that need to be passed to the test.
• The location from where the tests can be run. For example, certain tests
can be run only from the FEPROM. Other tests are program-independent
code, and can be run from FEPROM or main memory to enhance execution
speed.
• What is to be shown, if anything, on the console.
• What is to be shown, if anything, in the LED display.
• What action to take on errors (halt, repeat, continue).
The power-up script runs every time the system is powered on. You can also
invoke the power-up script at any time by entering T 0.
Additional scripts are included in the ROMs for use in manufacturing and
engineering environments. Customer Services personnel can run these scripts
and tests individually, using the T command. When doing so, note that
certain tests may be dependent upon a state set up from a previous test. For
this reason, use the UNJAM and INITIALIZE commands before running an
individual test. You do not need these commands on system power-up because
the system power-up leaves the machine in a defined state.
Customer Services Engineers (CSE) with a detailed knowledge of the system
hardware and firmware can also create their own scripts by using the 9F User
Script Utility. Table 4–3 lists the scripts available to Customer Services.
System Initialization and Acceptance Testing (Normal Operation)
4–13
