# DIGITAL TP Web Connector
DIGITAL Database Web Connector
Getting Started

Previous | Contents | Index

## 3.2.7 Aborting the Installation

To abort the installation procedure at any time, press Ctrl/Y. When you press Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again.

## 3.2.8 Accessing the :CD--ROM

Copy the saveset files from the TP Web Connector for Windows NT :CD--ROM to a directory on the OpenVMS system in which you will start the installation procedure. Log in to the system under an account having the appropriate privileges as described in Section 3.2.2. For example:

    Username:  SYSTEM
    Password:
    $

Set the default to the directory in which you are going to copy the distribution files. Refer to Section 3.2.5 for the disk space requirements. For example:

    $  SET DEFAULT SYS$UPDATE
    $

The directory SYS$UPDATE is used in this example.

The procedures differ based on whether the version is 6.1 or higher (see Section 3.2.8.1) or 5.5-2 (see Section 3.2.8.2).

### 3.2.8.1 Procedures for OpenVMS Alpha or VAX Version 6.1 or Higher

On OpenVMS Version 6.1 or higher (excluding Version 7.0) systems on either the Alpha or VAX platform, obtain the distribution files from the distribution :CD--ROM. To obtain the directory location of the saveset for the TP Web Connector OpenVMS components on the :CD--ROM, refer to OpenVMS Layered Products Compact Disc User's Guide, or, before starting the installation, complete these steps:

1. To determine whether the :CD--ROM drive is already mounted (MOUNT command), enter a command in the following format:

`SHOW DEVICE device-name`

2. If the device is not mounted, enter a command in the following format:

`MOUNT/OVERRIDE=ID device-name`

For example:

    $  MOUNT/OVERRIDE=ID DKA200:

3. To obtain the distribution files, use a COPY command, specifying the same device name, in the following format:

`COPY device-name:[directory-name]*.* []`

The directory-name depends on the OpenVMS platform, as follows:

OpenVMS Platform | Directory Name
--- | ---
Alpha | VMSALPHA
VAX | VMSVAX

For example:

    $  COPY DKA200:[VMSALPHA]*.* []
    $

This commands copies the distribution files for the Alpha platform.

4. Expand the self-extracting archive files to obtain the OpenVMS savesets. The commands to use depend on the platform.
   For OpenVMS Alpha platforms:

    $  RUN ACMSDA010AA.EXE
    File name:
    $  RUN ACMSDA010AB.EXE
    File name:
    $  RUN ACMSDA010AC.EXE
    File name:
    $

For OpenVMS VAX platforms:

    $  RUN ACMSDA010VA.EXE
    File name:
    $  RUN ACMSDA010VB.EXE
    File name:
    $  RUN ACMSDA010VC.EXE
    File name:
    $

Press Return at the `File name:` prompt to copy all files into the directory.

Now you are ready to begin the installation procedure (see Section 3.3).

### 3.2.8.2 Procedures for OpenVMS VAX Version 5.5-2

On OpenVMS VAX Version 5.5-2 platforms, use the FTP utility to copy the distribution files to the OpenVMS host-system directory from the device on the Windows NT system on which the :CD--ROM is mounted.

    FTP> open host-system
    ! Supply login information for OpenVMS Host system where
    ! username  is a privileged account.
    username:
    password:
    FTP> lcd E:\VMSVAX
    FTP> cd SYS$UPDATE:
    FTP> binary
    FTP> mput
    FTP> close
    FTP> quit

The FTP commands copy the distribution files to the directory in which you will run VMSINSTAL (SYS$UPDATE in this example).

Expand the self-extracting archive distribution files to obtain the OpenVMS savesets. For example:

    $  RUN ACMSDA010VA.EXE
    File name:
    $  RUN ACMSDA010VB.EXE
    File name:
    $  RUN ACMSDA010VC.EXE
    File name:
    $

Press Return at the `File name:` prompt to copy all files into the directory.

Now you are ready to begin the installation procedure (see Section 3.3).

# 3.3 Installation Procedure

To install the ACMSADU extension or the ACMS Desktop adapter gateway, perform the steps described in Sections 3.3.1 to 3.3.5.

## 3.3.1 Stopping the ACMS System

If you have TP Web Connector components already installed and running, shut them down. While logged in to the system under an account having the appropriate privileges as described in Section 3.2.2, execute the following commands:

    $  @SYS$STARTUP:ACMSDA$SHUTDOWN
    $

If you have ACMS software already installed and running, shut it down. Execute the following commands:

    $  ACMS/STOP SYSTEM
       .
       .
       .
    $  @SYS$STARTUP:ACMSTOP
       .
       .
       .
    $

When ACMS is stopped, invoke VMSINSTAL (see Section 3.3.2).

## 3.3.2 Invoking VMSINSTAL

When you invoke VMSINSTAL, it checks for the following conditions:

- You are logged in to a privileged account.
- You have adequate quotas for installation.
- No users are logged in to the system.

If VMSINSTAL detects any problems during the installation, it notifies you of the problem and asks whether you want to continue the installation. In some instances, you can answer YES to continue. To stop the installation process and correct the situation, answer NO or press the Enter key.

While logged in to the privileged account, set the default to the directory in which you stored the saveset files. SYS$UPDATE is used in this example.

    $  SET DEFAULT SYS$UPDATE
    $

Use the following syntax to invoke VMSINSTAL:

`@SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N`

The parameter saveset-name represents the installation name for the component. For the TP Web Connector components, use the installation name ACMSDA010. If you do not supply the saveset name, VMSINSTAL prompts you for it later in the installation procedure.

The parameter device-name represents the location of the saveset files (see Section 3.2.8). If you do not supply `device-name`, VMSINSTAL prompts you for this information later in the installation procedure.

OPTIONS N is an optional parameter indicating that you want to be prompted to display or print the release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not prompt you to display or print the release notes.

VMSINSTAL supports several other options. For information, refer to the OpenVMS documentation on software installation.

Next, execute the installation procedure on the ACMS host system. For example:

    $  @SYS$UPDATE:VMSINSTAL ACMSDA010 SYS$UPDATE: OPTIONS N

This command begins installing the ACMSDA010 saveset found in the SYS$UPDATE directory. VMSINSTAL asks several installation questions as described in Section 3.3.3.

## 3.3.3 Installation Questions

This section discusses the questions that VMSINSTAL asks during the installation. Each question in the installation is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example, [YES]. To give the default response, press the Enter key.

The following are the questions:

- Confirming active processes
  VMSINSTAL displays a list of all active processes and asks whether you want to continue the installation. Install the ACMSADU extension and the ACMS Desktop adapter gateway on a standalone system or cluster with DECnet shut down to minimize possible installation problems.
- Confirm system backup
  VMSINSTAL asks whether you are satisfied with your system backup. Always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press the Enter key. Answer NO to discontinue the installation.
- Release notes
  If you specified OPTIONS N when you invoked VMSINSTAL, the installation procedure gives you the following options for reviewing the release notes:

- Display release notes
  If you select option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing Ctrl/C.
- Print release notes
  If you select this option, VMSINSTAL prompts for the name of the print queue to use. Enter a queue name or press the Enter key to send the file to the default output print device.
- Both 1 and 2
  If you select this option, VMSINSTAL displays the release notes on line and prompts for a queue name for the print device.
- None of the above
  If you select option 4, VMSINSTAL continues the installation without printing or displaying release notes.

- Continuing the installation
  The installation procedure asks whether you want to continue the installation. To continue, answer YES. Otherwise, press the Enter key. In either case, the release notes are copied to a file in the SYS$HELP directory.
- Choosing to install components
  You can choose one of the following options for installation:

1. Install ACMSADU extension
2. Install ACMS Desktop adapter gateway
3. Install all of the above

- Choosing to run the IVP
  When you install the software, the installation procedure asks whether to run the IVP. The IVP checks that the software is installed correctly. DIGITAL recommends that you run the IVP during installation.

If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories and updates help files. If you asked for files to be purged, that work is done. The following message is displayed.

    %VMSINSTAL-I-MOVEFILES, Files will now be moved to
        their target directories...

If you are installing the TP Web Connector components on a system disk that has limited free space, VMSINSTAL might not be operating in safety mode. In this case, VMSINSTAL processes all files immediately and does not display the `%VMSINSTAL-I-MOVEFILES...` message.

If the disk has quotas enabled, a message is displayed.

## 3.3.4 Running the Installation Verification Procedure

If you chose to run the IVP, VMSINSTAL runs it next. When the IVP runs successfully, you see the following messages displayed:

    TP Web Connector V1.0 IVP started....

    The TP Web Connector V1.0 IVP completed successfully
                 Installation of ACMSDA V1.0 completed at 13.32

If you see no other messages between these messages and those described in Section 3.3.5, the IVP completed successfully.

## 3.3.5 Completing the Installation Procedure

The following messages indicate that the entire installation procedure is completed:

    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

    Creating installation data file:
        VMS$ROOT:[SYSUPD]ACMSDA010.VMI_DATA

     Installation of ACMSDA V1.0 - completed at 13:32

     VMSINSTAL procedure done at 13:33
    $

If you installed the ACMSADU extension, restart ACMS. Follow the standard procedure:

    $  @SYS$STARTUP:ACMSTART
       .
       .
       .
    $  ACMS/START SYSTEM
       .
       .
       .
    $

If you installed the ACMS Desktop adapter gateway, see the suggestions in Section 3.6.

You can now log out of the privileged account.

VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you continue using the SYSTEM account and you want to restore these symbols, log out of the system and log in to the system again.

# 3.4 System Failures

If you experience a system failure, such as a power loss, during installation, VMSINSTAL attempts to continue the installation when you reboot the system. Depending on when the system fails during the installation, one of the following conditions exists:

- The system disk did not undergo any changes before the system failure. VMSINSTAL instructs you to restart the installation.
- The system disk used by the installation was corrupted. VMSINSTAL instructs you to restore the system disk from the backup copy and restart the installation.
- VMSINSTAL continues the installation and can tell you to manually purge replaced files, even if you request that they be purged automatically. You can purge files, but remember that purging deletes all but the latest version of all files on your system disk. If you have multiple versions of system files to save, you can delete just the TP Web Connector for OpenVMS files that you want to remove from system directories.
  To purge files, perform the following steps:

- Reboot the system.
- Log in to the SYSTEM account.
- Purge all system files using the following command:

    $  PURGE/LOG SYS$SYSROOT:[*...]*.*

After you perform this task, the installation is completed.

After you see the message that indicates the beginning of the IVP, the installation of the component software is completed. If the system fails subsequently, VMSINSTAL displays the following message when you reboot:

    %VMSINSTAL-I-RECOVER, ACMSDA was being installed
       when the system crashed.

This message indicates that VMSINSTAL finished successfully, not that the installation of the software was successful. VMSINSTAL does not automatically restart the IVP. Run the IVP independently.

# 3.5 Installation Failures

If the installation of the TP Web Connector components or a sample application fails for some reason other than a system failure, the installation procedure displays a message describing the cause of the failure. To continue with the installation, correct the condition causing the error and restart the installation procedure from the beginning.

Errors can occur during the installation if any of the following conditions exist:

- The operating system version is incorrect.
- A prerequisite software version is incorrect.
- Quotas necessary for successful installation are insufficient.
- System parameter values for successful installation are insufficient.
- The OpenVMS HELP library is currently in use.

For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installations. If you are notified that any of these conditions exist, take the appropriate action as described in the message. (You might need to change a system parameter or increase a quota value.)

If the installation of the component software is completed satisfactorily, but a test fails during the IVP, the IVP displays a message describing the failure and suggests a course of action.

In most cases, the suggested course of action is to reinstall the software. If the IVP fails after you reinstall the software, contact a DIGITAL specialist.

# 3.6 After Installing the TP Web Connector Components

After installing the software, you can perform the procedures described in this section.

## 3.6.1 Operating the ACMS Desktop Adapter Gateway

If you installed the ACMS Desktop adapter gateway on your system, you can

1. Edit OpenVMS system startup and shutdown files so that the adapter gateway process runs when the system bootstraps and stops when system shutdown occurs. The OpenVMS system startup and shutdown files provide for automatic startup and shutdown of the ACMS Desktop adapter gateway. (This step is usually not necessary for system upgrades.) See Section 8.2 for procedures to automatically start up and shut down the ACMS Desktop adapter gateway.
2. Enable the adapters to find the ACMS Desktop adapter gateway. Supply the necessary configuration information using the TPware management utility as described in Chapter 8.

## 3.6.2 Steps for Calling ACMS Tasks

If you install the ACMSADU extension on your system and are developing clients that call ACMS tasks on this system, follow these general steps:

- Use TP Web Connector components on OpenVMS systems to begin the client development (see Chapter 6).
- Develop the client (using output from following the guidelines in Chapter 6) on a Windows NT system on which you have installed TP Web Connector components (see Chapter 4).
- Configure TPware parameters on a Windows NT system (see Chapter 7).
- Set up an ACMS Desktop adapter gateway on an OpenVMS system (see Chapter 8).

## 3.6.3 Running the ACMS Desktop Adapter IVP

This section describes how to run the installation verification procedure (IVP) separately from the installation procedure. The IVP can be run as a part of the normal installation. The IVP automatically runs when you install the software and answer YES to the IVP question. If the IVP fails for any reason, correct the error and rerun the IVP.

### 3.6.3.1 IVP Requirements

The IVP checks that the installation procedure successfully completed installing the ACMSADU extension or the ACMS Desktop adapter gateway and that the software can be used to set up or run applications. The IVP checks that all the necessary files are on the system.

### 3.6.3.2 IVP Steps

To run the IVP independently of the installation procedure, follow these steps:

1. Log in to the SYSTEM account.
2. Set your default to the test directory (SYS$TEST).
3. Run the ACMSDA$IVP.COM command procedure.
   You can run the IVP only on your current booted system. You cannot run the IVP over a networked connection. For example:

    $  @ACMSDA$IVP

The IVP takes no more than 30 seconds to run, depending on the current system load.

### 3.6.3.3 IVP Error Recovery

As the IVP executes, it checks the success of each test and operation that it performs. If any test or operation fails, the IVP displays a message describing the failure and suggests a course of action. Follow the suggested course of action and then restart the IVP.

Previous | Next | Contents | Index