Chapter 3

After the Installation

PL/I is now installed and can be invoked by all users with the DCL command, PLI.

The installation procedure modifies the DCL command table so that the PLI command is recognized and processed. However, the previous command table is still in effect for those users who are currently logged in. All logged-in users who want to use the PLI command for the newly installed product must log out of the system and log in again.

If PL/I is used extensively on your system, you can reduce system overhead requirements by installing it as a shareable image using the OpenVMS Install Utility. For more information, read Section 2.1.2, “Installing Endless PL/I V3.9 for OpenVMS VAX as a Shared Image” or Section 2.2.2, “Installing Endless PL/I V5.0 for OpenVMS Alpha as a Shared Image”.

3.1. Running the Installation Verification Procedure Separately

The Installation Verification Procedure (IVP) is usually run at installation. You can also run it separately at any time to ensure the integrity of installed files if you have problems with your system. The following command procedures execute the IVP:

Endless PL/I V3.9 for OpenVMS VAX

$ @SYS$SYSROOT:[SYSTEST]PLI$IVP.COM Return

Endless PL/I V5.0 for OpenVMS Alpha

$ @SYS$SYSROOT:[SYSTEST]DPLI$IVP.COM Return

If the IVP fails, one of the following messages is displayed, depending upon which OpenVMS system you are using:

Endless PL/I V3.9 for OpenVMS VAX

***  VAX PL/I Installation Verification Procedure ***
   **** Beginning at  dd-mmm-yyyy hh:mm:ss.ss ****

    IVP test ASSIGN...

******** VAX PL/I Installation Verification FAILED ********

***  VAX PL/I Installation Verification Procedure ***
    ***** Ending at  dd-mmm-yyyy hh:mm:ss.ss ****

Endless PL/I V5.0 for OpenVMS Alpha

        *--------------------------------------------*
        *    Installation Verification Procedure     *
        * DEC PL/I for OpenVMS AXP(tm) Systems V4.0  *
        *--------------------------------------------*

© Digital Equipment Corporation 1993.  All rights reserved.

   **** Beginning at  dd-mmm-yyyy hh:mm:ss.ss ****

    IVP test ASSIGN...

******** DEC PL/I Installation Verification FAILED ********

***  DEC PL/I Installation Verification Procedure ***
***** Ending at  dd-mmm-yyyy hh:mm:ss.ss ****

3.2. Installing PL/I on a VMScluster

If you want to run PL/I on multiple nodes of a VMScluster, first check to see that you have the appropriate software license. Then, follow these steps after installing PL/I:

Execute the LICENSE LOAD command to activate the license on each node in the VMScluster on which PL/I is to be executed.
To use the product on other nodes in the VMScluster, you must replace the version of the DCL tables installed on the other VMScluster nodes. To do this, perform the following steps:
1. Log in to a node on the cluster.
2. Run INSTALL and enter the following command at the INSTALL> prompt:
```
INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE Return
```
3. Repeat steps a and b for each node of the cluster.

As a faster alternative, you can use the SYSMAN utility to replace the DCL tables on all cluster nodes. To do this, perform the following steps.

Log in to a node on the cluster.
Run SYSMAN and enter the following commands at the SYSMAN> prompt:
```
SYSMAN> SET ENVIRONMENT/CLUSTER Return
SYSMAN> DO INSTALL REPLACE SYS$LIBRARY::DCLTABLES.EXE Return
```
You need do this on only one node of the cluster, and all nodes will be updated.

3.3. Maintenance Updates

Digital may periodically issue maintenance updates of PL/I. Each update consists of an installation kit. You should install this kit as described herein or in any documentation that may accompany the maintenance update.

Each time a maintenance update is released, the version number changes. For example, if the current version is 3.0, the version number of the first maintenance update will be 3.1. In addition, the maintenance update includes new release notes. The release notes describe the changes that have been made to PL/I since the previous release.

The update release notes are online. To locate the release notes after installing PL/I, type or print one of the following files:

Endless PL/I V3.9 for OpenVMS VAX

SYS$HELP:PLI$038.RELEASE_NOTES

Endless PL/I V5.0 for OpenVMS Alpha

SYS$HELP:DPLI050.RELEASE_NOTES

or, enter the following command:

$ HELP PLI RELEASE_NOTES Return

3.4. Determining and Reporting Problems

If an error occurs while using PL/I and you believe that the error is caused by a problem with PL/I, take one of the following actions:

If you purchased PL/I within the past 90 days and you think the problem is caused by a software error, you can submit a Software Performance Report (SPR).
If you have a Basic or DECsupport Software Agreement, call your Customer Support Center. With these services, you receive telephone support that provides high-level advisory and remedial assistance. For more information, contact your local Digital service representative.
If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR).

If you find an error in the PL/I documentation, complete and submit a Reader's Comments form from the back of the manual containing the error. Include the section and page number on which the error occurred.