Document revision date: 30 March 2001
[Compaq] [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]
[OpenVMS documentation]

Installing Compaq Availability Manager Version 1.4

on Compaq OpenVMS Alpha Systems

and

Running DECamds and the Availability Manager

This document contains the following sections:

1 Preparing to Install

Note

The Availability Manager Version 1.4 kit for OpenVMS includes the Data Analyzer and Data Collector:
  • The Java Data Analyzer can be installed only on OpenVMS Alpha Versions 7.1, 7.1-2, 7.2, 7.2-1, and 7.2-1 variants.
  • The Data Collector can be installed on OpenVMS VAX and Alpha Versions 6.2, 7.1, 7.1-2, 7.2, 7.2-1, and 7.2-1 variants. It can also be installed on Alpha Version 7.0.

The following sections contain instructions for preparing to install DECamds and the Availability Manager on OpenVMS systems.

1.1 Installing Patch Kits

Before installing the Availability Manager, please check for any remedial kits that Java requires; these are documented at the Java website.

Install these remedial kits, even if they are listed as optional. For example, for OpenVMS Version 7.2-1, the VMS721_PTHREAD remedial kit is listed as optional; however, this kit is required for Availability Manager Version 1.4.

1.2 Downloading the Software

Follow these steps to download the software:

  1. Go to the Availability Manager web site home page:


    http://www.openvms.compaq.com/openvms/products/availman/index.html 
    

  2. Click Software Download.
  3. Complete the user survey, which allows you to proceed to the Download web page.
  4. Click one of the Availability Manager or DECamds executables, or both:


        Availability Manager - Alpha: vmsavailman014.pcsi-dcx_axpexe      
                             - VAX:   vmsavailman014.pcsi-dcx_vaxexe      
     
        DECamds              - Alpha: decamds073-axp.pcsi-dcx_axpexe 
                             - VAX:   decamds073-vax.pcsi-dcx_vaxexe 
     
    

  5. Save the executable to a device and directory of your choice.
  6. Run the executable and accept the default file name. The result will be:


        Availability Manager:  DEC-VMS-AVAIL_MAN-V14--1.PCSI 
     
        DECamds:               DEC-VMS-AMDS-V0703--1.PCSI  
     
    

2 Installing the Availability Manager

This section explains how to install the Availability Manager on OpenVMS systems and how to perform postinstallation tasks.

2.1 Reading the Release Notes

The Availability Manager Version 1.4 provides online release notes. Compaq strongly recommends that you read the release notes before you proceed with the installation. On OpenVMS systems, you can obtain a text version of the Availability Manager Version 1.4 Release Notes by setting the default to the directory where the kit resides. Then enter the following command at the DCL prompt:


$ PRODUCT EXTRACT/BASE=VMS RELEASE_NOTES AVAIL_MAN 

If you have not set the default to that directory, enter the following command line:


$ PRODUCT EXTRACT/BASE=VMS RELEASE_NOTES AVAIL_MAN/SOURCE=disk:[directory] 

where disk:[directory] refers to the disk and directory where the kit resides. The default file name is DEFAULT.PCSI$RELEASE_NOTES.

2.2 Installing Additional Software

This section pertains to the installation of the Availability Manager, not DECamds. It describes the following additional software that must be installed on your system:

2.3 Starting the Installation

Use the following procedure to start the installation:

Enter the DCL command PRODUCT INSTALL, followed by the name of one or more products. For example, to install the Availability Manager Version 1.4, enter the following command:


$ PRODUCT INSTALL/BASE=VMS AVAIL_MAN/SOURCE=device directory/HELP

where device and directory refer to the device and the directory, respectively, where the kit is located.

Note

You currently must install Availability Manager files in the PCSI default directory root.

For a description of the features you can request with the PRODUCT INSTALL command when starting an installation such as running the IVP, purging files, and configuring the installation, see the POLYCENTER Software Installation Utility User's Guide.

Installation Checks for Java

The installation checks whether the Java JDK has been installed on your system. If a version of Java that does not meet the version requirements stated in Section 2.2 has been installed, a message is displayed, and the installation ends.

With the previous version of the Availability Manager, you needed to edit the AMDS$AM_LOGICALS.COM file to point to the correct Java class files. You no longer need to edit this file when you install new versions of Java. The new version of the AMDS$STARTUP.COM file performs the following steps to find the correct Java class libraries:

  1. AMDS$STARTUP.COM checks for the CLASSPATH logical name definition in LNM$SYSTEM_TABLE.
  2. If the CLASSPATH logical name is in the table, CLASSPATH is used to obtain the version of the JDK classes zip file.
  3. If the CLASSPATH logical is not in the table, AMDS$STARTUP.COM looks for the SYS$MANAGER:JAVA$SETUP.COM file.
  4. If the SYS$MANAGER:JAVA$SETUP.COM file is found, AMDS$STARTUP.COM executes it and rechecks for the CLASSPATH logical in the LNM$PROCESS_TABLE. AMDS$STARTUP.COM then performs step 2 and exits.
  5. If the SYS$MANAGER:JAVA$SETUP.COM file is not found, AMDS$STARTUP.COM displays an error message and exits.
  6. If the CLASSPATH logical is not defined after execution of the JAVA$SETUP.COM file, AMDS$STARTUP.COM displays an error message and exits.

Completion of Installation

As the installation procedure progresses, the system displays a percentage message to indicate how much of the installation is done. For example:


Percent Done: 0%...40%...60%...70%...80%...90%...100% 

If you started the installation using the /LOG qualifier to the INSTALL command, the system displays details of the installation.

Note

When the installation is complete, you must reboot your system.

2.4 Stopping and Restarting the Installation

Use the following procedure to stop and restart the installation:

  1. To stop the procedure at any time, press Ctrl/Y.
  2. Enter the DCL command PRODUCT REMOVE to reverse any changes to the system that occurred during the partial installation. This deletes all files created up to that point and causes the installation procedure to exit.
  3. Go back to the beginning of the installation procedure to restart the installation.

2.5 Recovering from Errors

If the installation procedure fails for any reason, the following message is displayed:


     %POLYCENTER Software Installation utility 
     %INSTAL-E-INSFAIL, The installation of AVAIL_MAN has failed. 

An error during the installation can occur if one or more of the following conditions exist:

If you receive an error message beginning with %PCSI-E-INSTAL, refer to the DCL HELP/MESSAGE utility for POLYCENTER Software Installation information and a possible solution to the problem.

If the installation fails, you must restart the installation procedure. If the installation fails due to an IVP failure, contact a Compaq support representative.

2.6 Performing Postinstallation Tasks

After you install the Availability Manager Version 1.4, you need to perform several postinstallation steps, which are explained in the following sections.

2.6.1 Merging Customizations of Files

If the Availability Manager installation finds these files, it renames them as follows:
Original File Name Renamed to...
AMDS$AM_LAUNCH_BROWSER.COM AMDS$AM_LAUNCH_BROWSER.COM_OLD
AMDS$DRIVER_ACCESS.DAT AMDS$DRIVER_ACCESS.DAT_OLD
AMDS$AM_LOGICALS.COM AMDS$AM_LOGICALS.COM_OLD
AMDS$LOGICALS.COM AMDS$LOGICALS.COM_OLD
AMDS$AM_STARTUP.COM AMDS$AM_STARTUP.COM_OLD
AMDS$STARTUP.COM AMDS$STARTUP.COM_OLD

The installation then creates new versions of these files using the original file name. You must merge any customizations you have made to the files into the files provided by the installation.

You might find it helpful to use the DIFFERENCES utility to compare the new and old files.

2.6.2 Editing Additional Files

Following installation of the Availability Manager software, you need to edit one file, and you can optionally edit two additional files on each Data Collector node.

The following list indicates the steps to take on OpenVMS Alpha or VAX Data Collector nodes. The files in steps 1 and 2, which are optional steps, contain default values that are used if you do not supply values. Step 3 is mandatory.

  1. Optionally edit the following file to change passwords, which allow the node to be monitored by another node:


    SYS$MANAGER:AMDS$DRIVER_ACCESS.DAT 
    

  2. Optionally edit the following file to change the name of the group you want this node to belong to:


    AMDS$SYSTEM:AMDS$LOGICALS.COM 
    

  3. To start the Data Collector when the system boots, you must add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file:


    $ @SYS$STARTUP:AMDS$STARTUP START 
    

3 Running DECamds and the Availability Manager

This section discusses how to configure and start Data Collectors and Data Analyzers for both DECamds and the Availability Manager.

To install and run DECamds and the Availability Manager concurrently, you need to complete the steps shown in Table 1.

Table 1 Installing and Running DECamds and Availability Manager Concurrently
Step Description For information, see...
1 Install DECamds. See Section 1 for preparation instructions. For installation steps, see Appendix A of the DECamds User's Guide, which is available online at the url cited in the introduction to this document.
2 Install the Availability Manager. Section 1 through Section 2.6.1
3 Review the Availability Manager and DECamds configuration files. Section 3.1
4 Make postinstallation edits. Section 3.2
5 Use DCL commands to run DECamds and the Availability Manager. Section 3.3

3.1 Understanding Availability Manager and DECamds Configuration Files

The DECamds and Availability Manager products have several common files that the Data Collector (or Data Provider, in DECamds terms) uses. These two products also have several files that have similar functions. Files, directories, or logical names with the same or similar function have the prefix AMDS$ or AMDS$AM, representing DECamds or the Availability Manager, respectively.

The installation also uses this naming scheme to place files that are specific to either product. For example, the file that defines logical names for DECamds is:


    AMDS$SYSTEM:AMDS$LOGICALS.COM 

For the Availability Manager, this file is:


    AMDS$AM_SYSTEM:AMDS$LOGICALS.COM 

The names of files that the products have in common usually start with AMDS$.

3.1.1 Using Configuration Files

The following table shows the configuration files that the startup command procedure creates for the Availability Manager and for DECamds.
File Availability Manager DECamds
Installation directory SYS$COMMON:[AMDS$AM] SYS$COMMON:[AMDS]
Startup command procedure SYS$STARTUP:AMDS$STARTUP Same as Availability Manager
Driver file (contains passwords for DECamds V7.1 and earlier) n/a AMDS$SYSTEM:
AMDS$DRIVER_ACCESS.DAT
Driver file (contains passwords for DECamds V7.2 and later) SYS$MANAGER:
AMDS$DRIVER_ACCESS.DAT
Same as Availability Manager
Logical names command file (contains group names for DECamds V7.1 and earlier) n/a AMDS$SYSTEM:
AMDS$LOGICALS.COM
Logical names command file (contains group names for DECamds V7.2 and and later) SYS$MANAGER:
AMDS$LOGICALS.COM
Same as Availability Manager

3.1.2 Merging Files

To use Data Collector passwords as well as group names and other configuration data from DECamds Version 7.1 and earlier, you must merge versions of files:

3.2 Making Postinstallation Edits

After you install DECamds and the Availability Manager and you understand the configuration files for both products, make postinstallation file edits for Version 7.2 or 7.2-1 Alpha or VAX Data Collector nodes. Two of the file edits are optional, and one is required, as explained in the following list:

  1. Optionally, edit the following file to change passwords, which allow the node to be monitored by another node:


    SYS$MANAGER:AMDS$DRIVER_ACCESS.DAT 
    

  2. Optionally, edit the following file to change the name of the group you want this node to belong to:


    AMDS$MANAGER:AMDS$LOGICALS.COM 
    

  3. To start the Data Collector when the system boots, you must add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file:


    @SYS$STARTUP:AMDS$STARTUP START 
    

  4. Before running the application from a particular account, verify that the following two account settings are at least the minimum quotas:
    Account Quota
    PGFLQUO 220,000 pagelets if you use the default for MHEAP. Add 2,000 pagelets for each MB you increase MHEAP above the default. (See Section 3.3.1.)
    BYTLM 36,000 bytes or greater

    If necessary, use the OpenVMS Authorize utility to increase these quotas.

3.3 Using DCL Commands to Run DECamds and the Availability Manager

After you make postinstallation file edits, use the commands shown in the following sections to start the Availability Manager and DECamds.

3.3.1 Starting the Availability Manager

Before starting the Availability Manager, you need to execute the following command file:


   SYS$MANAGER:JAVA$SETUP.COM 

This command file sets up logical names on your system for running Java.

To start the Availability Manager, enter the following DCL command:


$ AVAIL/AVAIL 

You can also use either of the following qualifiers to the AVAIL command:
Qualifier Description Default Value of n
IHEAP= n Initial heap size 16M
MHEAP= n Maximum heap size 40M

where n is the amount of memory to allocate to the heap. Use nK to specify kilobytes or nM to specify megabytes. The default values are in megabytes.

For large memory configurations, you might want to increase the heap sizes of the application for better performance. Note that the value of PGFLQUOTA must be a minimum of:


140,000 + (2,000 * MHEAP) 

3.3.2 Starting DECamds

To start DECamds, enter the following DCL command:


$ AVAIL/MOTIF 

You can also use any of the following qualifiers:
Qualifier Description
/CONFIGURE Specifies the directories from which input files are read. This can be a search list of directories or a logical defining a search list of directories.
/LOG_DIRECTORY Specifies the directory to which log files are written. Output files can be directed to the null device, NLA0:
/GROUP A comma-separated list of the groups of Data Provider nodes that you want the Data Analyzer to access.

Note

At a later time, if you install a version of DECamds previous to Version 7.2-1A, you must reinstall the Availability Manager to define the AVAIL command correctly.

  [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]  
  privacy and legal statement  
6552INSTALL_VMS.HTML