Table 4–31 (Cont.) CCA Component Descriptions
Parameter
Size
Description
Diagnostic
status
8 bytes
Results of the diagnostic tests. Initialized by firmware.
Breakdown of the status fields:
•
[07:00] = Error number
•
[15:08] = Subtest number
•
[23:26] = Test number
•
[27:24] = Group number
•
[30:28] = Diagnostic flags. For firmware use only.
•
31 = Set when bits 27:00 indicate a valid failure code.
The high-order four bytes are reserved for firmware.
Duplex
compati-
bility test
results
4 bytes
Results of the compatibility test. Written by firmware. See
Section 4.8.1.1 for the test descriptions and fault codes.
Reset
dispatch
block
16 bytes
Used by firmware and the OpenVMS operating system to
notify the firmware how to handle a reset entry to firmware.
See Section 4.8.1.2 for dispatch block description.
Boot
parameter
table
164 bytes
Boot parameter table. Initialized by firmware. See
Section 4.8.1.3 for the description.
Saved
register
block
132 bytes
Register block saved by the OpenVMS operating system on
a CPU/MEM fault. Initialized and used by the operating
system.
Reserved
64 bytes
Reserved for future expansion.
4.8.1.1 Duplex Compatibility Test
On firmware entry, the console program verifies a number of conditions that are
required for system operation in Duplex mode. These conditions determine if the
zone is synchable, that is, able to join a partner zone in Duplex operation.
The IZC protocol is used by the console program to execute the Duplex
compatibility test. Once the console establishes the IZC service, it executes
the test and notifies the other zone of the results. A zone is considered synchable
if it passes the test.
The compatibility test is responsible for storing the results in the CCA. The
following items are test parameters.
•
Diagnostic status:
CPU self-test passes
CPU zone test passes
Primary I/O expansion module self-test passes
CPU system test does not fail (not run assumes a passed condition)
•
Zone identification:
One Zone A, one Zone B.
Error Handling and Analysis 4–57