Document revision date: 19 July 1999

You can use the LIBDECOMP.COM procedure to decompress libraries in three ways:

• Entering a command and responding to prompts from the procedure
• Entering an interactive command
• Entering a batch command

The following sections describe each method.

If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure, do the following:

1. Enter the following command and then press the Return key:

   $ @SYS$UPDATE:LIBDECOMP.COM

   
   The following information is displayed:

   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 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):

2. Enter the appropriate letter or the numbers of the libraries you want to decompress. To decompress all libraries, the process takes approximately one-half hour.

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

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.

To add or remove operating system files:

1. Mount and boot the OpenVMS Alpha operating system CD-ROM.
2. Choose option 1 from the menu.
3. Choose the PRESERVE option.
4. Enter the name of the device that contains the system disk and answer the questions.
5. After you answer the question "Do you want detailed descriptions?," information regarding reconfiguring or reinstalling is displayed. Read the instructions, then choose the desired entry from the menu of options.

The following is a sample display:

Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 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.2 of the OpenVMS operating system is already installed on the target disk. You may choose one of the following actions: o Reconfigure the OpenVMS platform. This action will allow you to change your selections of which of the windowing and network products you included with your OpenVMS operating system installation. o Reconfigure the OpenVMS operating system. This action will allow you to change your choices about which options you included for the OpenVMS operating system. o Reinstall the OpenVMS operating system. This action will cause ALL operating system files to be replaced. You can also change your choices about which options you included for the OpenVMS operating system. Reinstall will take longer than Reconfigure. Reinstall may be appropriate if you suspect that files in the operating system, or in the windowing and network products have become corrupted. If you want to reinstall any of the windowing and network products, choose "Install or upgrade layered products and patches" (option 3) from the main menu. If you want to change your choices about which options you included for any of the windowing and network products, choose "Reconfigure installed products" (option 5) from the main menu. Please choose one of the following: 1) Reconfigure the OpenVMS platform. 2) Reconfigure the OpenVMS operating system. 3) Reinstall the OpenVMS operating system. 4) Return to the Main Menu (abort the upgrade/installation). Enter choice or ? for help: (1/2/3/4/?) 2 The following product has been selected: DEC AXPVMS VMS V7.2 Operating System Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS VMS V7.2: OpenVMS Operating System COPYRIGHT (c) 12-SEP-1998 -- All rights reserved Compaq Computer Corporation Do you want the defaults for all options? [YES]

Answer No to this question, and select the options you want as described in Section 3.5.2. A list of components is provided in Section 3.5.3. After you respond to the prompts, the display continues and the installation procedure completes as described in Section 3.5.4. The following is a continuation of the sample display:

Do you want to review the options? [NO] Execution phase starting ... The following product will be reconfigured: DEC AXPVMS VMS V7.2 Portion done: 0%...10%...20%...30%...40%...50%...60%...80%...90%...100% The following product has been reconfigured: DEC AXPVMS VMS V7.2 . . .

For detailed instructions on how to remove the OpenVMS Alpha operating system from your disk, see Appendix E.

4.9 Preparing to Use OpenVMS Management Station

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:

• Editing system files
• Starting OpenVMS Management Station on other nodes
• Verifying that you have the proper memory, disk space, media, and the required software to install and run OpenVMS Management Station on your PC
• Installing the client software on your PC
• Defining DECnet nodes

For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, see Appendix D.

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. To install layered products that require VMSINSTAL, see Section 4.10.1.

1. Shut down the system (described in Appendix A).
2. Boot the operating system CD-ROM (locally or from the InfoServer).
3. Choose option 2 from the menu to view which layered products can be installed using the POLYCENTER Software Installation utility.
4. Choose option 3 from the menu to install the layered products.
5. Shut down the system by selecting option 8 from the menu.
6. Boot from the system disk.

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:

1. From your running OpenVMS system (the target system disk), mount the OpenVMS Alpha operating system CD-ROM.
2. Locate the directories and files containing the available layered products by entering the following command (where, in the example, DKA400: is the device name of the CD-ROM):

   $ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT]

   
   You can use the PRODUCT FIND command to locate kits that are installed using the POLYCENTER Software Installation utility. For example:

   $ PRODUCT FIND * /SOURCE=DKA400:[*.KIT]

3. To install layered products that require VMSINSTAL (indicated in the directories by save-set file names with file types of .A, .B, and so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the CD-ROM device and directory. For example:

   $ @SYS$UPDATE:VMSINSTAL * Where will the distribution volumes be mounted: DKB400:[UCX032.KIT]

4. To install layered products that require the POLYCENTER Software Installation utility (indicated in the directories by file names with file types of .PCSI or .PCSI$DESCRIPTION), use the PRODUCT INSTALL command to specify the CD-ROM device name and directory. Following is an example of the PRODUCT INSTALL command:

   $ PRODUCT INSTALL POSIX /SOURCE=DKB400:[POSIX020.KIT]

When you install OpenVMS Alpha Version 7.2, the DIAGNOSE command is disabled. To enable the DIAGNOSE command, you must install the DECevent kit provided on the OpenVMS Alpha Version 7.2 CD-ROM following the installation of OpenVMS Alpha Version 7.2. The DECevent kit is located in the directory [DECEVENT_0252.KIT] on the CD-ROM.

If the DECevent kit provided on the OpenVMS Alpha CD-ROM is not installed after the operating system, users attempting to use the DIAGNOSE command will receive the following system message:

$ DIAGNOSE [params] %DIA-E-NOINSTAL, DIAGNOSE has not been installed on this system

4.10.3 Monitoring Performance History

The OpenVMS Alpha Version 7.2 operating system CD-ROM also includes a Monitoring Performance History (MPH) kit located in the [MPH] directory. See the OpenVMS Version 7.2 Release Notes for more information about installing and using this optional software.

4.11 Installing DIGITAL OpenVMS Debugger Clients on a PC

The DIGITAL OpenVMS Debugger Version 7.2 includes a client/server interface. The debug server runs on the OpenVMS operating system; there are debug clients that run on OpenVMS, Microsoft Windows 95, and Microsoft Windows NT. There is no separate installation procedure for the components that run on the OpenVMS operating system. They are installed when you install the operating system. This section describes the procedure for installing debug clients on a PC.

The following table shows which client kit to use for each PC configuration:

CPU	Operating System	Client Kit
Intel	Microsoft Windows 95	[DEBUG_CLIENTS010.KIT]DEBUGX86010.EXE
Intel	Microsoft Windows NT	[DEBUG_CLIENTS010.KIT]DEBUGX86010.EXE
Alpha	Microsoft Windows NT	[DEBUG_CLIENTS010.KIT]DEBUGALPHA010.EXE

The client kits are self-extracting .EXE files. To make these clients available to PC users, copy these files from the distribution media to a suitable PATHWORKS share, FTP server, or other device available to the PC.

Once the appropriate executable file has been transferred to the PC, you can run the file to install the debug client on the PC. The InstallShield installation procedure guides you through the installation.

By default, the debug client is installed in the \Programs\OpenVMS Debugger directory. You can also click on the Browse button to select an alternate directory.

You can choose one of the following installation options:

Install Option	Details
Typical	Debug Client and the OpenVMS Debugger Manual in HTML format
Compact	Debug Client only
Custom	Choice of Debug Client and/or the OpenVMS Debugger Manual in HTML format

The Typical installation option creates an OpenVMS Debugger program folder that contains shortcuts to the following items:

• Debug client
• Debug client Help file
• The OpenVMS Debugger Manual in HTML format
• A Readme file
• An Uninstall procedure

For information about using the OpenVMS Debugger, see the OpenVMS Debugger Manual.

4.12 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 standalone backup copy of 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.

To back up the system disk:

1. Shut down the system (described in Appendix A).
2. Boot the operating system CD-ROM (locally or from the InfoServer).
3. Use the menu system to enter the DCL environment (option 7).
4. Mount the system disk and the target device on which you will make the backup copy.
5. Enter backup commands to back up the system disk to the target device.
6. Log out from the DCL environment.
7. Shut down the system by selecting option 8 from the menu.
8. Boot from the system disk.

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.

To set up your system for multihead support:

1. After installing the DECwindows Motif for OpenVMS Alpha software on your system, log in to your system.
2. Rename the private server setup file by entering the following command:

   $ RENAME SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE _To: SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM

3. Restart the DECwindows server by entering the following command:

   $ @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.14 Running AUTOGEN

When you installed the OpenVMS Alpha 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 should run the AUTOGEN.COM procedure again to properly tune the system.

Run AUTOGEN as follows:

1. After 24 hours of operation, run AUTOGEN in feedback mode and reboot the system.
2. Run AUTOGEN again in feedback mode two workdays later, and then reboot the system.
3. Compaq recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis thereafter, and examine AGEN$PARAMS.REPORT to determine the need for additional changes.

Based on your examination of AGEN$PARAMS.REPORT, you might need to modify parameter values in MODPARAMS.DAT. If so, note the following:

• 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 that 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.

For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager's Manual.

4.15 Postinstallation Checklist

• Register your licenses if you did not do so during the installation procedure.
• Create accounts.
• Back up the system disk as a safeguard before customizing the system.
• Customize the system.
• Configure and start the DECnet for OpenVMS Alpha software.
• Run the User Environment Test Package (UETP) to test the system.
• Decompress the system libraries using LIBDECOMP.COM.
• Add and remove files.
• Prepare your OpenVMS Alpha system and your PC to run OpenVMS Management Station by following the procedures described in Appendix D.
• Install layered products.
• Back up the system disk after you have customized it and installed layered products.
• Configure your multihead system (if applicable).
• After the system has been running for at least 24 hours, run AUTOGEN to collect feedback information and modify the MODPARAMS.DAT file (if necessary).

	privacy and legal statement
6522PRO_005.HTML