HP OpenVMS Systems Documentation
OpenVMS VAX Version 7.3
If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure, do the following:
OpenVMS Library Decompression Utility 1 HELPLIB.HLB 15 SDA.HLB 28 PHONEHELP.HLB 2 STARLET.OLB 16 SHWCLHELP.HLB 29 LIB.MLB 3 ACLEDT.HLB 17 SYSGEN.HLB 30 STARLET.MLB 4 ANLRMSHLP.HLB 18 ANALAUDIT$HELP.HLB 31 STARLETSD.TLB 5 DBG$HELP.HLB 19 SYSMANHELP.HLB 32 SYS$STARLET_C.TLB 6 DBG$UIHELP.HLB 20 TFF$TFUHELP.HLB 33 ERFLIB.TLB 7 DISKQUOTA.HLB 21 EXCHNGHLP.HLB 34 VAXCCURSE.OLB 8 EDFHLP.HLB 22 TPUHELP.HLB 35 VAXCRTL.OLB 9 INSTALHLP.HLB 23 EVE$HELP.HLB 36 VAXCRTLG.OLB 10 LATCP$HELP.HLB 24 EVE$KEYHELP.HLB 37 IMAGELIB.OLB 11 MAILHELP.HLB 25 UAFHELP.HLB 38 DECCCURSE.OLB 12 MNRHELP.HLB 26 TECO.HLB 39 DECCRTL.OLB 13 EDTHELP.HLB 27 PATCHHELP.HLB 40 DECCRTLG.OLB 14 NCPHELP.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. (You can decompress all the libraries by omitting the /PARAMETERS qualifier.)
Be sure you do not include the file extensions. For example, to decompress the VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB libraries 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 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
When you enter the command for a batch job, be sure you enclose the list of library names within parentheses.
To remove OpenVMS VAX operating system files from the system disk, use VMSTAILOR or DECW$TAILOR. For example, if you are not running DECnet software, use VMSTAILOR to remove the files associated with DECnet.
You cannot use VMSTAILOR to remove files installed on an alternate device from save set VMS073.E.
Back up your system disk and then use either the VMSINSTAL command procedure or the POLYCENTER Software Installation utility to install layered products on your system.
For additional information about installing layered products, refer to
the OpenVMS System Manager's Manual.
4.10 Backing Up the Customized System Disk
For complete information about backup operations, refer to the upgrade
and installation supplement for your VAX computer and the system
4.11 Running AUTOGEN
When you installed the OpenVMS VAX operating system, the system executed the AUTOGEN.COM procedure to set the values of system parameters and the sizes of the page and swap files according to the system's workload.
In many cases, AUTOGEN can improve system performance by using dynamic feedback information from the running system. As a postinstallation task, you should run the AUTOGEN.COM procedure again to properly tune the system.
Run AUTOGEN as follows:
For large memory systems such as the VAX 9000 computer, AUTOGEN's initial parameter calculations are conservative. To obtain parameter values that match your system workload, you can run AUTOGEN in feedback mode a number of times. For more information, refer to the upgrade and installation supplement for your computer.
After you run AUTOGEN following the first 24 hours of system operation
(step 1), review the checklist in Section 4.13 to confirm that you
have completed all the tasks described in this chapter.
4.12 Modifying Parameters
When AUTOGEN runs, it uses the parameter values in SYS$SYSTEM:MODPARAMS.DAT. Based on your examination of AGEN$PARAMS.REPORT, you might need to modify parameter values in MODPARAMS.DAT. If so, note that hardcoded values in MODPARAMS.DAT affect AUTOGEN's ability to calculate feedback parameters. For AUTOGEN to properly calculate minimum default values, you should replace the hardcoded values in MODPARAMS.DAT with MIN_ values. If you need to modify the parameter values calculated by AUTOGEN, you can use AUTOGEN to change the hardcoded values in MODPARAMS.DAT.
For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, refer to the OpenVMS System Manager's Manual.
4.13 Postinstallation Checklist
Use the following checklist to make sure you perform all the necessary
If you are an experienced system manager, you can use the checklist at the end of this chapter to complete the necessary preupgrade tasks.
If you are system manager with limited OpenVMS VAX experience, you
should read the entire chapter and then use the checklist to make sure
you have completed all the preupgrade tasks.
5.1 Cautions and Restrictions
This section provides important information that can affect the success
of your upgrade. If you attempt to upgrade your system without
following these cautions and restrictions, the upgrade could fail or
your upgraded system might not perform as expected.
5.1.1 License Requirements
To upgrade to OpenVMS VAX Version 7.3, you must have an appropriate license. Compaq's software licenses grant the right to use the current version of a product or any previous version of the product at the time of purchase. If you have an OpenVMS license prior to Version 7.3 and are not covered by a Software Product Services agreement, which includes the right to use new versions (RTNV), you must purchase an Update License before upgrading to OpenVMS VAX Version 7.3.
If you do not have an Update License, contact your Compaq account
representative to assist you in obtaining the correct Product
Authorization Key (PAK) needed to access the OpenVMS operating system.
5.1.2 DECset Version 11 Debugger
If you have the DECset Version 11 layered product installed on your system, you must remove the @DEBUG$STARTUP.COM command from the system startup procedure. The debugger shipped with OpenVMS VAX Version 7.3 is a superset of the debugger that was shipped with the DECset Version 11 software. Removing the @DEBUG$STARTUP.COM command will cause the debugger shipped with OpenVMS VAX Version 7.3 to be the default system debugger.
To remove the @DEBUG$STARTUP.COM command before you upgrade the operating system software, perform the following steps:
If you do not remove this command before you upgrade the operating system software, you must remove it after the upgrade, and you must deassign the logicals that were defined by DEBUG$STARTUP.COM by performing the following steps:
$ DEASSIGN/SYSTEM DEBUG $ DEASSIGN/SYSTEM DEBUGSHR $ DEASSIGN/SYSTEM DEBUGUISHR $ DEASSIGN/SYSTEM DBGTBKMSG $ DEASSIGN/SYSTEM DBG$HELP $ DEASSIGN/SYSTEM DBG$UIHELP $ DEASSIGN/SYSTEM DEBUGAPPCLASS $ DEASSIGN/SYSTEM VMSDEBUGUIL
The OpenVMS VAX Version 7.3 upgrade procedure provides new
files and directories in the directory [VMS$COMMON...]. If you had any
special protections and access control lists (ACLs) before the upgrade,
you need to reapply them to reestablish the security environment you
had previously. For more information about creating and maintaining a
secure environment, refer to the OpenVMS Guide to System Security.
5.1.4 Operator and Accounting Logs
The upgrade procedure deletes all the operator and accounting logs. To
save these files, move them to a user directory before you start the
5.1.5 Special Testing and Debugging Files
Before you perform an upgrade, remove or rename any special testing or debugging files that you might have in any of the SYS$SPECIFIC: or SYS$SYSROOT: directories. Files in these directories are used in place of the files in SYS$COMMON: directories.
As a minimum, you should check the following directories:
Because the upgrade procedure affects the SYS$COMMON: directories and
does not check or alter the contents of the SYS$SPECIFIC: or
SYS$SYSROOT: directories, any testing or debugging files that you have
in these directories remain there unchanged until you remove or rename
them. If you do not remove or rename these files, your system might
behave in an unpredictable manner.
5.1.6 Cluster Considerations
The following cautions apply when you are upgrading a cluster system:
If you move the OpenVMS VAX save sets from the distribution media to the system disk or some other disk before beginning the upgrade, the save sets must be in the  directory of the disk, or the upgrade will fail.
Do not attempt to use VMSINSTAL with OPTION G to transfer OpenVMS VAX
save sets to another media type; doing so produces an unusable system.
Instead, you can use the DCL command COPY to transfer save sets to
another media type.
5.1.8 System Disk Cautions
The following cautions apply to the system disk:
If you use your AUTOGEN feedback data, you should save this information
before rebooting the system with minimum startup to begin the upgrade.
For more information, see Section 5.3.
5.1.10 OpenVMS VAX Version Requirements
Before you can upgrade to OpenVMS VAX Version 7.3, your system must be running at least Version 6.1 of the OpenVMS VAX operating system. For example, you can upgrade a system disk to Version 7.3 of the OpenVMS VAX operating system from any of the following versions (or related hardware releases):
OpenVMS VAX Version 6.1
OpenVMS VAX Version 6.2
OpenVMS VAX Version 7.0
OpenVMS VAX Version 7.1
OpenVMS VAX Version 7.2
These minimum requirements do not apply to rolling upgrades. There are special considerations for rolling upgrades. See Section 6.1 for additional information.
If you want to use DECwindows software with OpenVMS VAX Version 7.3, you must be running Version 1.2-4 or higher of the DECwindows Motif for OpenVMS VAX layered product.
If you have a shared system dump file in SYS$COMMON:[SYSEXE], the
shared dump file cannot have the name SYSDUMP.DMP. If you have a shared
system dump file with this name, Compaq recommends that you rename it
5.1.13 Layered Products
The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures.
If a layered product is available yet exhibits unexpected behavior once
Version 7.3 of the OpenVMS VAX operating system is running,
check the OpenVMS Version 7.3 Release Notes for possible layered-product restrictions.
5.2 Preparing to Upgrade
Before you begin to upgrade the OpenVMS VAX operating system, be sure
you have all the required hardware and software components.
5.2.1 Hardware Components
Examine your hardware for the following:
VAX 8600, 8650
VAX 8200, 8250, 8300, 8350
Examine your software for the following:
After the upgrade is finished, AUTOGEN runs. If it finds valid feedback
data on your system, it tries to use AUTOGEN feedback.
5.3.1 Valid Feedback Data
Feedback data is produced by the SAVPARAMS phase of AUTOGEN and is stored in SYS$SYSTEM:AGEN$FEEDBACK.DAT. Valid feedback data is defined as follows:
If your feedback data is not valid, AUTOGEN will run without feedback
(all previous feedback-generated parameters will be replaced by the
AUTOGEN NOFEEDBACK calculations).
5.3.2 How to Test Feedback Data
To ensure that AUTOGEN feedback will run after the upgrade, do the following:
$ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES
$ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES