After Compaq COBOL is installed, it 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 COBOL command or the newly updated version of the COBOL command must log out and log in again, or use the following DCL command:

$ SET COMMAND /TABLE=SYS$LIBRARY:DCLTABLES

The following tasks can be performed after Compaq COBOL is installed:

• Running the Installation Verification Procedure separately
• Customizing the Compaq COBOL messages
• Making Compaq COBOL usable on an OpenVMS Cluster System
• Setting user account privileges
• Installing Compaq COBOL as a shared image
• Running the REFORMAT utility

The Installation Verification Procedure (IVP) runs automatically during installation of the COBOL compiler. It requires the installation of the COBOL compiler on your system. If you want to run the IVP separately to ensure the integrity of installed files should system problems occur, in a privileged account use the following command procedure:

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

3.2 Customizing Compaq COBOL Error Messages

The PCSI installation automatically copies the Compaq COBOL message file, COBOL$MSG.MSG, into the system directory [SYSUPD]. You can edit COBOL$MSG.MSG to customize the error messages that users receive when using Compaq COBOL. Customized messages are often desirable for international users.

You must install Compaq COBOL before editing the message file. If you install Compaq COBOL after editing COBOL$MSG.MSG, the software installation will supersede the revised message file in the [SYSMSG] directory. Also, you must have the OpenVMS Message utility installed on your system before editing COBOL$MSG.MSG. The edited version of COBOL$MSG.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. Edit the message file.
   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 errors, 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 output (FAO) arguments that appear in the message
2. Run the OpenVMS Message utility.
   To translate the new message text into a file that Compaq COBOL can access, run the text file through the Message utility by entering the following command:

   $ MESSAGE COBOL$MSG

   
   The Message utility creates the object module COBOL$MSG.OBJ.

3. Enter the LINK command with the /SHARE qualifier to create the shareable image COBOL$MSG.EXE:

   $ LINK/SHARE COBOL$MSG

4. Install COBOL$MSG.EXE in the system directory [SYSMSG]:

   $ COPY COBOL$MSG.EXE SYS$COMMON:[SYSMSG]/PROT=W:RE

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

   $ INSTALL REPLACE SYS$MESSAGE:COBOL$MSG

Compaq COBOL will now generate your customized error messages.

3.3 Making Compaq COBOL Usable on an OpenVMS Cluster System

If you want to run Compaq COBOL on multiple nodes of a VMScluster, first check to see that you have the appropriate software license (see Section 1.2). Then, perform the following steps after you install Compaq COBOL:

1. Issue the LICENSE LOAD command to activate the license on each node in the VMScluster on which Compaq COBOL is to be executed.
2. Use the OpenVMS System Management utility (SYSMAN) to execute a set of commands on all cluster nodes, whether or not the nodes are licensed to use Compaq COBOL; failure to do so may cause unexpected errors for users.

   Note If you are using a mixed-architecture (VAX and Alpha) heterogeneous cluster, before executing these commands, make sure the appropriate logical names have been set to define the scope of the SYSMAN DO commands. For more information, see the OpenVMS system management documentation.

   
   While logged in as SYSTEM, or as another user name that has the SETPRV privilege or the CMKRNL and SYSPRV privileges, use the SYSMAN utility to update the version of DCLTABLES.EXE available, as follows:

   $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SYSTEM will be used on nonlocal nodes SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE %SYSMAN-I-OUTPUT, command execution on node NODE1 %SYSMAN-I-OUTPUT, command execution on node NODE2

   
   The SYSMAN utility will cause each DO command to be executed on all nodes of the local cluster.

3. If Compaq COBOL is installed as a known image, then also do the following:

   SYSMAN> DO INSTALL REPLACE SYS$SYSTEM:COBOL.EXE %SYSMAN-I-OUTPUT, command execution on node NODE1 %SYSMAN-I-OUTPUT, command execution on node NODE2

4. If the Compaq COBOL messages file is installed as a known image, then also do the following:

   SYSMAN> DO INSTALL REPLACE SYS$MESSAGE:COBOL$MSG.EXE %SYSMAN-I-OUTPUT, command execution on node NODE1 %SYSMAN-I-OUTPUT, command execution on node NODE2

5. If the Compaq COBOL RTL installation was performed, then complete the following steps:

   SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DEC$COBRTL.EXE %SYSMAN-I-OUTPUT, command execution on node NODE1 %SYSMAN-I-OUTPUT, command execution on node NODE2 SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:LIBOTS2.EXE %SYSMAN-I-OUTPUT, command execution on node NODE1 %SYSMAN-I-OUTPUT, command execution on node NODE2

6. Finally, exit from SYSMAN.

   SYSMAN> EXIT $

To use Compaq COBOL, each user account must have at least TMPMBX and NETMBX privileges. Use the OpenVMS Authorize utility to determine whether users have the privileges they require.

3.5 Installing Compaq COBOL as a Shared Image

If you expect Compaq COBOL to be used extensively on your system, you can reduce the system overhead and memory requirements by installing it as a shared image. To install Compaq COBOL as a shared image on a system that is currently running, use the OpenVMS Install utility (INSTALL). It is recommended that you install Compaq COBOL as shared on a system that has been rebooted recently, because the available space in the global page table is less likely to be fragmented. Invoke the OpenVMS Install utility from a privileged account and install Compaq COBOL as a shared image:

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

Add the following line to the appropriate system startup command file so that Compaq COBOL is available as a shared image each time the system is started:

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

The default operating system startup command file, for example, is SYS$MANAGER:SYSTARTUP_VMS.COM (previously named SYSTARTUP_V5.COM). If your site has modularized the system startup procedure using multiple command files, add the lines to the correct file.

To install the message file, use the following commands:

$ INSTALL ADD SYS$MESSAGE:COBOL$MSG.EXE

3.6 REFORMAT Utility

The PCSI installation automatically includes installation of REFORMAT.EXE, the REFORMAT utility. It is ready to run.

This appendix contains a sample log of an installation on the OpenVMS Alpha operating system, Version 7.1-2 and higher; a sample log of an installation verification (IVP); and a sample log of a deinstallation of the RTL and the compiler.

A.1 Installation of the Run-Time Library and the Compiler on OpenVMS Alpha

$ PRODUCT INSTALL COBRTL/VERSION=2.8-670B/SOURCE=SYS$UPDATE: The following product has been selected: DEC AXPVMS COBRTL V2.8-670B Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS COBRTL V2.8-670B: COBRTL for Compaq COBOL for OpenVMS Alpha Systems Copyright 2002 by Compaq Computer Corporation. This software is the product of Compaq Computer Corporation. No PAKs are used by this COBRTL product. Do you want the defaults for all options? [YES] Do you want to review the options? [NO] Execution phase starting ... The following product will be installed to destination: DEC AXPVMS COBRTL V2.8-670B DISK$YYYYYYSYSDSK:[VMS$COMMON.] The following product will be removed from destination: DEC AXPVMS COBRTL V2.7-603B DISK$YYYYYYSYSDSK:[VMS$COMMON.] Portion done: 0%...30%...50%...70%...90%...100% The following product has been installed: DEC AXPVMS COBRTL V2.8-670B Layered Product The following product has been removed: DEC AXPVMS COBRTL V2.7-603B Layered Product $ PRODUCT INSTALL COBOL /VERSION=2.8-1286/SOURCE=SYS$UPDATE: The following product has been selected: DEC AXPVMS COBOL V2.8-1286 Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS COBOL V2.8-1286: Compaq COBOL for OpenVMS Alpha Systems Copyright 2002 by Compaq Computer Corporation. This software is the product of Compaq Computer Corporation. A valid Product Authorization Key (PAK) is required. Do you want the defaults for all options? [YES] Do you want to review the options? [NO] Execution phase starting ... The following product will be installed to destination: DEC AXPVMS COBOL V2.8-1286 DISK$YYYYYYSYSDSK:[VMS$COMMON.] The following product will be removed from destination: DEC AXPVMS COBOL V2.7-1209 DISK$YYYYYYSYSDSK:[VMS$COMMON.] Portion done: 0%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS COBOL V2.8-1286 Layered Product The following product has been removed: DEC AXPVMS COBOL V2.7-1209 Layered Product %PCSI-I-IVPEXECUTE, executing test procedure for DEC AXPVMS COBOL V2.8-1286 ... %PCSI-I-IVPSUCCESS, test procedure completed successfully

A.2 Installation Verification (IVP) Run Separately

 
$ @SYS$TEST:COBOL$IVP.COM
 
 Copyright 2002 Compaq Computer Corporation 
 
 COMPAQ Registered in U.S. Patent and Trademark Office. 
 
 Confidential computer software. Valid license from Compaq required for 
 possession, use or copying. Consistent with FAR 12.211 and 12.212, 
 Commercial Computer Software, Computer Software Documentation, and 
 Technical Data for Commercial Items are licensed to the U.S. Government 
 under vendor's standard commercial license. 
 
        Successful test of Compaq COBOL V2.8-1286 
 
$ 

A.3 Removal (Deinstallation) of the Run-Time Library and the COBOL Compiler

 
$ PRODUCT REMOVE COBRTL
 
The following product has been selected: 
    DEC AXPVMS COBRTL V2.8-670B            Layered Product 
 
Do you want to continue? [YES] 
 
The following product will be removed from destination: 
    DEC AXPVMS COBRTL V2.8-670B            DISK$AFSCOBSYSDSK:[VMS$COMMON.] 
 
Portion done: 0%...10%...100% 
 
The following product has been removed: 
    DEC AXPVMS COBRTL V2.8-670B            Layered Product 

$ PRODUCT REMOVE COBOL The following product has been selected: DEC AXPVMS COBOL V2.8-1286 Layered Product Do you want to continue? [YES] The following product will be removed from destination: DEC AXPVMS COBOL V2.8-1286 DISK$AFSCOBSYSDSK:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...100% The following product has been removed: DEC AXPVMS COBOL V2.8-1286 Layered Product

This appendix provides information to help you with failures or errors that might occur during product installation or product use.

B.1 Failures During Compaq COBOL and Run-Time Library Installations

If PCSI detects any problems during installation, it notifies you and asks if you want to continue the installation.

The following PCSI messages are issued if the PCSI product kit is not found in the specified directory:

$ PRODUCT INSTALL /SOURCE=device:[directory] %PCSIUI-I-NOMATCH, no products found matching: COBOL %PCSIUI-E-NOPROD, no products found on which to perform this operation %PCSIUI-E-ABORT, fatal error encountered - operation terminated

The following PCSI and RMS messages are issued if the PCSI product kit is not found in the specified directory and you have defined the logical name PCSI$SOURCE:

$ PRODUCT INSTALL /SOURCE=device:[directory] %PCSI-E-OPENIN, error opening PCSI$SOURCE:[SYSUPD]*-*-*-%%%%%-*-*.PCSI*; as input -RMS-F-DEV, error in device name or inappropriate device type for operation %PCSI-E-S_OPFAIL, operation failed %PCSIUI-E-ABORT, fatal error encountered - operation terminated

The following PCSI messages are issued when the installation and the IVP test procedure execute properly:

$ PRODUCT INSTALL /SOURCE=device:[directory] . . . The following product has been installed: DEC AXPVMS COBOL V2.8-1286 . . . %PCSI-I-EXETSTOK, end of test procedure; completed with no errors

The following PCSI messages are issued when the COBOL installation fails only because the IVP test procedure fails.

$ PRODUCT INSTALL /SOURCE=device:[directory]

The PRODUCT INSTALL fails, with the following messages:

Portion Done: 10%...30%...40%...70%...80%...90%...100% %PCSI-I-PRCOUTPUT, output from subprocess follows... %LICENSE-F-NOAUTH, DEC COBOL use is not authorized on this node -LICENSE-F-NOLICENSE, no license is active for this software product -LICENSE-I-SYSMGR, please see your system manager %SYSTEM-F-ABORT, abort

The IVP test procedure fails, with the following messages:

%PCSI-E-EXETSTFAIL, end of test procedure; completed with errors; status returned from DCL follows -SYSTEM-F-ABORT, abort %PCSI-E-OPFAILED, operation failed Terminating is strongly recommended. Do you want to terminate? [YES] y

The following PCSI messages are issued when the installation fails and you ask PCSI to force completing the installation. In this case a PCSI "execute" statement failed. It is recommended that you terminate the installation in response to the question "Do you want to terminate?" If this message appears under the current setup, something has gone seriously wrong with the installation. Two possibilities are:

• One or more necessary files are missing from the kit.
• A delete of modules in the STARLET.OLB library has failed in the COBRTL installation, causing the succeeding PCSI update step to fail.

If you answer YES or take the default on the question, the installation will be backed out if it has gone less than 100%, and you will see the $ system prompt on the screen.

$ PRODUCT INSTALL COBRTL/SOURCE=device:[directory] %PCSI-I-PRCOUTPUT, output from subprocess follows... %SYSTEM-F-ABORT, abort Portion Done: 10% %PCSI-E-EXEFAIL, execute statement failed; status returned from DCL follows -SYSTEM-F-ABORT, abort %PCSI-E-OPFAILED, operation failed Terminating is strongly recommended. Do you want to terminate? [YES] n Portion Done: 30%...40%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS COBRTL V2.8-603 The following product has been removed: DEC AXPVMS COBRTL V2.8-603 %PCSIUI-I-COMPWERR, operation completed after explicit continuation from errors

B.2 Problems During Compaq COBOL Use

This section describes problems that might occur when you use Compaq COBOL.

B.2.1 Run-Time Library Mismatch

The system issues a severe error message if there is a mismatch in RTL versions between the compiled program and the RTL installed on the system where the program is run. In this situation, the program exits after the message is issued.

B.2.2 Other Problems

If you encounter a problem while using Compaq COBOL, see the section on Troubleshooting Tips in the Release Notes. If the problem is unresolved, report it to Compaq. If you have a Software Product Services Support Agreement, contact your Compaq Customer Support Center (CSC), either by telephone or using the electronic means provided with your support agreement (such as DSNlink). The CSC provides telephone support for high-level advisory and remedial assistance. When you initially contact the CSC, please indicate the following:

• The name (OpenVMS Alpha) and the version number of the operating system you are using
• The product name (Compaq COBOL) and the version number of Compaq COBOL you are using
• The hardware system you are using, such as a model number
• A very brief description of the problem (one sentence if possible)
• How critical the problem is

When you submit information electronically or are speaking on the phone to the appropriate Compaq COBOL support specialist, you can provide more detailed information. The information should include the specific commands used to compile and link the program, the error messages displayed, and relevant detailed information (possibly including source program listings). Please attempt to narrow the cause of the problem to a specific module or lines of code.

CSC personnel may ask for additional information, such as listings of any command files, INCLUDE and COPY files, relevant data files, and so forth. If the program is longer than 50 lines, submit a copy of it electronically or provide machine-readable media (diskette or magnetic tape).

Previous

Contents

Contents