HP OpenVMS Systems

C Programming Language
Content starts here



Installation Guide for
OpenVMS Alpha Systems

Order Number: AA-PUP1J-TE

November 2005

This guide contains instructions for installing HP C on OpenVMS Alpha systems.

This guide applies to HP C Version 7.1 for OpenVMS Alpha, and all subsequent point releases for Version 7.0.

Revision/Update Information: This is a revised manual replacing Order Number AA-PUP1H-TE

Operating System and Version: OpenVMS Alpha Version 7.3-2 or higher.
Future maintenance releases might require higher versions.

Software Version: HP C Version 7.1 for OpenVMS Alpha.

Hewlett-Packard Company
Palo Alto, California

© Copyright 2005 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP 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.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

This document is available on CD-ROM.

This document was prepared using DECdocument, Version V3.3-1e.



This guide describes how to install HP C on Alpha processors running the OpenVMS operating system. It is intended for system managers.

Keep this guide with your distribution kit. You will need it to install maintenance updates or to reinstall HP C for any other reason.

You can send comments or suggestions regarding this guide or any HP C document by sending electronic mail to the following Internet address:

Intended Audience

The audience for this guide is the system manager who installs HP C software.

Structure of this Document

This guide contains the following chapters and appendixes:

  • Chapter 1 describes how to prepare for HP C installation.
  • Chapter 2 describes the procedure to install HP C.
  • Chapter 3 describes what to do after installing HP C.
  • Appendix A shows sample installations.
  • Appendix B lists files installed.
  • Appendix C describes how to recover from errors.

Manuals in the HP C Documentation Set

In addition to this guide, the HP C for OpenVMS Alpha documentation set includes the following books:

  • HP C Language Reference Manual
  • HP C User's Guide for OpenVMS Systems
  • HP C Run-Time Library Reference Manual for OpenVMS Systems

The Read Before Installing HP C Version 7.n for OpenVMS Alpha Systems letter is provided along with this installation guide on the CD media.

Related Manuals

For information on OpenVMS system management, see the following documents in the OpenVMS documentation set:

  • HP OpenVMS System Manager's Manual
  • Guide to Maintaining a VMS System
  • HP OpenVMS License Management Utility Manual
  • Guide to OpenVMS Performance Management

For help understanding OpenVMS system error messages, see the OpenVMS System Messages and Recovery Procedures Reference Manual or the online HELP/MESSAGE facility.


Table 1 lists the conventions used in this guide.

Table 1 Conventions Used in this Guide
Convention Meaning
UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, the name of a file protection code, or the abbreviations for a system privilege.
$ @SYS$UPDATE:VMSINSTAL In interactive examples, prompts and displayed text appear in a monospace font. User input appears in bold monospace font.
italic type Italic type indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).
[Return] In interactive examples, a key name is shown enclosed to indicate that you press a key on the keyboard.
[Ctrl/x] In interactive examples, a sequence such as [Ctrl/x] indicates that you must hold down the key labeled Ctrl while you press another key; for example, Ctrl/C or Ctrl/Z.
[YES] Square brackets indicate that the enclosed item is a default value in an installation prompt. Also, square brackets serve as delimiters for a directory name in a file specification.

In this manual, some version numbers are given as Vn.n. When you install HP C, the actual version number appears on your screen.

Chapter 1
Preparing for HP C for OpenVMS Alpha Installation

This chapter describes the preparations and requirements necessary for installing HP C for OpenVMS Alpha Systems.

This guide applies to Version 7.1 of HP C for OpenVMS Alpha Systems and all subsequent maintenance releases up to the next release of the product that includes an updated installation guide.

Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your HP representative.

HP C provides online release notes. Reading the release notes before proceeding with the installation is strongly recommended. For information on accessing the online release notes, see Section 2.1, step 6.

The release notes contain installation-related notes and a summary of technical changes, known problems, restrictions, and incompatibilities.

1.1 Hardware Requirements

You can install HP C on any Alpha processor system capable of running OpenVMS Alpha Version 7.3-2 or higher. See the OpenVMS Operating System's Software Product Description (SPD 25.01.nn) for details.

1.2 Required Operating System Components

HP C Version 7.1 for OpenVMS Alpha Systems requires OpenVMS Alpha Version 7.3-2 or higher.

Future HP C releases may require higher versions of the OpenVMS operating system, as described in the release notes or the cover letter.

The OpenVMS Alpha operating system comes with a variety of support options (or components). Components include such features as networking and RMS journaling. To use HP C, your system should be running a version of OpenVMS Alpha that includes that includes the base component and the following other components:

  • Programming support
  • Utilities

For a complete list of the required components, see the HP C Software Product Description (SPD).

1.3 Optional Software

You can use the following optional OpenVMS software with HP C:

  • HP Language-Sensitive Editor/Source Code Analyzer (LSE/SCA). Support for C requires that LSE be installed before the compiler is installed.
  • HP Test Manager (DTM)
  • HP Performance and Coverage Analyzer (PCA)
  • HP Code Management System (CMS)
  • HP Module Management System (MMS)

1.4 License Registration

Before you install and run HP C Version 7.1 on a newly licensed node or cluster, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF).

The specific LMF product names used by HP C are:

  • C: Unlimited or Personal-Use License
  • C-USER: Concurrent-Use License

The HP C compiler accepts a C(-USER) PAK. The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing HP C as an update on a node or cluster already licensed for this software, you have already completed the License PAK registration requirements.

If you are installing prerequisite or optional software along with HP C, review the License PAK status and install the License PAKs for any prerequisite or optional software before you install HP C.

You must register and load your license for HP C before you start the installation in order to run the Installation Verification Procedure (IVP) and use the software.

To register a license under OpenVMS, log in to a privileged account, such as the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration:

  • Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK.
  • At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to the License PAK information.

If you plan to use HP C on more than one node in a cluster, you will need to perform a license load on the other nodes after you complete this installation. See Section 3.3.

For complete information on using the LMF, see the VMS License Management Utility Manual or the online HELP LICENSE utility.

1.5 Installation Procedure Requirements

After you have registered and loaded the license PAK and read the appropriate parts of this installation guide, the installation takes approximately 5 to 15 minutes, depending on your type of media, your system configuration, and the kit components chosen.

1.5.1 Installation Account Privileges and Disk Space

To install HP C, you must be logged in to an account that has the SETPRV privilege or at least the following privileges enabled:


VMSINSTAL turns off BYPASS privilege at the start of the installation.

Table 1-1 lists the storage requirements for free disk storage space. You can also install the C documentation in .ps, .txt, and .html formats. The installation default is to not install the documentation, but if you do, note the additional disk space required.

Table 1-1 Disk Space Requirements
Kit Blocks During Installation Blocks After Installation
Compiler only 150,000 100,000
Compiler and documentation 250,000 160,000

These counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options.

To determine the number of free disk blocks on the current system disk, enter the following DCL command:


1.5.2 System Parameters

Installing HP C requires certain system parameter settings.

The minimum number of free global pagelets (512-byte subpage unit) and global sections needed for the installation depends on whether SYS$SYSTEM:DECC$COMPILER.EXE was previously installed as a shared known image:

  • If not previously installed as shared, 1 global section and a sufficient number of contiguous free global pagelets to contain the file SYS$LIBRARY:DCLTABLES.EXE
  • If previously installed as shared, 2 global sections and approximately 10,000 contiguous free global pagelets plus a sufficient number of contiguous free global pagelets to contain the file SYS$LIBRARY:DCLTABLES.EXE

These values represent the number of free global pagelets and global sections required for the installation, not the total number you need to run your system and other software.


If you do not ensure that your system has the necessary global pagelets and global section SYSGEN parameters for the installation, the DCL tables can become corrupted in some situations. Calculating Values for GBLPAGES and GBLSECTIONS

To install and run HP C, you must have sufficient free global pagelets and global sections.

Enter the following DCL command to determine the number of global pagelets required by SYS$LIBRARY:DCLTABLES.EXE:


This command returns the size (in blocks) of SYS$LIBRARY:DCLTABLES.EXE. As an approximation, use this figure as the number of global pagelets needed for the file.

You can use the WRITE command with the F$GETSYI lexical function to find the number of free contiguous global pagelets and free global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT):


If the value of free global pagelets or global sections is less than the required value (see Section 1.5.2), you must increase the system parameter setting.

Section describes the procedures for increasing these values using AUTOGEN. Changing System Parameter Values with AUTOGEN

If you do not have enough free global pages or free global sections to install HP C, you can do either of the following:

  • Delete an existing known image using the OpenVMS INSTALL utility.
  • Use the AUTOGEN command procedure to increase the GBLPAGES or GBLSECTIONS system parameters.

AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the following file:


Use an editor to access the file.

To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value.

To add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example:

WSMAX = 8096

To modify incremental parameters such as GBLPAGES and GBLSECTIONS, use the ADD_ prefix. The following example increases the global page setting by 2000:


After you make all your changes, exit from the editor, then execute the AUTOGEN procedure to recalculate your system parameters and reboot the system:


When you specify REBOOT, AUTOGEN does an automatic system shutdown and then reboots the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect.

The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line.

For more information about using AUTOGEN, see the OpenVMS System Management Subkit.

1.5.3 VMSINSTAL and Installation Requirements

When you invoke VMSINSTAL, it checks the following:

  • Whether you have set your default device and directory to SYS$UPDATE
  • Whether you are logged in to a privileged account
  • Whether you have adequate quotas for installation (see Section
  • Whether DECnet is running
  • Whether any users are logged in to the system

If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, type NO or press Return. Then correct the problem and restart the installation. VMSINSTAL Installation Process Requirements

VMSINSTAL requires that the installation account have the following minimum quotas:

ASTLM = 100
BIOLM = 100
DIOLM = 100
ENQLM = 300
FILLM = 300 Modifying Process Quotas

Use the OpenVMS Authorize Utility to change the process quotas for the installation account in the user authorization file (UAF). (Some sites may restrict the use of the OpenVMS Authorize Utility to certain accounts or people.) For example, to change the BIOLM quota for the account-name installation account, you might enter the following command sequence:

UAF> MODIFY account-name /BIOLM = 100
UAF> SHOW account-name

After the quotas for the installation account have been changed, log out of the installation account and log in again for the new quotas to take effect. You can then proceed with the installation.

For more information on modifying account quotas, see the description of the AUTHORIZE utility in the OpenVMS System Management Subkit.

1.5.4 Backing Up Your System Disk

At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. You should do a system disk backup before installing any software.

Use the backup procedures established at your site. For details on performing a system disk backup, see the section on the BACKUP utility in the OpenVMS System Management Subkit.

1.6 Installing and Using Multiple Compiler Versions

HP C Version 6.4 and higher provides support for installing and using multiple versions of the compiler on the same node.

During installation of Version 7.n, if a Version 6.n of the compiler is already installed, you have the opportunity to preserve that compiler rather than overwrite it. If you choose to preserve the currently installed compiler, you are then given a choice to keep the currently installed compiler as the system default and install the new compiler as an alternate.

By default, the currently installed system compiler is preserved by making it an alternate compiler and installing the new compiler as the system default. Users can make the choice to use an alternate compiler instead of the installed system compiler by running a command procedure that changes the behavior of the cc command for the process that invokes it.

1.6.1 Displaying and Selecting the Compiler Version

This kit provides two command procedures to display and control which HP C compiler is used by a process:

    This procedure displays the HP C compilers available on the system, along with their version numbers. It also displays which compiler is the default for the current process. The procedure takes an optional version-number argument. Examples:

    $ @sys$system:decc$show_versions.com 
    The following HP C compiler(s) are available in 
    Filename                      Version 
    DECC$COMPILER.EXE             V6.4-005 
    DECC$COMPILER_T06_04-002.EXE  T6.4-002 
    DECC$COMPILER_T06_04-001.EXE  T6.4-001 
    DECC$COMPILER_V06_00-001.EXE  V6.0-001    Process Default 
    DECC$COMPILER_V06_02-008.EXE  V6.2-008 

    $ @sys$system:decc$show_versions.com V6.0 
    The following HP C compiler(s) are available in 
    Filename                      Version 
    DECC$COMPILER_V06_00-001.EXE  V6.0-001    Process Default 
    This procedure sets up process logicals that point to an alternate HP C compiler in SYS$SYSTEM, or it removes the process logicals to revert to using the default system compiler. The procedure takes one argument, a version number or the keyword SYSTEM. If no arguments are specified you are prompted for them. The SYSTEM argument selects the installed system compiler, which is the one displayed with the filename DECC$COMPILER.EXE in the output of decc$show_versions.com. Alternate compilers are shown in that output with their version number appended to the simple filename; for example, the version 6.2-008 compiler is shown as DECC$COMPILER_V06_02-008.EXE.
    To select a compiler, pass a full ident string or enough of the ident string to be unique. For example: to select the V6.2-008 compiler from the previous list, pass V6.2-008 or V6.2 to the decc$set_version.com routine. However, to select a 6.4 compiler, a full ident string is required to distinguish between the V6.4-005, T6.4-001, and the T6.4-002 compiler:

    @sys$system:decc$set_version.com V6.2-008 
    @sho logical DECC$* 
      "DECC$COMPILER" = 
      "DECC$MSG_SHR" = 
    $ @decc$set_version.com 6.4 
    The following 6.4 HP C compiler(s) are available in 
    Filename                      Version 
    DECC$COMPILER.EXE             V6.4-005 
    DECC$COMPILER_T06_04-001.EXE  T6.4-001 
    DECC$COMPILER_T06_04-002.EXE  T6.4-002 
    Ambiguous version number, please be specify a full version number, ex: V6.4-005 
    Version number : V6.4-005 
    $ sho logical DECC$COMPILER 
    $ sho logical DECC$msg_shr 

    When this procedure is run in a process, subsequent cc commands invoke the selected compiler version (until the procedure is run again). The process-level logicals used do not affect other processes or users on the system.

Next Contents