DEC C

DEC C

Installation Guide for
OpenVMSAlpha Systems

Order Number: AA--PUP1D--TE


May 1996

This guide contains instructions for installing DEC C on an Alpha processor system running the OpenVMS operating system.

Revision/Update Information: This revised manual supersedes the DEC C Installation Guide for OpenVMS Alpha Systems, (Order No. AA--PUP1C--TE)

Operating System and Version: OpenVMS Alpha Version 6.1 or higher.

Software Version: DEC C for OpenVMS Alpha Systems, Version 5.3 or higher.

Digital Equipment Corporation
Maynard, Massachusetts


First Printing, November 1992
Revised, May 1994 Revised, May 1995 Revised, May 1996

The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document.

The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license.

Copyright ©1992, 1994, 1995, 1996

The following are trademarks of Digital Equipment Corporation: DEC, DECnet, DECset, DECsupport, Digital, OpenVMS, VAX, VAXcluster, VAX DOCUMENT, VMS, VMScluster, and the DIGITAL logo.

ZK6139

This document is available on CD-ROM.

This document was prepared using VAX DOCUMENT, Version V3.2-1a.

Contents


Preface

Purpose of this Guide

This guide describes how to install DEC C on Alpha processors running the OpenVMS operating system.

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

You can send comments or suggestions regarding this guide or any DEC C document by filling out one of the Reader's Comments forms at the back of this guide or by sending electronic mail to the following Internet address:

decc_docs@casdoc.enet.dec.com

Intended Audience

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

Structure of this Document

This guide contains the following chapters and appendix:

Manuals in the DEC C Documentation Set

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

The Read Before Installing DEC C Version 5.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:

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

Conventions

Table 1 lists the conventions used in this guide.

Table 1 Conventions Used in this Guide
Convention Meaning
VMS systems Refers to OpenVMS Alpha systems and OpenVMS VAX systems unless otherwise specified.
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
fprintf function
auto storage class
Monospaced type identifies displayed or typed text, language keywords, and the names of OpenVMS and DEC C Run-Time Library routines.
boldface monospace text Boldface monospace text represents user input in interactive examples.
$ The dollar sign is used to indicate the DCL prompt. This prompt may be different on your system.
[Ctrl/x] In procedures, 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.
[Return] In procedures, a key name is shown enclosed to indicate that you press a key on a keyboard.
.
.
.
A vertical ellipsis in an example indicates that information not directly related to the example has been omitted.
file-spec,... A horizontal ellipsis indicates that you can enter additional parameters, values, or information.
[logical-name] Square brackets indicates that the enclosed item is optional. (Square brackets are not, however, optional in the syntax of a directory name in a file specification or in the syntax of a substring specification in an assignment statement.)


Chapter 1
Preparing for DEC C for OpenVMS Alpha Installation

This chapter discusses the preparations and requirements necessary for installing DEC C for OpenVMS Alpha Systems.

This guide applies to Version 5.3 of DEC 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 Digital representative.

DEC C provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. 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 Required Operating System Components

DEC C Version 5.3 for OpenVMS Alpha Systems requires OpenVMS Alpha Version 6.1 or higher. Future DEC C releases may require higher versions of the OpenVMS operating system, as described in the online release notes or the Read Before Installing or Using DEC C Version 5.n for OpenVMS Alpha Systems letter.

The OpenVMS operating system comes with a variety of support options, or classes. Classes include such features as networking and RMS journaling. To use DEC C, your system should be running a version of OpenVMS Alpha that includes the following classes:

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

1.2 Optional Software

Table 1-1 provides information on optional software that can be used together with DEC C.

Table 1-1 Related Optional Software
Product Name Description
DECset A comprehensive Computer Aided Software Engineering (CASE) environment consisting of the following integrated components: Language-Sensitive Editor (LSE), Source Code Analyzer (SCA), Performance Coverage Analyzer (PCA), Code Management System (CMS), Module Management System (MMS), and DEC Test Manager.

1.3 License Registration

Before you install and run DEC C Version 5.3 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 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 DEC 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 DEC C, review the License PAK status and install the License PAKs for any prerequisite or optional software before you install DEC C.

You must register and load your license for DEC 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, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration:

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

1.4 Installation Procedure Requirements

This section and those that follow discuss various requirements for installing DEC C.

The installation takes approximately 5 minutes, depending on your type of media, your system configuration, and the kit components chosen.

1.4.1 Installation Account Privileges and Disk Space

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

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

The DEC C compiler's requirements for free disk storage space are different during installation and after installation. Table 1-2 lists the storage requirements.

Table 1-2 Disk Space Requirements
Kit Blocks During Installation Blocks After Installation
Compiler 34,000 22,000

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


$ SHOW DEVICE SYS$SYSDEVICE

1.4.2 System Parameters

Installing DEC 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:

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.

Note

You must ensure that your system has the necessary global pagelets and global section SYSGEN quotas for the installation. Failure to do so could cause the DCL tables to become corrupted in some situations.

1.4.2.1 Calculating Values for GBLPAGES and GBLSECTIONS

To install and run DEC 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:


$ DIR/SIZE 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):


$ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES")
15848
$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")
24

If the value 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 1.4.2.2 describes the procedures for increasing these values using AUTOGEN.

1.4.2.2 Changing System Parameter Values with AUTOGEN

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

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:


SYS$SYSTEM:MODPARAMS.DAT

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 ADD_. The following example increases the global page setting by 2000:


ADD_GBLPAGES = 2000

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


$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT

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.4.3 VMSINSTAL and Installation Requirements

When you invoke VMSINSTAL, it checks the following:

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

1.4.3.1 VMSINSTAL Installation Process Requirements

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

1.4.3.2 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 BYTLM quota for the account-name installation account, you might enter the following command sequence:


$ RUN SYS$SYSTEM:AUTHORIZE
UAF> MODIFY account-name /BYTLM = 18000
UAF> SHOW account-name
UAF> EXIT
$ LOGOUT

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.4.4 Backing Up Your System Disk

At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you 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.


Next Contents