![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
You can also use the LICENSE REGISTER command.
For information about registering licenses, see the following:
When AUTOGEN runs, it writes informational and, if necessary, warning
messages to the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You should examine
the contents of this report file.
8.3.1 Interpreting the Report File
To view AGEN$PARAMS.REPORT on your screen, enter the following command and press the Return key:
$ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT
(You can also print this file or examine it using the EDIT/READ_ONLY command.)
For more information on AGEN$PARAMS.REPORT, see the OpenVMS System Manager's Manual.
If the report includes a message similar to the following, you might need to modify the size of the page, swap, or dump file:
%AUTOGEN-W-DSKSPC, The disk on which DKA0:[SYS0.SYSEXE]PAGEFILE.SYS
resides would be over 95% full if it were modified to hold 20000
blocks.
For more information about modifying the sizes of the page, swap, and
dump files, see the next section.
8.4 Modifying the System Parameters File
Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade procedure created
a new version of this file. The old version is named
SYS$SYSTEM:MODPARAMS.DAT_OLD. Modify the parameters in the new file as
necessary. The following two sections are examples of instances where
you need to modify parameters in MODPARAMS.DAT.
8.4.1 System File Sizes
AUTOGEN sets the following files at sizes appropriate for your system:
If you have special workloads or configurations, you can specify different sizes for these files by performing the following steps:
$ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES
$ @SYS$UPDATE:AUTOGEN GENPARAMS REBOOT
If you are upgrading an OpenVMS Cluster system, note the following:
The upgrade procedure retains the site-specific versions of the following files located in the [VMS$COMMON] directory:
[SYSMGR]LAT$SYSTARTUP.COM [SYSMGR]LOGIN.COM [SYSMGR]SYCONFIG.COM [SYSMGR]SYLOGICALS.COM [SYSMGR]SYLOGIN.COM [SYSMGR]SYPAGSWPFILES.COM [SYSMGR]SYSECURITY.COM [SYSMGR]SYSHUTDWN.COM [SYSMGR]SYSTARTUP_VMS.COM [SYSMGR]TFF$SYSTARTUP.COM [SYSMGR]WELCOME.TXT [SYS$STARTUP]ESS$LAST_STARTUP.DAT
The upgrade procedure provides new templates for some of these files
with the .TEMPLATE extension. The new templates might include features
that are not in your site-specific files. Check the templates against
your site-specific files and edit your files as necessary.
8.6 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.
8.6.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.
8.6.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.
8.6.3 Responding to LIBDECOMP.COM Prompts
If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure:
$ @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
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 extension. 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 type the command for a batch
job, be sure you enclose the list of library names within parentheses.
8.7 Testing the System with UETP
Run the User Environment Test Package (UETP) to verify that the upgrade completed correctly.
For instructions on running UETP, see the OpenVMS System Manager's Manual.
8.8 Adding and Removing Operating System Files
If you decide after the upgrade 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 ($).
The procedure is as follows:
Following is a sample reconfigure operation:
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-MAY-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 upgrade 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: 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.)
8.10 Installing Layered Products
Except in certain instances, you should not have to reinstall layered products that you had on your system prior to the upgrade. However, if you need to install layered products, follow these directions:
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 upgrade 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.
8.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.
8.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 upgrade procedure.
Beginning with OpenVMS Alpha Version 7.1, the definition of the DIAGNOSE command during upgrade 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 upgrade to 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 upgrade 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.
8.11 Backing Up the Customized System Disk
After you have upgraded and customized the OpenVMS Alpha operating
system to your satisfaction and installed layered products, protect
your work by making a backup copy of the system disk.
8.11.1 How to Back Up the Customized System Disk
To back up the system disk, use the following procedure:
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.
8.12 Rebooting Cluster Members
If you are performing a rolling upgrade in an OpenVMS Cluster environment and have completed all the postupgrade tasks required for your upgraded system disk, reboot each system that boots from that system disk.
For more information about booting your system, see Appendix A.
8.13 Running AUTOGEN
Although AUTOGEN runs automatically at the end of the upgrade
procedure, Digital recommends that you run AUTOGEN periodically after
you perform an upgrade. This section describes how often you should run
AUTOGEN and what it does.
8.13.1 Running After the Upgrade
After 24 hours of operation, run AUTOGEN in FEEDBACK mode and reboot
the system. Run AUTOGEN in this way again two workdays later.
8.13.2 Running Weekly
AUTOGEN sets the values of system parameters and the sizes of the page and swap files according to the system's work load. Digital recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis and examine AGEN$PARAMS.REPORT to determine the need for additional changes.
Hardcoded values in MODPARAMS.DAT should not hinder AUTOGEN's ability
to calculate feedback parameters. AUTOGEN generally does not reduce the
value of parameters that allocate resources; it considers current
parameter values to be minimum values, which means you do not have to
add MIN_* symbols to MODPARAMS.DAT. AUTOGEN does increase parameter
values according to its calculations unless you have specified explicit
or maximum values (by adding MAX_* symbols) in MODPARAMS.DAT.
8.13.3 For More Information
For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager's Manual.
8.14 Postupgrade Checklist
Use the following checklist to make sure you have performed all the
necessary tasks:
This appendix contains the following information:
The following sections describe different methods of booting your
system.
A.1.1 Booting the Operating System CD--ROM
If you need to boot the OpenVMS Alpha operating system CD--ROM, either
to perform an installation or upgrade or to perform related operations
such as mounting or backing up the system disk, follow the steps in the
following sections, depending on whether you are booting locally or
from the InfoServer.
A.1.1.1 Booting from the Local Drive
Boot from the local drive as follows:
BOOT -flags 0,0 source-drive
>>> BOOT -flags 0,0 DKA400
After you boot, the system displays a menu from which you can choose options to perform the following tasks:
To boot the operating system CD--ROM using the InfoServer, do the following:
>>> B -FL 0,0 -FI APB_061 lan-device-name
| Alpha Computer | Ethernet Device |
FDDI Device |
|---|---|---|
| ALPHAbook 1 | EOA0 | -- |
| AlphaServer 400 series | EWA0 | FWA0 |
| AlphaServer 1000 series | ERA0, EWA0 | FRA0 |
| AlphaServer 1000A series | EWA0 | FWA0 |
| AlphaServer 2000 series | ERA0, EWA0 | FRA0 |
| AlphaServer 2100, 2100A series | ERA0, EWA0 | FRA0 |
| AlphaServer 4100 series | EWA0 | FWA0 |
| AlphaServer 8200 series | EXA0, EWA0 | FXA0 |
| AlphaServer 8400 series | EXA0, EWA0 | FXA0 |
| AlphaStation 200 series | EWA0 | FWA0 |
| AlphaStation 400 series | EWA0 | FWA0 |
| AlphaStation 500 series | EWA0 | FWA0 |
| AlphaStation 600 series | ERA0, EWA0 | FWA0 |
| DEC 2000 series | ERA0 | -- |
| DEC 3000 series | ESA0 | "n/ESA0" |
| DEC 4000 series | EZA0 | -- |
| DEC 7000 series | EXA0 | FXA0 |
| DEC 10000 series | EXA0 | FXA0 |
>>> BOOT -FL 0,0 -start 0 -FI APB_F70 EZA0
Network Initial System Load Function
Version 1.1
FUNCTION FUNCTION
ID
1 - Display Menu
2 - Help
3 - Choose Service
4 - Select Options
5 - Stop
Enter a function ID value:
Enter a function ID value: 3[Return] OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2[Return] Enter a Known Service Name: ALPHAF70[Return]
6486P006.HTM OSSG Documentation 6-DEC-1996 10:35:16.35
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.