Document revision date: 30 March 2001

## OpenVMS Alpha Version 7.3
Upgrade and Installation Manual

Previous | Contents | Index

## D.4 Defining TCP/IP Nodes

Your hosts file or name server must be able to resolve the IP name or address of all primary-server systems. If you can successfully ping the primary-server systems from your PC, then this condition is met.

## D.5 Uninstalling Version 2.1 of the OpenVMS Management Station Client

Version 3.0 of the OpenVMS Management Station client is not dependent on Version 2.1 and does not share any files with this prior version. After installing the Version 3.0 client, you can uninstall the Version 2.1 client software.

## D.6 Uninstalling OpenVMS Management Station

If you need to uninstall the OpenVMS Management Station client software, make sure you first exit OpenVMS Management Station. The uninstallation fails if OpenVMS Management Station is currently running.

If you run the OpenVMS Management Station Help, the following files might be created:

- VMSMGMT.FTS
- VMSMGMT.GID
- VMSPRINT.FTS
- VMSPRINT.GID
- VMSSCOPE.FTS
- VMSSCOPE.GID
- VMSSTORE.FTS
- VMSSTORE.GID
- VMSACNT.FTS
- VMSACNT.GID

The OpenVMS Management Station Uninstall program does not delete these files. To complete the uninstall:

1. Delete these files
2. Delete the OpenVMS Management Station directory

Note that the OpenVMS Management Station Uninstall program does not uninstall the Microsoft Management Console (MMC) support files.

## D.7 Getting Started with OpenVMS Management Station

All information about getting started, setting up, and using OpenVMS Management Station is contained in online help and the OpenVMS Management Station Overview and Release Notes.

## Appendix E
Removing the Compaq OpenVMS Alpha Operating System

You can remove the Compaq OpenVMS Alpha operating system from your disk in the following ways:

- If the disk contains a small number of user files, copy those user files elsewhere and then reinitialize the disk.
- If the disk contains many user files, use the PRODUCT REMOVE command to remove an obsolete or extra copy of the Compaq OpenVMS Alpha operating system without removing any of the user files. Note that you must also delete or archive certain operating system files that the PRODUCT REMOVE command cannot delete.

Follow these steps to remove Compaq OpenVMS Alpha operating system files:

1. If your system disk has multiple system-specific roots, boot the system and execute SYS$MANAGER:CLUSTER_CONFIG.COM to remove all roots except the one from which you are booted.
2. Shut down and boot from the distribution CD-ROM or from a system disk other than the one from which Compaq OpenVMS Alpha is being removed. Then do one of the following:
   - If Compaq OpenVMS Alpha is not running from the distribution CD-ROM, log in to a privileged account.
   - If Compaq OpenVMS Alpha is running from the distribution CD-ROM, choose the option to execute DCL commands.
3. Enter the following DCL commands:

       $ DEFINE/NOLOG PCSI$SYSDEVICE target-disk
       $ DEFINE/NOLOG PCSI$SPECIFIC target-disk:[SYSx.]
       $ DEFINE/NOLOG PCSI$DESTINATION target-disk:[VMS$COMMON]
       $ PRODUCT REMOVE VMS /REMOTE

   where:
   - target-disk is the device name of the disk from which OpenVMS Alpha is being removed
   - SYSx is the root number that you did not remove in step 1
4. If the disk also contains layered products that were installed using the POLYCENTER Software Installation utility, Compaq recommends that you remove them as well. Remove any layered products before using the PRODUCT REMOVE VMS command.
   Use the following command to remove all the products at once. Select the layered products you want to remove from the menu.

       $ PRODUCT REMOVE * /REMOTE

   Use the following commands to remove individual products:

       $ PRODUCT SHOW PRODUCT/REMOTE
       $ PRODUCT REMOVE product-name /REMOTE

5. Because the PRODUCT REMOVE command does not delete certain files, review the target disk to determine if you want to delete, move, or archive the operating system files that still remain on the disk.
   Following are lists of the files that the PRODUCT REMOVE command does not delete:
   - In target-disk:[SYS*.SYSEXE], where * is 0 or the hexadecimal number of any additional OpenVMS Cluster roots on the target disk:

     > ALPHAVMSSYS.PAR
     > MODPARAMS.DAT
     > PAGEFILE.SYS
     > SWAPFILE.SYS

   - In target-disk:[VMS$COMMON.SYSEXE]:

     > LMF$LICENSE.LDB
     > PCSI$FILE_SYSTEM.PCSI$DATABASE
     > PCSI$PROCESSOR.PCSI$DATABASE
     > PCSI$ROOT.PCSI$DATABASE
     > RIGHTSLIST.DAT
     > SYSUAF.DAT

   As you examine the preceding lists of files, you may want to archive, rather than delete, the following files:

   > ALPHAVMSSYS.PAR
   > MODPARAMS.DAT
   > LMF$LICENSE.LDB
   > RIGHTSLIST.DAT
   > SYSUAF.DAT

   Also, if you previously removed layered products, there may be additional files created by the layered products that you may want to delete, move, or archive.
6. Review the target disk for the directory structures [VMS$COMMON...] and [SYSx...] that remain after you remove the Compaq OpenVMS Alpha operating system. You may want to delete these directories.
   Note that the directories [SYSx]SYSCOMMON.DIR (in all [SYSx]) are aliases for the file [000000]VMS$COMMON.DIR. DO NOT DELETE THESE SYSCOMMON.DIR files. Instead, use SET FILE /REMOVE as follows:

       $SET FILE /REMOVE [SYS*]SYSCOMMON.DIR

   After you have executed this command and deleted, moved or archived all the files in [VMS$COMMON...] you can delete [000000]VMS$COMMON.DIR. You can then proceed to delete, move or archive the files in each [SYSx] directory.

## Glossary

This glossary defines key terms in the context of an Compaq OpenVMS Alpha computing environment.

boot, bootstrap: The process of loading system software into a processor's main memory. This guide uses the term boot to refer to this process.

boot server: An Alpha computer that is part of a local area OpenVMS Cluster. The boot server is a combination of a MOP server and a disk server for the satellite system disk. See also satellite node.

CI only OpenVMS Cluster: A computer system consisting of a number of Alpha computers. It uses only the computer interconnect, or CI, to communicate with other Alpha computers in the cluster. These computers share a single file system.

CI: A type of I/O subsystem. It links computers to each other and to HSx devices (for example, an HSC or HSD).

device name: The name used to identify a device on the system. A device name indicates the device code, controller designation, and unit number.

disk server: A computer that is part of a local area OpenVMS Cluster. This computer provides an access path to CI, DSSI, and locally connected disks for other computers that do not have a direct connection.

HSx device: A self-contained, intelligent, mass storage subsystem (for example, an HSC or HSD) that lets computers in an OpenVMS Cluster environment share disks.

HSx drive: Any disk or tape drive connected to an HSx device (for example, an HSC or HSD). A system disk on an HSx drive can be shared by several computers in an OpenVMS Cluster environment.

InfoServer: A general-purpose disk storage server that allows you to use the operating system CD-ROM to install the operating system on remote client systems connected to the same local area network (LAN).

local area OpenVMS Cluster: A configuration consisting of one or more computers that act as a MOP server and disk server, and a number of low-end computers that act as satellite nodes. The local area network (LAN) connects all of the computers. These computers share a single file system.

local drive: A drive, such as an RRD42 CD-ROM drive, that is connected directly to an Alpha computer. If you have a standalone Alpha computer, it is likely that all drives connected to the system are local drives.

media: Any packaging agent capable of storing computer software (for example, CD-ROMs, magnetic tapes, floppy diskettes, disk packs, and tape cartridges).

mixed interconnect OpenVMS Cluster: A computer system consisting of a number of computers. It uses CI, Ethernet, and DSSI adapters to communicate with other computers in the cluster.

MOP server: A computer system running DECnet software that downline loads OpenVMS Cluster satellites using the DECnet maintenance operations protocol.

OpenVMS Cluster environment: A computer system consisting of a number of Alpha and VAX computers. There are four types of OpenVMS Cluster environments: CI only, DSSI only, local area, and mixed-interconnect.

satellite node: A computer that is part of a local area OpenVMS Cluster. A satellite node is downline loaded from a MOP server and then boots remotely from the system disk served by a disk server in the local area OpenVMS Cluster. See also boot server, disk server, MOP server.

scratch disk: A blank disk or a disk with files you no longer need.

source drive: The drive that holds the distribution kit during an upgrade or installation, or the drive from which you restore files to a target disk.

standalone system: A computer system with only one Alpha computer.

system disk: The disk that contains or will contain the Compaq OpenVMS Alpha operating system.

target drive: The drive that holds the system disk during an upgrade or installation, or the drive you designate when backing up the system disk.

UETP (User Environment Test Package): A software package that tests all the standard peripheral devices on your system, various commands and operating system functions, the system's multiuser capability, DECnet software, and the OpenVMS Cluster environment.

Index | Contents

| privacy and legal statement |
6629PRO_016.HTML