Document revision date: 19 July 1999

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

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:

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 reconfigure/reinstall options.

The following is a sample reconfigure operation:

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.

8.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 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:

• 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

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

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, 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 8.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.

8.10.1 Alternate Procedure

The 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:[LP.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. The following is an example of the PRODUCT INSTALL command:

   $ PRODUCT INSTALL name /SOURCE=DKB400:[name.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 upgrade to 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

8.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.

8.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.

8.12 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.

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.

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

Although AUTOGEN runs automatically at the end of the upgrade procedure, Compaq recommends that you run AUTOGEN periodically after you perform an upgrade.

After 24 hours of operation, run AUTOGEN in FEEDBACK mode and reboot the system. Run AUTOGEN in this way again two workdays later.

AUTOGEN sets the values of system parameters and the sizes of the page and swap files according to the system's work load. Compaq 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.

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

8.15 Postupgrade Checklist

Use the following checklist to make sure you have performed all the necessary tasks:

• In a volume shadowing environment, reform the shadow set.
• Register new licenses.
• Examine AUTOGEN output stored in the file AGEN$PARAMS.REPORT.
• Examine MODPARAMS.DAT.
• Examine the command procedure templates supplied with the OpenVMS Alpha Version 7.2 operating system.
• Decompress the system libraries using LIBDECOMP.COM.
• Run the User Environment Test Package (UETP) to test the system (described in the OpenVMS System Manager's Manual).
• 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, including DECwindows (if necessary).
• Back up the customized system disk.
• Reboot each system that boots from the upgraded system disk (for a rolling upgrade in an OpenVMS Cluster environment).
• Run AUTOGEN.

This appendix contains the following information:

• Booting operations, including the following:
  • Booting the operating system CD-ROM, locally and from an InfoServer system
  • Booting manually from the system disk
  • Performing a conversational boot
  • Booting with minimum startup
  • Booting with the XDelta utility (XDELTA)
  • Booting from a different directory
  • Booting with a PMAZB or PMAZC TURBOchannel adapter
  • Booting over the network with an alternate TURBOchannel adapter
  • Booting in an emergency
• Set, Show, and Writeboot operations, including the following:
  • Setting the system for automatic booting
  • Setting and showing boot devices
  • Setting boot parameters
  • Using the Writeboot utility
• Halt and shutdown operations
• Troubleshooting procedures

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:

1. Insert the operating system CD-ROM into the local CD-ROM drive.
2. At the console prompt (>>>), enter the SHOW DEVICE command so you can identify the name of the CD-ROM drive (for example, DKA400:)
3. Enter the boot command in the following format:

   BOOT -FLAGS 0,0 source-drive

   
   Substitute the device name of the CD-ROM drive (as listed in the SHOW DEVICE display) for source-drive.
   For example, if the SHOW DEVICE display lists the device name of your CD-ROM drive as DKA400, enter the following command and press the Return key:

   >>> BOOT -FLAGS 0,0 DKA400

After you boot, the system displays a menu from which you can choose options to perform the following tasks:

• Install or upgrade the operating system using the POLYCENTER Software Installation utility.
• Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk.
• Shut down the system.

To boot the operating system CD-ROM using the InfoServer, do the following:

1. At the console prompt, enter the following command:

   >>> B -FLAGS 0,0 -FILE APB_072 lan-device-name

   
   Note the following conventions:

   • APB_072 is the file name of the APB program used for the initial system load (ISL) boot program.
   • lan-device-name is the name of the local area network (LAN) device identified with your computer. For information about the LAN devices your system supports, refer to the following table. For additional information, see the hardware manuals that you received with your Alpha computer and the OpenVMS Software Product Description.

   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 1200 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
   Digital Personal Workstation (DPWS) series	EWA0	FWA0

   Note If you are using a DEC 3000 or 4000 series system, note the following: On DEC 3000 series systems, you can boot through the InfoServer with an Ethernet PMAD device or FDDI DEFTA device by specifying the device name as "n/ESA0". The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8 in Appendix A. On DEC 4000 series, you must specify the ISL file name in uppercase (APB_072).

2. The InfoServer ISL program then displays the following menu:

   Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value:

3. Respond to the prompts as follows, pressing the Return key after each entry:
   1. Enter 3 for the function ID.
   2. Enter 2 for the option ID.
   3. Enter the service name (ALPHA072).
   
   A sample display follows:

   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: ALPHA072[Return]

After you boot, the system displays a menu from which you can choose options to perform the following tasks:

• Install or upgrade the operating system using the POLYCENTER Software Installation utility.
• Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk.
• Shut down the system.

	privacy and legal statement
6522PRO_010.HTML