![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
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, the system displays a message similar to the following:
OpenVMS Alpha (TM) Operating System, Version V7.1
Copyright (c) 1996 Digital Equipment Corporation. All rights reserved.
%STDRV-I-STARTUP, VMS startup begun at 15-NOV-1996 16:24:02.27
.
.
.
The system next displays informational messages and accounting information indicating that your OpenVMS Alpha operating system is running. For example:
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 29-NOV-1996 12:55:43.92 Accounting information: Buffered I/O count: 1733 Peak working set size: 3184 Direct I/O count: 650 Peak page file size: 19440 Page faults: 974 Mounted volumes: 0 Charged CPU time: 0 00:00:04.45 Elapsed time: 0 00:00:34.82
At this time, you can log in to the SYSTEM account (so you can perform postinstallation tasks), as described in the following sections.
3.12.1 Logging in to 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:
Welcome to OpenVMS Alpha (TM) Operating System, Version V7.1
Username: SYSTEM
Password:
.
.
.
Welcome to OpenVMS Alpha (TM) Operating System, Version V7.1
(If you forget your password, follow the instructions in Appendix A
to perform an emergency startup.)
3.12.2 Logging in to 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 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 OpenVMS Alpha operating system, you must perform several important tasks to prepare the system for operation. These tasks, described in this chapter in the order in which you perform them, are as follows:
The installation procedure gave you the opportunity to register any software product licenses. If you did not register your OpenVMS Alpha licenses at that time, you must do so before you can use the OpenVMS Alpha operating system. You must also register the licenses for OpenVMS Alpha layered products.
You can invoke the OpenVMS License utility by entering the following command:
$ @SYS$UPDATE:VMSLICENSE
(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 Digital 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 Digital service
representatives and UETP, see the OpenVMS System Manager's Manual: 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.
4.3.1 How to Back Up the System Disk
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.
4.3.3 For More Information
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 Appendix B.
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:
Note: You can customize your DECwindows
environment as well, but you must first install the separate DECwindows
Motif for OpenVMS Alpha layered product (see Section 4.10).
4.5 Configuring and Starting Networking Software
The following sections describe how to configure and start your
networking software.
4.5.1 DECnet-Plus (Phase V)
If you installed DECnet-Plus for OpenVMS (Phase V) software, refer
DECnet-Plus for OpenVMS Release Notes and DECnet-Plus for
OpenVMS Installation and Basic Configuration for postinstallation
instructions.
4.5.2 DECnet (Phase IV)
If you plan to run DECnet for OpenVMS Alpha (Phase IV) software, note the following:
!$ 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
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, Digital 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
If you have approximately 30,000 free blocks on the disk, you can
decompress the libraries. Note that you can choose to decompress only
the libraries that are used frequently.
4.7.2 Methods of Using LIBDECOMP.COM
You can use the LIBDECOMP.COM procedure to decompress libraries in three ways:
The following three sections describe each method.
Note: Before you use the LIBDECOMP.COM
procedure, be sure you are logged in to the SYSTEM account.
4.7.3 Responding to LIBDECOMP.COM Prompts
If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure, do the following:
$ @SYS$UPDATE:LIBDECOMP.COM
OpenVMS Library Decompression Utility
1 HELPLIB.HLB 14 NCPHELP.HLB 27 PHONEHELP.HLB
2 STARLET.OLB 15 SDA.HLB 28 LIB.MLB
3 ACLEDT.HLB 16 SHWCLHELP.HLB 29 STARLET.MLB
4 ANLRMSHLP.HLB 17 SYSGEN.HLB 30 STARLETSD.TLB
5 DBG$HELP.HLB 18 ANALAUDIT$HELP.HLB 31 SYS$STARLET_C.TLB
6 DBG$UIHELP.HLB 19 SYSMANHELP.HLB 32 ERFLIB.TLB
7 DISKQUOTA.HLB 20 TFF$TFUHELP.HLB 33 SYS$LIB_C.TLB
8 EDFHLP.HLB 21 EXCHNGHLP.HLB 34 VAXCCURSE.OLB
9 INSTALHLP.HLB 22 TPUHELP.HLB 35 VAXCRTL.OLB
10 LATCP$HELP.HLB 23 EVE$HELP.HLB 36 VAXCRTLD.OLB
11 MAILHELP.HLB 24 EVE$KEYHELP.HLB 37 VAXCRTLT.OLB
12 MNRHELP.HLB 25 UAFHELP.HLB 38 IMAGELIB.OLB
13 EDTHELP.HLB 26 TECO.HLB
39 VMS$VOLATILE_PRIVATE_INTERFACES.OLB
40 FMG_HELP_FILE__AMERICAN_ENGLISH.HLB
A ALL libraries to be decompressed
E EXIT this procedure
* Enter letter or number(s) of libraries to be decompressed
(Separate multiple entries with a comma):
You can execute LIBDECOMP.COM interactively to decompress up to eight libraries at a time by listing the names of the libraries you want to decompress as parameters on the command line.
Be sure to separate the library names with commas and do not include the file extensions. For example, to decompress VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB interactively, enter the following command:
$ @SYS$UPDATE:LIBDECOMP VAXCRTL, DISKQUOTA, LIB
4.7.5 Using LIBDECOMP.COM in Batch
You can also execute LIBDECOMP.COM in batch mode to decompress up to
eight libraries at a time by listing the names of the libraries you
want to decompress as parameters on a command line that includes the
SUBMIT command.
Be sure to separate the library names with commas and do not include the file extensions. For example, to decompress VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB as a batch job, enter the following command:
$ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)- _$ SYS$UPDATE:LIBDECOMP
Note: When you enter the command for a batch
job, be sure you enclose the list of library names within parentheses.
4.8 Adding and Removing Operating System Files
If you decide after the installation to change which OpenVMS Alpha operating system files you want installed on your system, you can use the menu system contained on the OpenVMS Alpha operating system CD--ROM to add or remove files.
Note that you can obtain information about individual system files by
entering HELP SYSTEM_FILES at the dollar sign prompt ($).
4.8.1 How to Add and Remove Files
To add or remove operating system files:
Following is a sample menu display:
Please choose one of the following:
1) Install or upgrade OpenVMS Alpha Version V7.1
2) Display products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Execute DCL commands and procedures
8) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1
***********************************************************
.
.
.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE]
.
.
.
Version V7.1 of the OpenVMS operating system is already installed
on the target disk. You may choose one of the following actions:
o Reconfigure the OpenVMS operating system.
This action will allow you to change your choices about which
options you included when the operating system was installed.
Changes you make will cause options to be added or removed.
o Reinstall the OpenVMS operating system.
This action may be appropriate if you suspect that some of the
operating system files have become corrupted.
Either of these choices will allow you to change your choices for
the operating system options you included when the OpenVMS operating
system was installed or upgraded, including your choices for the DECnet
and DECwindows support that is part of the OpenVMS operating system.
If you want to install, reconfigure or remove the DECwindows Motif
graphical user interface or any of the Digital network products, you
must select options 3, 5 or 6 from the main menu.
Do you want to Reconfigure the OpenVMS operating system? (Yes/No) yes
The following product has been selected:
DEC AXPVMS VMS V7.1
Do you want to continue? [YES]
*** DEC AXPVMS VMS V7.1: OpenVMS Operating System
COPYRIGHT (c) 11-NOV-1996 -- All rights reserved
Digital Equipment Corporation
Do you want all the default values for this product? [YES]
Do you want to view the values? [NO]
Execution phase starting ...
The following product will be reconfigured:
DEC AXPVMS VMS V7.1
Portion done: 0%...10%...20%...30%...40%...50%...60%...80%...90%...100%
The following product has been reconfigured:
DEC AXPVMS VMS V7.1
.
.
.
If you installed the OpenVMS Management Station software on your system (either by accepting all default values or by selecting the component manually during the installation procedure), you must perform several tasks on your OpenVMS Alpha system and your PC before you can use OpenVMS Management Station. These tasks include the following:
For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, see Appendix E.
Note
Note that after you complete the tasks described in Appendix E, which include transferring the client software files from your system to two floppy diskettes, you can then remove those files from your system to save disk space. (Use the PRODUCT RECONFIGURE command rather than a delete operation. See OpenVMS System Management Utilities Reference Manual: M--Z for complete information about using the PRODUCT command.)
You can use the menu system included on the operating system CD--ROM to install certain layered products with the POLYCENTER Software Installation utility. If you did not install those layered products previously during the installation procedure, you can do so using the following procedure.
Note: To use this procedure, the target system must have the exact same version of the OpenVMS Alpha operating system as the CD--ROM. If you need to install layered products on a target system that has a different version of the operating system, use the alternate procedure described in the next section.
If the layered product that you want to install is not listed in the display, see the documentation you received with that layered product for installation information.
For additional information about installing layered products, see the OpenVMS System Manager's Manual.
Be sure you back up the system disk after you install all your layered
products.
4.10.1 Alternate Procedure
Following is another method for installing layered products from the OpenVMS Alpha operating system CD--ROM:
$ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT]
$ @SYS$UPDATE:VMSINSTAL * Where will the distribution volumes be mounted: DKB400:[UCX032.KIT]
$ PRODUCT INSTALL POSIX /SOURCE=DKB400:[POSIX020.KIT]
If you installed the Digital TCP/IP Services for OpenVMS software during the installation or if you choose to install it now as a layered product, note that you must also install the mandatory security update kit included with this release.
The Digital TCP/IP Kit and the mandatory Security Update Kit are available in the following directory on the OpenVMS Alpha CD-ROM:
[TCPIP_ALPHA_041]
If you choose to install the Digital TCP/IP Services for OpenVMS
software, you must install both kits.
4.10.3 DECevent
In OpenVMS Alpha Version 7.0 and earlier releases of OpenVMS Alpha, the DECevent DCL command DIAGNOSE was defined during the operating system installation procedure.
Beginning with OpenVMS Alpha Version 7.1, the definition of the DIAGNOSE command during installation is disabled. To enable the DIAGNOSE command in OpenVMS Version 7.1, the DECevent kit provided on the OpenVMS Alpha Version 7.1 CD--ROM must be installed following the installation of OpenVMS Alpha Version 7.1. For information about the location of the DECevent kit, see the Guide to OpenVMS Version 7.1 CD--ROMS.
If the DECevent kit provided on the OpenVMS Alpha CD--ROM is not installed after you install the operating system, users attempting to use the DIAGNOSE command will receive the following system message:
$ DIAGNOSE [params] %DIA-E-NO1HOME, DIAGNOSE functions not available on this system %DIA-I-GETKIT, install DECevent for access to DIAGNOSE $
The OpenVMS Alpha Version 7.1 operating system CD--ROM also includes a
Monitoring Performance History (MPH) kit located in the [MPH]
directory. See the OpenVMS Version 7.1 Release Notes for more information about installing
and using this optional software.
4.11 Backing Up the Customized System Disk
After you have customized the OpenVMS Alpha operating system to your
satisfaction and installed your layered products, protect your work by
making a backup copy of the system disk.
4.11.1 How to Back Up the Customized System Disk
To back up the system disk:
For complete information about backup operations, including a
description of an alternate method that does not require booting from
the operating system CD--ROM, see Appendix B.
4.12 Configuring a Multihead System
A multihead configuration consists of a single workstation (such as a DEC 3000 Alpha Model 500 system) that supports multiple graphics options. A graphics option consists of a graphics controller and a graphics display interface (monitor).
Your system can be automatically configured for multihead use if you
rename the private server setup file from a template file type to a
command procedure file type. The DECwindows Motif for OpenVMS Alpha
server loads this command procedure on startup or restart. This file
always configures the console as the primary head, or screen 0. The
firmware always selects the lowest device found in the system (that is,
the device with the lowest TURBOchannel slot address) as the console
device.
4.12.1 How to Set Up the System
To set up your system for multihead support:
$ RENAME SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE _To: SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
$ @SYS$STARTUP:DECW$STARTUP RESTART
See the most recent version of the DECwindows Motif for OpenVMS
Installation Guide and Managing DECwindows Motif for OpenVMS Systems for more information about
customizing your DECwindows environment using the
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file.
4.13 Running AUTOGEN
When you installed the operating system, the system executed the
AUTOGEN.COM procedure to set the values of system parameters and the
sizes of the page, swap, and dump files according to the system
configuration. As a postinstallation procedure, you need to run the
AUTOGEN.COM procedure again to properly tune the system.
4.13.1 When to Run AUTOGEN
Run AUTOGEN as follows:
Based on your examination of AGEN$PARAMS.REPORT, you might need to modify parameter values in MODPARAMS.DAT. If so, note the following:
For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager's Manual.
6486P003.HTM OSSG Documentation 6-DEC-1996 10:35:11.42
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.