User`s guide

System Initialization and Acceptance Testing (Normal Operation)
4.4 Basic Acceptance Test Procedure
4. Run one pass of the DSSI internal drive tests (DRVTST and DRVEXR)
using the Diagnostic Utility Protocol (DUP) driver as described in
Section 5.4.
5. If the above steps complete successfully and you have time to test the
Q–bus options, load MDM. (MDM release 137A, V4.8A, or higher is
required for VAX 4000 Model 100/100A systems; Model 105A/106A requires
release 138, V4.9, or higher.) Run the system tests from the Main Menu. If
they run successfully, the system has gone through its basic checkout and
the operating system software can be loaded.
6. Bring up the operating system.
7. Bringing up the OpenVMS operating system completes the installation
procedures. Run the VMS User Environment Test Package (UETP) to test
that the OpenVMS operating system is correctly installed.
4.5 Machine State on Power-Up
This section describes the state of the kernel after a power-up halt.
The descriptions in this section assume the system has just powered-up
and the power-up diagnostics have successfully completed. The state of the
machine is not defined if individual diagnostics are run or for any other halts
other than a power-up halt (SAVPSL<13:8>(RESTART_CODE) = 3). Refer
to Appendix D for a description of the normal state of CPU configurable bits
following completion of power-up tests.
4.6 Main Memory Layout and State
Main memory is tested and initialized by the firmware on power-up.
Figure 4–2 is a diagram of how main memory is partitioned after diagnostics.
System Initialization and Acceptance Testing (Normal Operation) 4–17