Compaq ACMS for OpenVMS
Remote Systems Management Guide

Previous Contents Index

Part 1

Part 1 contains information about configuring and using the remote management features of ACMS. It contains an overview of the Remote Manager as well as information on how it is managed and operates.

Chapter 2 and Chapter 3 describe how to install and configure both the Remote Manager and the Remote Manager web agent. Chapter 4 and Chapter 5 explain how to manage data collection and how to use the Remote Manager to modify a running ACMS system.

Finally, Chapter 6 and Chapter 7 show you how to write programs that perform remote management using RPC and SNMP.

Chapter 1
Overview of Remote Management

This chapter provides an overview of ACMS remote management.

1.1 Architecture and Implementation

The ACMS Remote Manager provides system managers with the capability of monitoring and managing their ACMS application environment across a network. The facilities that comprise the Remote Manager are based on a client/server architecture. Two protocols are supported for accessing the ACMS remote management server: Open Network Computing Remote Procedure Call (ONC RPC), which is used by command line utilities (provided with the remote management option) and can be called directly from user-written programs; and Simple Network Management Protocol (SNMP), for use with third-party management consoles.

As Figure 1-1 shows, users communicate with the ACMS Remote Manager over a TCP/IP network using one of the supported interfaces:

Figure 1-1 ACMS Remote Manager Architecture

Using SNMP or RPC commands, ACMS system managers can configure and control the system data being collected, automatic variable monitoring, and operation of the interfaces themselves.

Communications between the ACMS Remote Manager and the ACMS run-time system are transparent. Users may be on the same or a different node than the Remote Manager, but the Remote Manager must be running on the same node as the ACMS run-time system it is monitoring or accessing.

The Remote Manager obtains initial configuration information during process startup from a user-maintained configuration file (described in Chapter 4). Once started, the Remote Manager provides ACMS system managers remote access to their ACMS application environment through the interfaces.

1.2 Remote Management Capabilities

The Remote Manager provides ACMS system managers with the ability to:

Chapter 2
Getting Started with the ACMS Remote Manager

This chapter describes how to prepare and run the ACMS Remote Manager software on a node where Compaq ACMS for OpenVMS, Version 4.4 has been installed. This chapter does not describe the actual installation. For information about installing Compaq ACMS for OpenVMS, Version 4.4, refer to the Compaq ACMS for OpenVMS Version 4.4 Installation Guide.


The procedures in this chapter assume Compaq TCP/IP Services Version 5.0A for OpenVMS (TCP/IP) or higher is installed. The image and process names changed in Version 5.0 from UCX* to TCPIP*. If you are using a machine with an older version of TCP/IP Services installed, you should substitute UCX wherever you see TCPIP in the instructions in this chapter.


The following terms are used in this chapter:

2.1 Running the ACMS Remote Manager

The following sections outline the steps required to get the ACMS Remote Manager running on an OpenVMS system. If you are an inexperienced user of ACMS, you should first read Section 2.2 and Section 2.3 for detailed information about how to set up a node for ACMS remote management.

This section describes setup for both client and server nodes. Server nodes automatically support all client functions; once a node is set up as a server, it can function as a client and a server without additional work. Client nodes can function only as clients.

When you complete the following procedures, the ACMS Remote Manager will be running on your system and you can access it using the ACMSMGR command line utility, the Remote Manager web agent, or a third-party or user-written client that uses one of the supported interfaces.

Note that the Remote Manager web agent requires some configuration before use. See Chapter 3 for detailed configuration instructions as well as for a brief overview of the browser interface.

2.1.1 Server Node Setup

Before you begin, you must have already installed the ACMS Version 4.4 kit on your system. Also ensure that you have the minimum supported version of TCP/IP (as described in the ACMS Software Product Description [SPD 25.50.xx]) installed on your node, and that it is operational. (If TCP/IP is not installed and operational, the ACMS Remote Manager will not run.) For information about TCP/IP setup, see Section 2.2.

Once you have installed the ACMS and TCP/IP software, perform the following steps to set up a Remote Manager server node:

  1. Verify Portmapper (RPC) setup (see Section
  2. Run the ACMS postinstallation procedure (see Section
  3. Define process logicals and symbols (see Section
  4. Prepare the ACMS environment (see Section
  5. Start the ACMS Remote Manager (see Section

Server nodes are automatically client nodes. Therefore, you do not need to perform the tasks in Section 2.1.2 for nodes that you set up as server nodes. Verify Portmapper (RPC) Setup

Before you attempt to start the Remote Manager, ensure that the proper TCP/IP support is in place. This section provides an overview of the Portmapper (RPC) verification process. If you need more detailed information, or if you will be using third-party tools or writing your own SNMP management tools, see Section 2.2.

  1. Look for the process TCPIP$PORTM (UCX$PORTM on older versions):


    If you find the TCPIP$PORTM process, RPC is running and you can skip to Section Otherwise, go to step 2.

  2. See whether the Portmapper service is enabled:

    $ TCPIP 
    Service             Port  Proto    Process       Address    State 
    PORTMAPPER           111  TCP,UDP  TCPIP$PORTM    Enabled 

    The Portmapper should have both the TCP and UDP protocols defined. If it does not, you may need to configure the Portmapper (see Section 2.2.2). If the Portmapper state is Enabled, skip to Section Otherwise, go to step 3.

  3. To enable the Portmapper, enter the following commands:

    $ TCPIP 

    Then restart TCP/IP. The Portmapper process does not automatically start when TCP/IP starts, so you may not see the TCPIP$PORTM process. The process starts the first time the Portmapper is accessed. Run the ACMS Postinstallation Procedure

If you did not run the postinstallation procedure when you installed the ACMS Version 4.4 kit, do so now. For details, see Section 2.3.

  1. Run the postinstallation procedure as follows:


  2. When you are asked whether you want to configure the ACMS Remote Manager, answer YES:

    Do you want to SETUP and CONFIGURE the ACMS Remote System Manager [Y]? YES 

  3. Answer the questions according to the needs of your organization. Define Process Logicals and Symbols

The ACMS$MGMT_ENV.COM command procedure is provided to define some symbols that make using the ACMSMGR utility simpler. For more information, see Section 2.3.2, or run the procedure now by entering the following command:

$ @SYS$STARTUP:ACMS$MGMT_ENV.COM Prepare the ACMS Environment

You are now ready to start the Remote Manager. If you need more information about this procedure, see Section 2.3.3. Then follow these steps:

  1. Ensure that the ACMSTART.COM procedure has been run by entering the following command:


    If you get the following error, you must invoke the SYS$STARTUP:ACMSTART.COM procedure described in step 2:

    %DCL-W-ACTIMAGE, error activating image ACMSHR    

    If you get a message indicating that the ACMS system is stopped, or if some information about the ACMS system is displayed, go to Section

  2. Invoke the ACMSTART command procedure:

    $ @SYS$STARTUP:ACMSTART Start the ACMS Remote Manager

To start the ACMS Remote Manager, follow these steps:

  1. Enter the following command:


  2. Check that the Remote Manager processes (ACMS$MGMT_SVR, ACMS$TRACE_MON, and ACMS$MGMT_DCL) are started by entering the following command:


  3. If the processes are running, you should be able to communicate with them using ACMSMGR commands (see Section 2.1.3).
    If any of the process are not running, you can look for information in the following places:
    For more information about these sources, refer to Section and Section

2.1.2 Client Node Setup

All ACMS Remote Manager client nodes require that TCP/IP be installed and operational. (For information about TCP/IP setup, refer to Section 2.2.) Other than TCP/IP connectivity to the server node, no additional TCP/IP setup is required. (The Portmapper does not need to be running on the client node.)

The following sections describe how to set up an ACMS Remote Manager client node. You can skip these sections if you are installing the ACMS Remote Mangement server; server nodes are automatically client nodes.

If the client node will not be used as an ACMS submitter node, the ACMS Remote Option kit does not need to be installed. How you set up the client node depends upon whether the ACMS Remote Option kit has been installed.

Once you have completed these tasks, you can try to communicate with a Remote Manager on a server node using the procedure in Section 2.1.3.

Note that you cannot obtain ACMS system management information or perform system management functions on nodes that are client nodes only. Client nodes can get information from and perform operations on server nodes only. Run ACMS_POST_INSTALL.COM

Follow these steps to run the ACMS_POST_INSTALL.COM command procedure:

  1. Run the postinstallation procedure as follows:


  2. When you are asked whether you want to configure the ACMS Remote System Manager, answer YES:

    Do you want to SETUP and CONFIGURE the ACMS Remote System Manager [Y]? YES 

  3. Answer the questions according to the needs of your organization.
  4. Now execute the ACMS$MGMT_ENV.COM command procedure to define some symbols that make using the ACMSMGR utility simpler:

    $ @SYS$STARTUP:ACMS$MGMT_ENV.COM Copy Files and Define Symbols

If you did not install the ACMS Remote Option kit (that is, if this node will not be an ACMS submitter node), follow this procedure. You will need access to a node with one of the ACMS Version 4.4 Run-Time kits installed.

  1. Copy the ACMSMGR executable to your node from SYS$SYSTEM on the node that has ACMS Version 4.4 installed. Which executable to copy depends on the version of Compaq TCP/IP Services for OpenVMS (TCP/IP) you have installed:
  2. Copy ACMS$MGMT_ENV.COM to your node and run it. This file is located in SYS$STARTUP of a node where ACMS Version 4.4 is installed. ACMS$MGMT_ENV.COM defines some symbols that make using the ACMSMGR utility simpler. Execute the command procedure as follows:


2.1.3 Communicate with the Remote Manager

Before you issue any ACMSMGR commands, you must either log in to the Remote Manager (see step 1) or use an ACMS proxy (see step 2). For detailed information, see Section 2.3.5.

  1. To log in to the Remote Manager, you must have a valid user account and password on the node on which the Remote Manager is running. The following example commands log in to the Remote Manager on node SERVER, using account MYACCT and password MYPASS. (For more details, see Section

    ACMS Remote Management -- Command line utility 

    If the login succeeds, no messages are displayed. Go to step 3.
    If the login fails, check the following possible reasons:

    Refer to Section 2.4 for more help.
  2. If you will be using ACMS proxies to access the Remote Manager, and you already know that you have a valid proxy account, go to step 3. If you have not set up proxies but would like to use them, create a proxy file on the node on which the Remote Manager will run. (For more information, see Section


    Now you can add a proxy. To add a proxy, you need to know the following information:

    For example, assume you will be on node CLIENT using account MYACCT, and you will be accessing node SERVER using account SRVACCT. Enter the following command on node SERVER:


  3. You can now enter any of the ACMSMGR commands. For example:


    This command results in output similar to the following:

    ACMS Remote Management -- Command line utility 
    ACMS V4.4-0  Interfaces Display                 Time: 18-APR-2001 13:59:15.51 
                     Enabled Running Get      Set      Alarms Time Last 
    Node   Interface State   State   Requests Requests Sent   Alarm Sent 
    ------ --------- ------- ------- -------- -------- ------ ----------------------- 
    SERVER rpc       enabled started 987      0        0      17-NOV-1858 00:00:00.00  
    SERVER snmp      enabled started 0        0        0      17-NOV-1858 00:00:00.00  

    If you get error messages instead, refer to Section 2.4.

2.2 TCP/IP Setup

There are three components to the TCP/IP setup for the ACMS Remote Manager:

The information in the following sections applies mainly to server nodes on which the ACMS Remote Manager will run. Section 2.2.2 and Section 2.2.3 do not apply to ACMS Remote Manager client nodes.

2.2.1 Review TCP/IP Host Names

For consistent handling and display of commands that use the ACMSMGR /NODE qualifier and the ACMS$MGMT_SERVER_NODE logical, all potential ACMS systems should have a TCP/IP host name (or alias) that matches the current six-character DECnet host name.

To determine whether potential ACMS hosts are named appropriately, use the following command to list the contents of the TCP/IP hosts database:


You will see a display similar to the following, where SPARKS.ACMS.COMPAQ.COM is the host name and SPARKS a system alias:

Host address         Host name 

Review this list and do one of the following for each potential ACMS host:

If you have defined any new aliases, restart TCP/IP to apply the changes made in the host database.

Previous Next Contents Index