In this case, the installation skips any subsequent inquiries, including the question about the PAK, and proceeds to install only the COBRTL image.

As in the full installation, the version of the current COBRTL.EXE is automatically checked.

If the version already installed on your system is later than the COBRTL.EXE you are attempting to install separately, the installation procedure issues the following message followed by another prompt:

%COBOL-I-IDNTCK, COBRTL found in SYS$SHARE has later ident than COBRTL to be installed. Do you still want to install COBRTL from kit [NO]? [Return]

Press Return at the prompt to terminate the installation without installing the COBRTL image supplied with your Compaq COBOL kit. Or type YES and press Return to install it.

* Do you still want to install COBRTL from kit [NO]? Y [Return] %COBOL-I-UPDIMG, Installing new COBRTL image %PATCH-I-NOLCL, image does not contain local symbols %PATCH-I-WRTFIL, updating image file ... DKB300:[SYS0.SYSUPD.COBOLver]COBRTL.EXE;2 %COBOL-I-UPDOBJ, Updating system object library %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Remember to use the INSTALL utility to make the COBRTL.EXE that is replaced by the installation a known image. This must be done on every node in a VAXcluster. Use INSTALL REPLACE or use the OpenVMS System Management utility (SYSMAN) to facilitate the installation on multiple nodes (see Section 2.3).

Step 6: Respond to LMF queries.

This product supports the OpenVMS License Management Facility (LMF). For more information on LMF, see the OpenVMS License Management Utility Manual.

During the installation procedure, the Compaq COBOL Product Authorization Key (PAK) is invoked and the following questions are asked:

* Does this product have an authorization key registered and loaded? YES [Return]

This step allows you to indicate whether or not your LMF license for Compaq COBOL is registered and loaded.

It is strongly recommended that you install the PAK for Compaq COBOL prior to installing the product.

If the PAK is not installed, you can still proceed with the installation and install the PAK after the installation is complete. However, a check for the PAK is done by the compiler during the IVP, and if the PAK is not installed, the IVP will fail. Also, the build of the REFORMAT utility (Step 7) requires prior installation of the PAK.

The following list summarizes the outcome of your responses to this query:

• If you answer YES and the PAK is installed, the installation proceeds normally.
• If you answer YES and the PAK is not installed, the IVP will fail.
• If you answer YES and the PAK is not installed, the installation fails if you selected the REFORMAT utility option.
• If you answer NO, the installation terminates.

In any case, the Compaq COBOL compiler will not execute until the PAK for Compaq COBOL is installed.

Step 7: Install the REFORMAT utility.

* Do you want the REFORMAT utility installed [YES]? [Return]

Depending on your use of Compaq COBOL, you may want to install the optional REFORMAT utility.

Step 8: Respond to the message file query.

* Do you want to save the COBOL message file for modification [NO]? [Return]

This query enables you to edit the Compaq COBOL message file COBOLMSG.MSG. Customized messages are often desirable for international users. If you plan to edit the message file, type YES and press Return. If you do not want to edit the message file, press Return. For more information, see Section 3.2.

Step 9: Respond to the purge files query.

If the installation is successful, the SYS$EXAMPLES, SYS$HELP, SYS$LIBRARY, SYS$MANAGER, SYS$UPDATE, SYS$MESSAGE, and SYS$SYSTEM directories may contain previous versions of the following Compaq COBOL files:

• [SYSEXE]COBOL.EXE
• [SYSEXE]REFORMAT.EXE
• [SYSLIB]DCLTABLES.EXE
• [SYSTEST.COBOL]COBOL$IVP.COM
• [SYSHLP]COBOLver.RELEASE_NOTES
• [SYSHLP]COBOLver_RELEASE_NOTES.PS
• [SYSMSG]COBOLMSG.EXE
• [SYSUPD]COBOLMSG.MSG
• [SYSLIB]LSE$SYSTEM_ENVIRONMENT.ENV

* Do you want to purge files replaced by this installation [YES]? [Return]

These files are replaced during the installation with new files, but the old files are not automatically purged. Purging is recommended. (Purging will not destroy earlier versions of the release notes, which you should retain.) In response to the purging prompt, press Return to purge the files or type NO to keep them. In either case, the system help files are updated.

Not purging these files allows you to go back to a previous version of a file, if necessary.

The installation may also create a new version of the following file, which is not purged along with the other files:

• [SYSLIB]COBRTL.EXE

The installation procedure may update the following files (it will not create new versions of them, nor will it purge them):

• [SYSLIB]IMAGELIB.OLB
• [SYSLIB]STARLET.OLB

The query on purging files is the last one you have to respond to during the installation. After you respond to this query, the following message is displayed:

No more questions will be asked during this installation.

If another user has locked the Help file during the installation, the following three informational messages are issued:

%VMSINSTAL-I-DCLHLPINUSE, DCL HELP could not be updated. -VMSINSTAL-I-DCLHLPINUSE, manually update HELP libraries after installation. -VMSINSTAL-I-DCLHLPINUSE, use SYS$COMMON:[SYSHLP]COBOLHLP.HLP for providing new HELP.

You may need to mount additional distribution volumes depending on the media used. In this case, you will receive a prompt from VMSINSTAL to determine that you are ready to proceed. (See Step 10.)

Step 10: Insert the subsequent installation kit volumes as requested.

%BACKUP-I-READYREAD, mount volume 2 on _MYCPU$MUA100: for reading Enter "YES" when ready: YES [Return]

VMSINSTAL prompts you to insert the next volume and waits for you to type YES after inserting it. If you type NO, VMSINSTAL displays the prompt again. This prompt is displayed only if your installation kit contains more than one volume. Exactly when these prompts appear depends on the type of media that you are using.

Step 11: Read the informational messages.

The Compaq COBOL installation procedure produces a number of informational messages that report on the progress of the installation.

The success of the installation is indicated by the following message:

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

If the installation procedure is successful, the new or modified files are moved to their target directories.

The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE files are updated to include the new versions of the Compaq COBOL Help text and the Compaq COBOL command line definition.

Step 12: Observe the Installation Verification Procedure.

VMSINSTAL now calls the IVP to verify that Compaq COBOL was installed successfully.

Start of Compaq COBOL for OpenVMS VAX Installation Verification Procedure Successful test of Compaq COBOL for OpenVMS VAX V5.n-cc Installation of COBOL V5.n completed at hh:mm

If another user has locked the Help file during your installation, the following messages are displayed:

%VMSINSTAL-I-REFDCLHLP, DCL HELP could not be updated. -VMSINSTAL-I-REFDCLHLP, Reference SYS$UPDATE:DODCLHELP.VMI for information on -VMSINSTAL-I-REFDCLHLP, updating DCL HELP.

Step 13: End the installation procedure.

VMSINSTAL procedure done at hh:mm $ LOGOUT [Return] SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.ss

When the product installation procedure is complete, you can choose to install more products or to log out (as shown here). If you removed any media from the console drive before beginning the installation, you should replace it now.

Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again.

2.3 Installing Compaq COBOL on a VAXcluster

You can use the OpenVMS System Management utility (SYSMAN) to facilitate running Compaq COBOL on multiple nodes in a cluster. With SYSMAN, you can define a system management environment so that operations performed on one node are automatically executed on all other nodes in the VAXcluster. (See the OpenVMS VAX documentation for more information.)

Always check first to see that you have the appropriate software license. Once you have installed Compaq COBOL on one system disk in the VAXcluster, you can update the version of the DCL tables and the version of the COBRTL installed on the other nodes in the cluster. Do the following:

1. Log in to a privileged account on a node on the VAXcluster. Invoke SYSMAN and enter the following command at the SYSMAN> prompt:

   SYSMAN>SET ENVIRONMENT/CLUSTER [Return]

2. If you are a new customer, ensure that the PAK has been registered before attempting to install Compaq COBOL. To load the PAK on all nodes in your cluster environment simultaneously, invoke SYSMAN and enter the following command at the SYSMAN> prompt:

   SYSMAN>LICENSE LOAD COBOL [Return]

3. Enter the following commands at the SYSMAN> prompt:

   SYSMAN>DO INSTALL REPLACE SYS$SHARE:DCLTABLES.EXE [Return] SYSMAN>DO INSTALL REPLACE SYS$SHARE:COBRTL.EXE [Return]

If Compaq COBOL will be used extensively on your system, you can reduce the system overhead and memory requirements by installing it as a shared image. To perform the installation on a system that is currently running, use the OpenVMS Install utility while you are logged in to a privileged account. If errors occur, consult the OpenVMS system messages documentation.

Do the following to install Compaq COBOL for OpenVMS VAX as a shared image:

1. Determine the number of available global pages and global sections on your system. See Section 1.3 for information on how to do this.
2. Invoke the OpenVMS Install utility and install Compaq COBOL as a shared image, as follows:

   $ INSTALL [Return]

   INSTALL> ADD SYS$SYSTEM:COBOL.EXE/OPEN/SHARED [Return] INSTALL> ADD SYS$MESSAGE:COBOLMSG.EXE/OPEN/SHARED [Return] INSTALL> EXIT [Return]

3. Update the system startup file to install Compaq COBOL.

To ensure that Compaq COBOL is installed as a shared image each time the system is bootstrapped, include the following lines in the site-specific startup file SYS$MANAGER:SYSTARTUP_V5.COM or SYS$MANAGER:SYSTARTUP_VMS.COM (SYS$MANAGER:SYSTARTUP_V5.COM has been changed to SYS$MANAGER:SYSTARTUP_VMS.COM for OpenVMS V6.2 and higher).

$ INSTALL ADD SYS$SYSTEM:COBOL.EXE/OPEN/SHARED $ INSTALL ADD SYS$MESSAGE:COBOLMSG.EXE/OPEN/SHARED

2.5 Using the PCSI Transition Kit to Register Compaq COBOL V5.7 and the COBRTL

After the installation of Compaq COBOL V5.7 has been completed, the installer on OpenVMS VAX V6.2 and higher can use five new files delivered with this kit to register the COBOL compiler and the COBRTL in the POLYCENTER Software Installation utility (PCSI) database. These files are placed in your SYS$UPDATE directory. These files are:

DEC-VAXVMS-COBOL-V0507--6.PCSI$DESCRIPTION DEC-VAXVMS-COBOL-V0507--6.PCSI$TLB DEC-VAXVMS-COBRTL-V0506--6.PCSI$DESCRIPTION DEC-VAXVMS-COBRTL-V0506--6.PCSI$TLB COBOL_PCSI_REGISTER.COM

The first four files provide binary product information for the product registrations. They constitute a PCSI transition kit for the COBOL compiler and another for the COBRTL. The fifth file, COBOL_PCSI_REGISTER.COM, contains two DCL PRODUCT REGISTER commands, which accomplish the two registrations.

After the successful completion of the kit using VMSINSTAL as shown in the Installation Guide, you can execute the following @ command at the DCL prompt:

$ @COBOL_PCSI_REGISTER

The procedure will ask you twice if you wish to continue: once for COBOL V5.7 and once for COBRTL V5.6. Answer Y to both inquiries. This procedure will take approximately one minute to execute.

Compaq COBOL is now installed on your local system and can be invoked by all users with the COBOL command.

The installation procedure modifies the DCL command table so that the COBOL 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 newly installed version of Compaq COBOL should issue the following command:

$ SET COMMAND/TABLE=SYS$LIBRARY:DCLTABLES [Return]

If Compaq COBOL will be used extensively on your system, you can reduce system overhead and memory requirements by installing it as a shared image by using the OpenVMS Install utility. For more information, see Section 2.4.

3.1 Running the Installation Verification Procedure Separately

The Installation Verification Procedure (IVP) is run at installation. If you want to run the IVP separately to ensure the integrity of installed files, execute the following command procedure:

$ @SYS$COMMON:[SYSTEST.COBOL]COBOL$IVP.COM [Return]

If the IVP fails for any reason, the following messages are displayed:

The Compaq COBOL for OpenVMS VAX V5.n Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for Compaq COBOL for OpenVMS VAX V5.n has failed.

What to Do If the Installation Fails During or After Running the IVP

Some causes of installation failure after running the IVP can produce error messages such as the following:

%CLI-F-SYNTAX, error parsing ...

%COBOL-F-BADVALUE ...

These errors indicate an incompatibility between SYS$SYSTEM:COBOL.EXE and the COBOL command syntax in SYS$LIBRARY:DCLTABLES. To understand the causes of such errors and to correct them, follow this procedure:

1. If either SYS$SYSTEM:COBOL.EXE or SYS$LIBRARY:DCLTABLES exists in SYS$SPECIFIC, the SYS$SPECIFIC file will override the file in SYS$COMMON (where the installation procedure places these files). Ensure that neither of these files exists in SYS$SPECIFIC.
2. Deassign any logical names for COBOL or DCLTABLES.
3. If neither 1 nor 2 applies and you are in the same account on the same node where Compaq COBOL was installed, this error indicates that DCLTABLES was not updated. This error usually occurs when another user had DCLTABLES locked during the installation procedure. To correct the error, you must reinstall Compaq COBOL.

Other causes of installation failure after running the IVP can produce RPC$SHARE error messages. Such errors occur because Compaq COBOL accesses RPC$SHARE indirectly through CDDSHR.EXE (if you have a version of CDD prior to Version 5.0) and usually indicate a problem with the Oracle CDD/Repository installation. To correct these errors, execute the following command procedure:

$ @SYS$STARTUP:CDDSTRTUP.COM [Return]

If you encounter other errors after executing this command procedure, consult the Oracle CDD/Repository documentation for further information or contact your Customer Support Center.

3.2 Customizing Compaq COBOL Error Messages

If you choose to customize the Compaq COBOL message file, the installation procedure copies the Compaq COBOL message file COBOLMSG.MSG into the system directory [SYSUPD]. After the file is copied to the system directory, you can edit COBOLMSG.MSG to customize the error messages that users receive when using Compaq COBOL. Customized messages are often desirable for international users.

There are two prerequisites:

• You must install Compaq COBOL before editing the message file. If you install Compaq COBOL after editing the message file, the software installation's COBOLMSG.MSG file will supersede your revised message file in the [SYSMSG] directory.
• You must have the OpenVMS Message utility installed on your system before editing COBOLMSG.MSG. The edited version of COBOLMSG.MSG must be processed through the Message utility before the file can be accessed by Compaq COBOL.

The following steps explain how to edit the Compaq COBOL messages and install the customized message file on your system:

1. Run the Compaq COBOL installation procedure and answer YES to the question "Do you want to save the COBOL message file for modification [NO]?"
   The installation procedure copies the message file, COBOLMSG.MSG, into the system directory [SYSUPD].
2. Edit the message file in [SYSUPD].
   Each error message appears on a separate line and is enclosed in angle brackets (< >). You can edit the text portion of the error messages, but for Compaq COBOL to correctly identify the error messages, you must not change the following:
   • The 3- to 9-character mnemonic that appears in the first column
   • The sequence in which the error messages appear in the file
   • The severity level of the error message
   • The number, type, and order of the formatted ASCII ouput (FAO) arguments that appear in the message
3. Run the OpenVMS Message utility.
   To translate the new message text into a file that Compaq COBOL can access, process the text file through the Message utility by entering the following command:

   $ MESSAGE COBOLMSG [Return]

   
   The Message utility creates the object module COBOLMSG.OBJ.

4. Enter the LINK command with the /SHARE qualifier to create the shareable image COBOLMSG.EXE:

   $ LINK/SHARE COBOLMSG [Return]

5. Copy COBOLMSG.EXE into the system directory [SYSMSG]:

   $ COPY COBOLMSG.EXE SYS$COMMON:[SYSMSG]/PROT=W:RE [Return]

6. If Compaq COBOL is installed as a known image, you must reinstall COBOLMSG.EXE by entering the following command:

   $ INSTALL REPLACE SYS$MESSAGE:COBOLMSG [Return]

Compaq COBOL will now generate your customized error messages.