HP OpenVMS Systems Documentation
OpenVMS Alpha Version 7.3
After you have successfully installed the operating system, boot the
new system disk, as described in the following sections.
3.7.1 Preparing to Boot the New System Disk
Before you boot the new system disk, you must do the following:
SET BOOTDEF_DEV target-drive
Substitute the device name of the system disk for target-drive. The SET BOOTDEF_DEV command tells the system which disk to boot from. For example, if the system disk has the device name DKA400, enter the following command and press the Return key:
>>> SET BOOTDEF_DEV DKA400
>>> SET BOOTDEF_DEV DUA18.104.22.168.0
To boot the system disk, enter the following command and press the Return key:
>>> BOOT -FLAGS 0,0
When the system finishes booting, it displays informational messages that begin as follows:
OpenVMS (TM) Alpha Operating System, Version 7.3 %DECnet-I-LOADED, network base image loaded, version = 05.0D.00 $! Copyright (c) 2001 Compaq Computer Corporation. All rights reserved. Installing required known files... Configuring devices... . . .
1 For more information about halting your Alpha computer, see Appendix A.
If during the installation, you previously answered Yes to the question about joining an OpenVMS Cluster, the system now asks a series of questions about your configuration (CI, DSSI, SCSI, local area, or mixed-interconnect).
You might need to refer to OpenVMS Cluster Systems or Guidelines for OpenVMS Cluster Configurations to answer
3.8.1 OpenVMS Cluster Prompts
Table 3-1 lists the OpenVMS Cluster prompts and suggested responses. Note that, depending on your responses and particular cluster configuration, some prompts will not be displayed.
|Question||How to Respond|
|Will this node be a cluster member (Y/N)?||Enter Y.|
|What is the node's DECnet node name?||Enter the DECnet node name (for example, MYNODE). The DECnet node name may be from one to six alphanumeric characters in length and cannot include dollar signs or underscores.|
|What is the node's DECnet node address?||Enter the DECnet node address --- for example, 2.2.|
|Will the Ethernet be used for cluster communications (Y/N)?||Enter N for a CI only or DSSI-only OpenVMS Cluster. Otherwise, answer Y. 1|
|Enter this cluster's group number:||Enter a number in the range from 1 to 4095 or 61440 to 65535.|
|Enter this cluster's password:||Enter the cluster password. The password must be from 1 to 31 alphanumeric characters in length and may include dollar signs and underscores. 2|
|Reenter this cluster's password for verification:||Reenter the password.|
|Will MYNODE be a disk server (Y/N)?||Enter Y if you want local disks to be served to the cluster (mandatory for local area and mixed-interconnect configurations). Refer to OpenVMS Cluster Systems for information on served cluster disks.|
|Will MYNODE serve RFxx disks (Y)?||Enter a response appropriate for your DSSI configuration, if such disks are available to your system.|
|Enter a value for MYNODE's ALLOCLASS parameter:||In a CI only system (connected to a dual-ported disk), a DSSI-only system, or a local area or mixed-interconnect configuration where nodes serve DSSI or CI disks, enter the appropriate allocation class value (1 to 255). Otherwise, enter 0. For information about selecting the ALLOCLASS parameter, see OpenVMS Cluster Systems.|
|Does this cluster contain a quorum disk (Y/N)?||
For CI only, SCSI, local area, and mixed-interconnect configurations,
enter Y or N, depending on your configuration.
For most DSSI systems, enter Y. However, if you are adding a two-system DSSI configuration to an existing cluster (in which case you might not need a quorum disk), you can answer N.
If you enter Y, the system asks for the name of the quorum disk. Enter the device name of the quorum disk.
Refer to OpenVMS Cluster Systems for information on quorum disks.
The system next runs AUTOGEN to evaluate your hardware configuration and estimate typical work loads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and you reboot your system, the installation procedure is complete.
The installation procedure displays messages similar to the following:
AUTOGEN will now be run to compute the new SYSGEN parameters. The system will then shut down and reboot, and the installation or upgrade will be complete. After rebooting you can continue with such system management tasks as: Decompressing the System Libraries Configuring DECnet Using SYS$MANAGER:CLUSTER_CONFIG.COM to create an OpenVMS Cluster Creating FIELD, SYSTEST, and SYSTEST_CLIG accounts if needed %AUTOGEN-I-BEGIN, GETDATA phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GETDATA phase has successfully completed. %AUTOGEN-I-BEGIN, GENPARAMS phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created. You may wish to purge this file. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GENPARAMS phase has successfully completed. %AUTOGEN-I-BEGIN, GENFILES phase is beginning. %SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended %SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended %SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created %AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages that have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may wish to review the information in that file. %AUTOGEN-I-END, GENFILES phase has successfully completed. %AUTOGEN-I-BEGIN, SETPARAMS phase is beginning. . . .
The system is shutting down to allow the system to boot with the generated site-specific parameters and installed images. The system will automatically reboot after the shutdown and the installation will be complete. SHUTDOWN -- Perform an Orderly System Shutdown on node ALPCSI %SHUTDOWN-I-BOOTCHECK, performing reboot consistency check... %SHUTDOWN-I-CHECKOK, basic reboot consistency check completed . . .
If the system does not reboot automatically, reboot the system manually.
For example, if the system disk is on an RZ25 disk drive with a unit number of 1, enter the following command and press the Return key:
>>> BOOT DKA1
After the system reboots, a message similar to the following is displayed:
OpenVMS (TM) Alpha Operating System, Version 7.3 Copyright (c) 2001 Compaq Computer Corporation. All rights reserved. %STDRV-I-STARTUP, OpenVMS startup begun at 27-MAY-2001 14:50:18.35 . . .
The system next displays informational messages and accounting information indicating that your Compaq OpenVMS Alpha operating system is running. For example:
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 27-MAY-2001 14:51:23.47 Accounting information: Buffered I/O count: 2177 Peak working set size: 6848 Direct I/O count: 1358 Peak page file size: 179552 Page faults: 1805 Mounted volumes: 0 Charged CPU time: 0 00:00:13.37 Elapsed time: 0 00:01:06.20
At this time, you can log in to the SYSTEM account (so you can perform postinstallation tasks), as described in the following sections.
3.10 Logging in to the SYSTEM Account from a Character Cell Terminal
Log in to a character cell terminal by entering the user name SYSTEM
followed by the password. The display is similar to the following:
OpenVMS (TM) Alpha Operating System, Version 7.3 Username: SYSTEM Password: . . . OpenVMS (TM) Alpha Operating System, Version 7.3
(If you forget your password, follow the instructions in Appendix A
to perform an emergency startup.)
3.11 Logging in to the SYSTEM Account from a Workstation
If you installed the DECwindows Motif for OpenVMS Alpha software on your workstation, do the following after the login window displays on your screen:
After you have successfully installed the Compaq OpenVMS Alpha operating system and logged in to the SYSTEM account, you must perform certain postinstallation tasks before you can use the system. For complete information, go to Chapter 4.
After you have installed the Compaq OpenVMS Alpha operating system, you must perform several important tasks to prepare the system for operation. This chapter describes the following postinstallation tasks in the order in which you perform them:
The installation procedure gave you the opportunity to register any software product licenses. If you did not register your Compaq OpenVMS Alpha licenses at that time, you must do so before you can use the Compaq OpenVMS Alpha operating system. You must also register the licenses for Compaq OpenVMS Alpha layered products.
You can invoke the OpenVMS License utility by entering the following command:
(You can also use the LICENSE REGISTER command.)
For information about registering licenses, see the following:
During the installation, DEFAULT and SYSTEM accounts are created for you automatically. However, if you plan to have Compaq service representatives test your system or if you plan to run testing software such as UETP, you must create accounts for each representative and a SYSTEST (standalone system) or SYSTEST_CLIG (OpenVMS Cluster system) account to run UETP.
For complete information about creating accounts for Compaq service
representatives and UETP, see the OpenVMS System Manager's Manual, Volume 1: Essentials.
4.3 Backing Up Your System Disk
After you install the operating system, protect your work by making a backup copy of the system disk in case you have any problems while customizing it.
To back up the system disk:
In addition to backing up the system disk now before you customize it, you should back up your system disk again after you successfully complete your customization tasks and install layered products.
For complete information about backup operations, including a
description of an alternate method that does not require booting from
the operating system CD-ROM and that allows you to
back up a shadowed disk without disabling the shadow set, see
4.4 Customizing the System
You can customize the system to meet your site-specific needs. In addition, if your Alpha computer is part of an OpenVMS Cluster environment, you must prepare the cluster environment and configure the cluster.
For instructions on customizing the system, review the following documentation:
If you have installed the DECwindows Motif for OpenVMS Alpha layered product (see Section 4.10), you can customize your DECwindows environment.
The following sections describe how to configure and start your
4.5.1 DECnet-Plus for OpenVMS Alpha
If you installed DECnet-Plus for OpenVMS Alpha software, refer to the DECnet-Plus
for OpenVMS Release Notes and DECnet-Plus for OpenVMS
Installation and Basic Configuration for postinstallation
4.5.2 DECnet Phase IV for OpenVMS Alpha
Support for DECnet Phase IV for OpenVMS Alpha is only available under Compaq's Prior Version Support Program. Contact your local Compaq support representative for additional information.
!$ SUBMIT SYS$MANAGER:STARTNET.COM
$! DECNET_VERSION = F$INTEGER(F$EXTRACT(2,2,F$GETSYI("DECNET_VERSION"))) $! IF DECNET_VERSION .GE. 5 $! THEN $! START/NETWORK "DECNET/OSI" $! ELSE $! START/NETWORK DECNET $! ENDIF
$ DEFINE DECW$IGNORE_DECNET TRUE
If you installed Compaq TCP/IP Services for OpenVMS software, refer to the TCP/IP
Services for OpenVMS Installation and Configuration manual for
information about how to configure this software using the
4.6 Testing the System with UETP
The User Environment Test Package (UETP) is a software package designed to test whether the OpenVMS Alpha operating system is installed correctly. As part of the postinstallation procedure, Compaq recommends that you run UETP to verify the installation.
For complete information about using UETP, see the OpenVMS System Manager's Manual.
4.7 Decompressing the System Libraries
Decompressing the system libraries gives the system faster access to
them. The decompressed libraries require several thousand additional
blocks of disk space for all libraries to be decompressed. You use the
LIBDECOMP.COM procedure to decompress the libraries.
4.7.1 Determining Disk Space
To find out how much disk space you have, enter the following command and press the Return key:
$ SHOW DEVICE SYS$SYSDEVICE
The additional amount of disk space required to decompress all the system libraries is about 55,000 blocks. Note that you can choose to decompress only the libraries that are used frequently.
Table 4-1 gives the approximate number of blocks consumed by each library after decompression.