HP OpenVMS Systems Documentation

Content starts here

HP Pascal for OpenVMS

Installation Guide

Order Number: AA-PXSPD-TK

January 2005

This guide explains how to install the HP Pascal compiler and related software components on the HP OpenVMS operating system.

Revision/Update Information: This revised manual supersedes the Compaq Pascal Installation Guide for OpenVMS Systems, Version 5.7.

Operating System: OpenVMS I64 Version 8.2 or higher
OpenVMS Alpha Version 6.1 or higher
OpenVMS VAX Version 5.5 or higher

Software Version: HP Pascal for OpenVMS I64 Systems Version 5.9
HP Pascal for OpenVMS Alpha Systems Version 5.9
HP Pascal for OpenVMS VAX Systems Version 5.8

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.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Printed in the US




This guide describes how to install HP Pascal on the OpenVMS operating system.

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

Intended Audience

This guide is intended for the system manager who installs HP Pascal.

Document Structure

This guide contains the following chapters:

  • Chapter 1 describes the hardware and software requirements for
    HP Pascal and related procedures that you complete before the installation.
  • Chapter 2 describes the HP Pascal installation procedure.
  • Chapter 3 describes the HP Pascal Installation Verification Procedure (IVP) and any postinstallation procedures you must complete to use
    HP Pascal.

Related Documents

In addition to this guide, the HP Pascal documentation set includes the following books:

  • HP Pascal for OpenVMS User Manual
  • HP Pascal for OpenVMS Language Reference Manual
For general information on OpenVMS system management, see the OpenVMS operating system documentation set.

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


1 This book has been archived, and is available on the OpenVMS documentation CD-ROM.

Reader's Comments

HP welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet openvmsdoc@hp.com
Postal Mail Hewlett-Packard Company
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

HP Pascal Home Page

You can access the HP Pascal home page at:



The following product names may appear in this manual:

  • HP OpenVMS Industry Standard 64 for Integrity Servers
  • OpenVMS I64
  • I64

All three names---the longer form and the two abbreviated forms---refer to the version of the OpenVMS operating system that runs on the Intel Itanium architecture.

The following typographic conventions might be used in this manual:

Ctrl/ x A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.
[Return] In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)

In the HTML version of this document, this convention appears as brackets, rather than a box.

... A horizontal ellipsis in examples indicates one of the following possibilities:
  • Additional optional arguments in a statement have been omitted.
  • The preceding item or items can be repeated one or more times.
  • Additional parameters, values, or other information can be entered.
A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( ) In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one.
[ ] In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.
| In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.
{ } In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.
bold type Bold type represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.
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).
UPPERCASE TYPE Uppercase type indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
- A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.

Chapter 1
Preparing to Install HP Pascal

This chapter discusses the preparations and requirements necessary for installing HP Pascal.

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 Pascal provides online release notes, which are copied to the following file during installation:

HP recommends that you read the release notes before proceeding with the installation. For information on accessing the online release notes, see Section 2.1.

Your distribution kit includes a "Read First" cover letter. Please read this cover letter for information that you should know before installing HP Pascal. This information may not be included in this installation guide or in the release notes.

1.1 Required Operating System Components

HP Pascal requires:

  • OpenVMS I64 Version 8.2 or higher
  • OpenVMS Alpha Version 6.1 or higher
  • OpenVMS VAX Version 5.5 or higher

Future HP Pascal releases may require higher versions of the OpenVMS operating system, as described in the online release notes or the Read First cover letter for your operating system.

The OpenVMS operating system comes with a variety of support options or components.

1.2 License Registration

You must register the HP Pascal license through the OpenVMS License Management Facility (LMF) in accordance with the license agreement signed by your site. The license registration information you need is contained in the Product Authorization Key (PAK) that is shipped with HP Pascal if you ordered the license and media together; otherwise, the PAK is shipped separately to a location based on your license order. The PAK is a paper certificate that contains information about the license to run a particular piece of software.

If you are installing HP Pascal as an update on a node or cluster that is licensed for this software, you have already completed the License PAK registration requirements.

During the installation, the system asks whether you have registered the HP Pascal license and loaded the appropriate PAK. Before you start the installation, you must register and load your license for HP Pascal to be able to run the Installation Verification Procedure (IVP) and for users to be able to run HP Pascal.

To register a license, first log in to the system manager's account (username: 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 License PAK information.
For information on using LMF, see the HP OpenVMS License Management Utility Manual.

1.3 Multiple Version Support

HP Pascal provides support for using multiple versions of the compiler on the same OpenVMS system.

During installation, you have the opportunity to save the current version of the compiler for later use. If chosen, the installation copies the current compiler before installing the new compiler.

The kit provides three command files to display and control which HP Pascal compiler is used.

  • SYS$SYSTEM:PASCAL$SHOW_VERSIONS.COM is used to display all HP Pascal compilers saved on the system and their version numbers. It also shows the current settings for process, job, group, and system-wide compiler settings. This command file has no parameters.
  • SYS$SYSTEM:PASCAL$SET_VERSION.COM is used to select a HP Pascal compiler other than SYS$SYSTEM:PASCAL.EXE. If invoked without parameters, it displays the currently available compilers and asks for a file name to use for the process-wide compiler setting. It has 2 optional parameters. The first parameter can be PROCESS, JOB, GROUP, or SYSTEM. This selects the level of visibility for the selected compiler. The second parameter can be a file name to use instead of being prompted for a file. This allows you to place a compiler selection in a LOGIN.COM or some other command file. All saved compilers are located in SYS$SYSTEM:.
  • SYS$SYSTEM:PASCAL$DEFAULT_VERSION.COM is used to select the default HP Pascal compiler when SYS$SYSTEM:PASCAL$SET_VERSION.COM has not be used. The installation always provides a new SYS$SYSTEM:PASCAL.EXE and copies existing compilers. You can use this command file to select one of the saved compilers to be SYS$SYSTEM:PASCAL.EXE and rename the existing SYS$SYSTEM:PASCAL.EXE for later use through SYS$SYSTEM:PASCAL$SET_VERSION.COM.

1.4 Installation Procedure Requirements

The installation of HP Pascal takes approximately 5 to 45 minutes, depending on your system configuration.

1.4.1 Installation Account Privileges and Disk Space

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



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

HP Pascal requirements for free disk storage space are different during installation and after installation. Table 1-1, Table 1-2, and Table 1-3 summarize the storage requirements for the three operating systems.

Table 1-1 Number of Blocks Required for OpenVMS I64 Systems
Kit During
HP Pascal V5.9 for
OpenVMS I64 systems
45,000 40,500
HP Pascal Run-Time Library for
OpenVMS I64 systems 1
1,100 1,100
HP Pascal STARLET files 15,000 15,000
HP Pascal examples 150 150

1Only when that kit is newer than the installed version.

Table 1-2 Number of Blocks Required for OpenVMS Alpha Systems
Kit During
HP Pascal V5.9 for
OpenVMS Alpha systems
25,000 21,000
HP Pascal Run-Time Library for
OpenVMS Alpha systems 1
500 500
HP Pascal STARLET files 15,000 15,000
HP Pascal examples 150 150

1Only when that kit is newer than the installed version.

Table 1-3 Number of Blocks Required for OpenVMS VAX Systems
Kit During
HP Pascal V5.8 for
OpenVMS VAX systems
3,500 3,000
HP Pascal STARLET files 11,500 10,000
HP Pascal examples 150 150

1Only when that kit is newer than the installed version.

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


1.4.2 System Parameters

Installing HP Pascal 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:PASCAL.EXE was previously installed as a shared image, as follows:

  • If not previously installed as a shared image: one global section and a sufficient number of contiguous free global pagelets to contain the file SYS$LIBRARY:DCLTABLES.EXE
  • If previously installed as a shared image or will be subsequently installed with the PASCAL$STARTUP command file ( Section 3.4.2):
    • Global sections: six on OpenVMS I64 systems, three on OpenVMS Alpha systems, and two on OpenVMS VAX systems
    • A sufficient number of contiguous free global pagelets to contain the file SYS$LIBRARY:DCLTABLES.EXE:
      32,000 additional global pagelets on OpenVMS I64 systems
      10,000 additional global pagelets on OpenVMS Alpha systems
      1,500 additional global pagelets on OpenVMS VAX systems
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 the Values for GBLPAGES and GBLSECTIONS

To install and run HP Pascal, you must have sufficient free contiguous global pagelets and global sections. To determine the number of global pagelets required by SYS$LIBRARY:DCLTABLES.EXE, enter the following DCL command:

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

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


If the number of free global pagelets or global sections is less than the required value (see Section 1.4.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 pagelets or free global sections to install HP Pascal, 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:


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, insert a line in the file that includes both the name of the parameter and its value. For example:

WSMAX = 1024

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



When you set the page file quota, do not use a value that exceeds the amount of page file space available on the system.

After you make all your changes, exit from the editor and then execute the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt to recalculate your system parameters and to reboot the system:


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

AUTOGEN 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.

Next Contents