Order Number: AA--PY27F--TE

This guide contains instructions for installing DIGITAL C++ on OpenVMS Alpha systems. It also explains how to read the online release notes before or after installing the product.

Revision/Update Information: This is a revised manual, replacing AA--PY27E--TE

Operating System & Version: OpenVMS Alpha Version 6.2 to 7.2
Future maintenance releases might
require higher versions.

Software Version: DIGITAL C++ Version 6.1 to 7.2 for OpenVMS Alpha

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.

No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies.

Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Copyright ©1993, 1999

The following are trademarks of Digital Equipment Corporation: Alpha, DEC, DEC FUSE, DECthreads, DIGITAL, Ladebug, OpenVMS, ULTRIX, VAX, VAX DOCUMENT, VMS, and the DIGITAL logo.

The following are third-party trademarks:

Motif is a registered trademark of Open Software Foundation Incorporated.

PostScript is a registered trademark of Adobe Systems Incorporated.

ZK6306

This document is available on CD-ROM.

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

Contents

This guide describes how to install DIGITAL C++ on the OpenVMS Alpha operating system. It is intended for system managers. Keep this guide with your distribution kit, in case you need it to reinstall DIGITAL C++ for OpenVMS Alpha for any reason.

You may send comments or suggestions concerning this guide, or any DIGITAL C++ for OpenVMS Alpha document, by electronic mail to the following Internet address:

• cxx_docs@bookie.enet.dec.com

Document Structure

This guide contains three chapters and one appendix:

• Chapter 1 describes how to prepare for DIGITAL C++ for OpenVMS Alpha installation.
• Chapter 2 describes how to install the DIGITAL C++ for OpenVMS Alpha compiler.
• Chapter 3 describes postinstallation procedures.
• Chapter 4 describes how to install the DIGITAL C++ debugger.
• Appendix A shows a sample installation.

Associated Documentation

In addition to this guide, the DIGITAL C++ for OpenVMS Alpha Version 6.1 documentation set includes the following books:

• Stroustrup, Bjarne. The C++ Programming Language, 3nd Edition. Reading, Massachusetts: Addison-Wesley, 1997. This book is available only as hardcopy documentation.
• Using DIGITAL C++ for OpenVMS Alpha
• DEC C++ Class Library Reference Manual
• DEC C Run-Time Library Reference Manual for OpenVMS Systems

For information on the DIGITAL C++ for OpenVMS Alpha online release notes, see Chapter 1.

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 or the online HELP/MESSAGE facility.

Conventions

Table 1 lists the conventions used in this guide.

Table 1 Conventions

Convention	Meaning
UPPERCASE TEXT	Uppercase text indicates the name of a command, a file, a parameter, a procedure, or utility.
$ @SYS$UPDATE:VMSINSTAL	In interactive examples, prompts or displayed text appears in a monospace font. User input appears in bold monospace font.
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 or a pointing device button; for example, Ctrl/C or Ctrl/Z.
[YES]	Square brackets indicate that the enclosed item is a default value in a VMSINSTAL prompt. Also, square brackets serve as delimiters for a directory name in a file specification.

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 Compaq representative.

DIGITAL C++ for OpenVMS Alpha provides online release notes, which are copied to SYS$HELP during installation. DIGITAL strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the online release notes for the DIGITAL C++ compiler, see step 2 in Section 2.1.

Debugging support has been improved as of DIGITAL C++ Version 5.5. These improvements require the installation and use of a new OpenVMS debugger. This special DIGITAL C++ debugger is shipped with DIGITAL C++ but must be separately installed. The installation of this debugger does not replace the debugger that is supplied with the operating system, and you need to take special steps after installation if you want the special DIGITAL C++ debugger to be the default debugger on your system. See Chapter 4.

1.1 License Registration

Before you install and run DIGITAL C++ for OpenVMS Alpha 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 DIGITAL C++ for OpenVMS Alpha 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 DIGITAL C++ for OpenVMS Alpha, review the PAK status and install the PAKs for any prerequisite or optional software before you install DIGITAL C++ for OpenVMS Alpha.

You must register and load your license for DIGITAL C++ for OpenVMS Alpha before you start the installation to run the Installation Verification Procedure (IVP) and use the software.

Log in to the system manager's account, SYSTEM. You have a choice of two ways to register a license:

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

If you plan to use DIGITAL C++ for OpenVMS Alpha on more than one node in a VMScluster, 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 OpenVMS License Management Utility Manual.

1.2 Required Operating System Components and Software

DIGITAL C++ for OpenVMS Alpha Version 6.1 requires the OpenVMS Alpha operating system Version 6.2 to 7.2. Future DIGITAL C++ for OpenVMS Alpha releases may require higher versions of the operating system, as described in the online release notes or the Read Before Installing or Using DIGITAL C++ Version 6.1 for OpenVMS Alpha 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 DIGITAL C++ for OpenVMS Alpha, your system should be running a version of OpenVMS Alpha that includes the base component and the following:

• Programming support
• Utilities

Table 1-1 provides information about optional software that you can use together with DIGITAL C++ for OpenVMS Alpha.

Table 1-1 Optional Software

Optional Product	Purpose
DEC Language-Sensitive Editor (LSE) Version 4.0 or higher	Formatted language constructs simplify editing source programs. Support for DIGITAL C++ requires that LSE be installed before the compiler is installed.

1.3 Installation Procedure Requirements

This section discusses settings that you should check to be sure that your system is ready for the installation of DIGITAL C++ for OpenVMS Alpha to proceed.

1.3.1 Process Privileges

To install DIGITAL C++ for OpenVMS Alpha, you must be logged in to an account that has SETPRV or at least the following privileges:

• CMKRNL
• WORLD
• SYSPRV

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

1.3.2 Process Account Quotas

VMSINSTAL requires that the installation account have minimum quotas as shown in Table 1-2.

Table 1-2 Process Quotas for the Installing Account

Name	Quota
ASTLM	190
BIOLM	160
BYTLM	99,000
DIOLM	160
ENQLM	4000
FILLM	300

Use the OpenVMS Authorize Utility to verify and change 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 instance, 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 = 99000 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.

User account quotas are stored in the file SYSUAF.DAT. For more information on modifying account quotas, see the description of the Authorize Utility in the OpenVMS System Management Subkit.

1.3.3 System Parameters

Table 1-3 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings.

Table 1-3 Minimum Required System Parameter Values

System Parameter	Minimum Value	Default Value
CLISYMTBL 1	500	500
GBLPAGES 2	6300	6300
GBLPAGFIL	1024	1024
GBLSECTIONS 2	2	2

Requirements for free disk storage space are different during installation and after installation. Table 1-4 summarizes the storage requirements.

Table 1-4 Disk Space Requirements

Kit	Blocks During Installation	Blocks After Installation
Compiler	145,000	90,000
C RTL header files with text header files	1000 8300 1	500 7700 1
C++ header files with text header files	3800 5200	1900 2600
Release notes	300	300
Total with text header files	33100 41800	16700 24600

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

$ SHOW DEVICE SYS$SYSDEVICE

1.3.5 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 back up your system disk before installing any software.

Use the backup procedures that are 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.3.6 Additional System Maintenance Procedures

This section explains how to use the System Generation Utility (SYSGEN) and the AUTOGEN Utility to prepare your system for an installation of DIGITAL C++. AUTOGEN uses system configuration data to automatically set system parameters.

1.3.6.1 Checking System Parameter Values

To check the values of your system parameters, enter the following command:

$ RUN SYS$SYSTEM:SYSGEN SYSGEN>

At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The following example displays the value for the WSMAX system parameter:

SYSGEN> SHOW WSMAX

Parameter Name Current Default Min. Max. Unit -------------- ------- ------- ------- ------- ---- WSMAX 81920 4096 1024 1048576 Pagelets internal value 5120 256 64 65536 Pages

After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. For information on setting dynamic system parameter values, see Section 1.3.6.4.

1.3.6.2 Calculating the Values for Global Pagelets and Global Sections

To install and run DIGITAL C++ for OpenVMS Alpha, you must have sufficient free global pagelets and global sections. You must first find out how many free global pagelets and sections you have on your system. Then use AUTOGEN if you need to increase the global pagelets and global sections system parameters.

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 for the file.

You can use the WRITE command with the F$GETSYI lexical function to find the number of free global pagelets and 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 values displayed by the system are greater than the values in Table 1-3, you do not need to increase the values for these parameters. If the value of free global pagelets or global sections is less than the value in Table 1-3, you must increase the system parameter setting.

Section 1.3.6.3 describes the procedures for increasing these values using AUTOGEN.

1.3.6.3 Changing System Parameter Values with AUTOGEN

Use the AUTOGEN command procedure to change 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:

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 free global pagelets and global sections, use ADD_GBLPAGES or ADD_GBLSECTS. The following example increases the global page setting by 2000:

ADD_GBLPAGES = 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 execute the AUTOGEN procedure to recalculate your system parameters. The following command recalculates your system parameters and reboots the system:

$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT

When you specify REBOOT, AUTOGEN performs 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.

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 system management documentation for your operating system.

1.3.6.4 Setting Dynamic System Parameter Values

Use SYSGEN to set dynamic parameters. Dynamic parameters changed with the SYSGEN command WRITE ACTIVE become active immediately without any need to reboot your system. Rebooting returns dynamic system parameter values to their previous settings.

After you change the dynamic parameter values, you should complete the installation before rebooting the system. After you finish the installation, you can reset the dynamic parameters to their previous values or let them be reset automatically when you reboot your system the next time.

If the dynamic parameter values on your system are less than the values previously listed, use the following series of commands to change the values. This example changes the GBLPAGES value to 100000:

$ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SET GBLPAGES 100000 SYSGEN> WRITE ACTIVE SYSGEN> EXIT

After you register and load the License Product Authorization Key (License PAK), the installation takes approximately 3 to 10 minutes, depending on your system configuration and the kit components chosen.

2.1 Installation Procedure

If it is not already inserted, place the compact disc (CD-ROM) media into the CD-ROM drive.

To abort the installation procedure at any time, press Ctrl/Y. When you press Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again.

When the system prompts you with a question during the installation procedure, the default answer is often listed in brackets ([]).

1. Log in to a privileged account and set your default device and directory to SYS$UPDATE.

   Username: SYSTEM Password:

2. Invoke VMSINSTAL.

   @SYS$UPDATE:VMSINSTAL saveset-name device-name option-list

   
   To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. The elements that you specify when you invoke the VMSINSTAL command procedure are as follows:

   saveset-name

   The installation name for the component. For DIGITAL C++ for OpenVMS Alpha, use the following installation name:

   CXX06n

   
   n represents the minor (point) release number for DIGITAL C++ for OpenVMS Alpha.
   To obtain the directory location of the DIGITAL C++ for OpenVMS Alpha save set on the CD-ROM, refer to the Software Product Library CD-ROM User's Guide booklet that accompanies the CD-ROM distribution kit, or before starting installation, complete these steps:

   1. To determine whether the CD-ROM drive is already mounted (with the MOUNT command), enter the following command:

      $ SHOW DEVICE DKA400:

   2. If it is not mounted, enter the appropriate MOUNT command to mount the CD-ROM (omit the /FOREIGN qualifier).
   3. To obtain the save-set name, enter a DIRECTORY command specifying the directory file from the previous command:

      $ DIRECTORY DKA400:[CXX06n.KIT]CXX06n.A

      
      n represents the minor release of DIGITAL C++ for OpenVMS Alpha.

   device-name

   The name of the device on which you plan to mount the media and the directory containing the DIGITAL C++ for OpenVMS Alpha save set. For example, DKA400: is the device name used in examples in this guide. The directory is [CXX06n], where n is the minor release number.
   To specify the device name on the @VMSINSTAL command line, enter:

   DKA400:[CXX06n]

   option-list

   The word OPTIONS followed by one or more of the following option designators---A, G, L, N, R:

   • Auto_answer option (A)
     Initially creates a file that contains your answers to VMSINSTAL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system).
   • Get save-set option (G)
     Lets you store product save sets temporarily on a magnetic tape or in a disk directory.
   • File log option (L)
     Logs all activity to the terminal during installation.
   • Display or print the release notes (N)
     Indicates that you want to see the installation question on release notes. If you do not include the N option, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation.
     If you are restarting the installation and have already reviewed the release notes, you do not need to specify the N option. (Even if you omit the N option when you invoke VMSINSTAL, the DIGITAL C++ for OpenVMS Alpha release notes are copied automatically to the SYS$HELP directory.)
   • Alternate root option (R)
     Lets you install the product to a system root other than that of the running system.

   
   For detailed information on these software installation options, see the OpenVMS operating system documentation. If you specify more than one option, separate the options with commas, such as OPTIONS A,N.

   
   The following example invokes VMSINSTAL to install DIGITAL C++ for OpenVMS Alpha and shows the system response. This example uses the OPTIONS N release note option.

   $ @SYS$UPDATE:VMSINSTAL CXX06n DKA400:[CXX06n] OPTIONS N OpenVMS AXP Software Product Installation Procedure K7.2 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help.

   
   If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure.

   Verify user's account and quotas
   
   When you invoke VMSINSTAL, it checks the following:

   • Whether you are logged in to a privileged account. DIGITAL recommends that you install software from the system manager's account with your default device and directory set to SYS$UPDATE.
   • Whether you have adequate quotas for installation. VMSINSTAL checks for the quota values shown in Table 1-2.
   
   VMSINSTAL then checks to determine whether any users are logged in to the system. If users are logged in, VMSINSTAL asks whether you want to continue the installation:

   * Do you want to continue anyway [NO]? YES

   
   If you want to continue, enter YES. If you want to stop the installation, press Return.

   Confirm system backup
   

   * Are you satisfied with the backup of your system disk [YES]?

   
   If you are satisfied with the backup of your system disk, press Return. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation.

   Specify distribution
   
   If you omitted the device name on the VMSINSTAL command line, the following prompt appears:

   * Where will the distribution volumes be mounted: DKA400:[CXX06n]

   
   If this prompt appears, enter the name of the distribution (media) device and directory that contains the DIGITAL C++ for OpenVMS Alpha kit (save set). For example, if the media is contained on a CD-ROM located on unit DKA400:, enter DKA400:[CXX06n] in reply to this question (where n is the minor version number).

   Specify save set
   
   If you omitted the product save set name on the VMSINSTAL command line, the following prompt appears:

   Enter the products to be processed from the first distribution volume set. * Products: CXX06n

   
   If this prompt appears, enter the DIGITAL C++ for OpenVMS Alpha kit name. The name has the format, CXX06n (where n is the minor version number).

   Verify the product being installed
   

   The following products will be processed: CXX Vn.n Beginning installation of CXX Vn.n at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A...

   
   The product name and version are displayed. This save set (A) is restored to a subdirectory of SYS$UPDATE:.
   Next, VMSINSTAL displays the following message:

   %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. DIGITAL C++ Vn.n for OpenVMS Alpha Systems

   The release notes are copied to the following files in the SYS$HELP directory (where n is the minor version number):

   SYS$HELP:CXX06n.RELEASE_NOTES SYS$HELP:CXX06n_RELEASE_NOTES.PS

   
   After the installation, you can enter the following command to view the location of the release notes through the Help facility:

   $ HELP CXX RELEASE_NOTES

   Note The name of the release notes file (installed by VMSINSTAL) consists of the current product name and version number.

   Choose the Installation Verification Procedure option
   
   If you have chosen to install the compiler component, the installation procedure now asks if you want to run the Installation Verification Procedure (IVP). The IVP checks to be sure that the installation is successful. DIGITAL recommends that you run the IVP.

   * Do you want to run the IVP after the installation [YES]?

   
   After DIGITAL C++ for OpenVMS Alpha is installed, you can run the IVP independently to verify that the software is available on your system. You might need to run the IVP after a system failure to make sure that users can access DIGITAL C++ for OpenVMS Alpha.

   Select components to install
   
   The installation procedure lets you select the components of the kit that you want to install. The choices are as follows:

   • DIGITAL C++ compiler
     This component includes help text, command definitions, and the IVP for the compiler.
   • C Run-Time Library and C++ Class Library text header files
     For efficiency, the header files are installed on the system in text library format, within SYS$LIBRARY. However, this creates a problem when users need to use the headers as reference. To remedy this, the installation procedure will now prompt you to install a "reference copy" of the text headers. These are in traditional text form, and are suitable for searching, lookup, and so on. When selected, the procedure will break them up and install them into the following subdirectories:

     SYS$COMMON:[CXX$LIB.REFERENCE.CXXL$DEF_HXX] SYS$COMMON:[CXX$LIB.REFERENCE.CXXL$DEF_H] SYS$COMMON:[CXX$LIB.REFERENCE.DECC$RTLDEF_HXX] SYS$COMMON:[DECC$LIB.REFERENCE.DECC$RTLDEF]

     
     By default, they will not be searched by the compiler.

     Note The header files (text libraries) are now automatically installed based on the time stamps found within them. Time stamps on the kit versions are compared to those on the system, and the kit libraries are installed only if they are found to be more recent. All of this occurs without prompting.

   • CXXLINK facility
   
   Select the components you want to install by answering YES or NO to the questions. If you want a more detailed description of any component, enter a question mark (?). After the explanation is displayed, you will be prompted again for a response.
   If you enter YES, the installation procedure validates that your request is possible and installs the component.
   If you enter NO, the installation procedure then issues prompts for selecting the next component.

   Respond to license registration query
   
   The DIGITAL C++ for OpenVMS Alpha compiler component supports the OpenVMS License Management Facility (LMF). If you entered YES to install the compiler component, the installation procedure displays license information about DIGITAL C++ for OpenVMS Alpha. It asks whether you have registered and loaded your PAK for each product. The following is an example of the information and the queries presented by the installation procedure:

   The DIGITAL C++ compiler component requires a Product Authorization Key (PAK) for DIGITAL C++ to be registered and loaded. Answer the following question with YES if a PAK with the specified product name and a date equal to or later than the date shown is registered and loaded, otherwise answer NO. Product: CXX-V Producer: DEC Version: 6.n Release Date: dd-mmm-yyyy

   * Does this product have an authorization key registered and loaded?: YES

   
   If you have not registered and loaded your PAK, you must answer NO to this question. You have to register and load your PAKs to successfully complete the installation (see Section 1.1). If you have not done so, you should stop the installation, register and load your PAKs, and then restart the installation.

   Read informational messages
   
   At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. The new files include the following:

   SYS$HELP:CXX06n.RELEASE_NOTES [new] SYS$HELP:CXX06n_RELEASE_NOTES.PS [new] SYS$TEST:CXX$IVP.COM [new] SYS$TEST:CXX$IVP_C.COM [new]

   
   Additionally, if you elected to install the compiler component, the new and modified files consist of the following:

   SYS$SYSTEM:CXX$COMPILER.EXE [new] SYS$MESSAGE:CXX$COMPILER_MSG.EXE [new] SYS$HELP:HELPLIB.HLB [modified] SYS$COMMON:[SYSHLP.CXX$HELP]*.* [new] SYS$LIBRARY:DCLTABLES.EXE [modified]

   
   The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE files are updated to include the new versions of the DIGITAL C++ for OpenVMS Alpha help text (module CXX$HELP.HLP) and the cxx command-line definition.
   If the header file components are installed, the following new files are copied:

   SYS$LIBRARY:DECC$RTLDEF.TLB [new] SYS$LIBRARY:DECC$RTLDEF_HXX.TLB [new] SYS$LIBRARY:CXXL$DEF_HXX.TLB [new] SPS$LIBRARY:CXXL$DEF_HXX.TLB [new]

   
   If you answered YES in response to the prompt that requests a file purge, previous versions of the DIGITAL C++ for OpenVMS Alpha files are now purged.
   The end of the installation is indicated by the following message:

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

   Observe the IVP
   
   If you chose to run the IVP, VMSINSTAL now invokes the IVP to verify that DIGITAL C++ for OpenVMS Alpha was installed successfully.
   If DIGITAL C++ for OpenVMS Alpha was installed successfully, the IVP displays the following:

   Digital C++ V6.1 Installation Verification Procedure completed successfully

   End the installation procedure
   

   Installation of CXX Vn.n completed at hh:mm Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]CXX061.VMI_DATA

   
   Depending on whether you specified parameters on the VMSINSTAL command line, the * Products: prompt or the DCL prompt ($) may appear. If the * Products: prompt appears, you can return to the DCL prompt by pressing Ctrl/Z.
   If you removed any media from the console drive before beginning the installation, you should replace it now.
   VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the installation account (such as SYSTEM) and you want to restore these symbols, you should log out and log in again.

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, enter NO or press Return. Correct the problem and restart the installation.

If errors occur during the installation itself or when the Installation Verification Procedure (IVP) is running, VMSINSTAL displays failure messages. If the installation fails, you will see the following message:

%VMSINSTAL-E-INSFAIL, The installation of DIGITAL C++ for OpenVMS Alpha Version 5.n has failed.

If the IVP fails, you will see these messages:

The DIGITAL C++ for OpenVMS Alpha Version 5.n Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for DIGITAL C++ for OpenVMS Alpha Version 5.n has failed.

Errors can occur during the installation if any of the following conditions exist:

• The operating system version is incorrect.
• A prerequisite software version is incorrect.
• Quotas necessary for successful installation are insufficient.
• System parameter values for successful installation are insufficient.
• The OpenVMS Help library is currently in use.
• The product license has not been registered and loaded.

For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For information on installation requirements, see Chapter 1.

If the installation fails, you must restart the installation procedure from step 2. For an explanation of any system messages, see the OpenVMS System Messages and Recovery Procedures Reference Manual or the online HELP/MESSAGE facility. If the installation fails due to an IVP failure, contact a Compaq field service representative.

DIGITAL C++ for OpenVMS Alpha is now installed and can be invoked by all users with the cxx command.

The installation procedure modifies the DCL command table so that the cxx 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 cxx command must log out and log in again, or use the following DCL command:

$ SET COMMAND /TABLES=SYS$LIBRARY:DCLTABLES

The following tasks can be performed after DIGITAL C++ for OpenVMS Alpha is installed:

• Running the Installation Verification Procedure (IVP) separately
• Editing the system startup and shutdown files
• Modifying system parameter settings
• Making the product usable on a VMScluster
• Setting user account quotas
• Tailoring your system
• Enhancing performance
• Reporting problems

The following sections describe these tasks in detail.

3.1 Running the Installation Verification Procedure Separately

You usually run the Installation Verification Procedure (IVP) during installation. To run the IVP separately to ensure the integrity of installed files should system problems occur, type the following:

$ @SYS$TEST:CXX$IVP.COM

If the IVP fails for any reason, the following message is displayed:

DIGITAL C++ for OpenVMS Alpha VERSION Vn.n TEST FAILED

3.2 Editing and Organizing the System Files

You do not need to edit the compiler system startup and shutdown files to provide for automatic startup and shutdown of DIGITAL C++ when your system is rebooted.

3.3 VMScluster Considerations

After completing the initial installation, if you want to install DIGITAL C++ for OpenVMS Alpha on multiple nodes in a cluster, you must run INSTALL on each of the other nodes and enter the following command:

INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE

If you are using a dual-architecture (VAX and Alpha systems) 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 Manager's Manual.

3.4 User Account Requirements

Many products cannot be used unless certain privilege and quota requirements are met by user accounts. The following sections describe the privilege and quota requirements needed to work with DIGITAL C++ for OpenVMS Alpha.

3.4.1 User Privileges

To use DIGITAL C++ for OpenVMS Alpha, each account must have at least the TMPMBX and NETMBX privileges. Use the OpenVMS Authorize Utility to determine whether users have the privileges they require.

3.4.2 User Account Quotas

To use DIGITAL C++ for OpenVMS Alpha, a user account does not need to meet any special quota requirements. However, for users who will be compiling very large programs (many program units compiled together), consider adjusting the working set (WSDEF, WSQUOTA, WSEXTENT) and pagefile (PGFLQUOTA) account quotas to improve performance.

See Section 1.3.2 for a description of how to verify and change account quotas.

3.4.3 Installing the DIGITAL C++ for OpenVMS Alpha Compiler and the DIGITAL C++ Class Library as a Shared Image

DIGITAL highly recommends that you reduce the system overhead and memory requirements by installing the DIGITAL C++ for OpenVMS Alpha compiler and the DIGITAL C++ Class Library as shared images. To install DIGITAL C++ for OpenVMS Alpha as a shared image on a system that is currently running, use the INSTALL Utility. DIGITAL recommends that you install DIGITAL C++ for OpenVMS Alpha as shared on a system that has been rebooted recently because the available space in the global pagelet table is less likely to be fragmented.

To install DIGITAL C++ for OpenVMS Alpha and the Class Library as a shared image:

1. Determine the number of available (free) global pagelets and global sections on your system and the number of each needed to install and run DIGITAL C++ for OpenVMS Alpha (see Section 1.3.6.2).
2. If necessary, increase the current number of global pagelets and global sections parameters (see Section 1.3.3).

After you reset the system parameter values, invoke the INSTALL Utility from a privileged account and install the DIGITAL C++ for OpenVMS Alpha compiler as a shared image:

$ INSTALL INSTALL> ADD SYS$SYSTEM:CXX$COMPILER.EXE /OPEN /SHARED INSTALL> EXIT

Similarly, install the DIGITAL C++ Class Library as a shared image:

$ INSTALL INSTALL> ADD SYS$LIBRARY:CXXL$011_SHR.EXE /OPEN /SHARED INSTALL> EXIT

Add the following lines to the appropriate system startup command file so that DIGITAL C++ for OpenVMS Alpha is available as a shared image each time the system is started. (If your site has modularized its startup procedures, be sure you add the lines to the correct file.) The default startup command file is SYS$MANAGER:SYSTARTUP_VMS.COM.

$ INSTALL ADD SYS$SYSTEM:CXX$COMPILER.EXE /OPEN /SHARED ADD SYS$LIBRARY:CXXL$011_SHR.EXE /OPEN /SHARED EXIT

Using the /PRIVILEGED qualifier is neither necessary nor recommended.

To install the compiler message file, enter the following commands:

$ INSTALL INSTALL> ADD SYS$MESSAGE:CXX$COMPILER_MSG.EXE INSTALL> EXIT

To install the Class Library message file, enter the following commands:

$ INSTALL INSTALL> ADD SYS$MESSAGE:CXXL$MSG_SHR.EXE INSTALL> EXIT

When you install DIGITAL C++ for OpenVMS Alpha as a shared image you need to increase the global pagelets and global sections parameters. See Section 1.3.3 for information on changing these parameters.

3.5 Getting Help and Reporting Problems

If an error occurs while DIGITAL C++ for OpenVMS Alpha is in use and you believe the error is caused by a problem with the product, please report it to DIGITAL.

If you have a Software Product Services Support Agreement, contact your Customer Support Center (CSC) by telephone or by 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, indicate the following:

• The name and version number of the operating system you are using
• The version number of DIGITAL C++ for OpenVMS Alpha you are using
• The hardware system you are using (such as a model number)
• A brief description of the problem (one sentence if possible)
• How critical the problem is

Whether you submit information electronically or contact the appropriate support specialist by telephone, please take the following steps:

1. Describe as accurately as possible the circumstances and state of the system when the problem occurred. Include the description and version number of the DIGITAL C++ for OpenVMS Alpha compiler being used. Demonstrate the problem with specific examples.
2. Reduce the problem to as small a size as possible.
3. Remember to include listings of any command files, INCLUDE files, or relevant data files, and so forth.
4. Provide a listing of the program.
5. If the program is longer than 50 lines, submit a copy of it on machine-readable media (diskette or magnetic tape).
6. Report only one problem per report. This will facilitate a faster response.
7. Mail the problem report to DIGITAL.

If the problem is related to DIGITAL C++ for OpenVMS Alpha documentation, you can report the problem to the CSC (if you have a Software Product Services Support Agreement and the problem is severe); otherwise, send your comments about DIGITAL C++ for OpenVMS Alpha documentation to the following Internet address:

cxx_docs@bookie.enet.dec.com

To obtain information about purchasing a DIGITAL Software Product Services Support Agreement or other support services, please contact your local Compaq sales representative or business partner.

A special C++ debugger is provided with the DIGITAL C++ Version 6.1 kit and must be installed to debug programs compiled with DIGITAL C++ Version 6.1.

The special C++ debugger is an early copy of the standard OpenVMS debugger that will ship in a future release after OpenVMS Alpha Version 7.2 and provide full support for languages other than C++. The installation of this debugger kit does not replace the debugger supplied with the operating system. Thus, you can use either debugger after installation. Special steps must be taken if you want the special C++ debugger to be the default debugger on your system.

If you install the debugger on a version of OpenVMS that does not have DECwindows Motif installed, or on a version of OpenVMS that has a version of DECwindows Motif prior to Version 1.2-4, the C++ debugger's Graphic User Interface (GUI) image will not be installed. If you decide later to install Motif, or to upgrade Motif to Version 1.2-4, and you then want to use the debugger's GUI, you should then reinstall the DIGITAL C++ debugger, to create the debugger's GUI image.

4.1 Installing the Debugger

The C++ debugger must be installed in addition to the compiler. The installation procedure is similar to that for the compiler kit; to install the debugger, invoke the VMSINSTAL command procedure, as described in Section 2.1. The saveset-name for the debugger kit is ADX072. The other parameters to VMSINSTALL should be the same as specified when installing the compiler kit. For example:

@SYS$UPDATE:VMSINSTAL ADX072 device-name option-list

The installation of this debugger kit does not replace the debugger supplied with the operating system. After installing the C++ debugger, you need to invoke a command procedure to install the C++ debugger images and define the default system debugger.

If you want the special C++ debugger to be the default debugger for the system, you should do the following from a privileged account, after installing the ADX072 kit:

1. Enter the following command and add it to the system startup procedure (SYS$STARTUP:SYSTARTUP_VMS.COM):

   @SYS$STARTUP:DEBUG$STARTUP_V72X.COM V72X

2. On OpenVMS versions prior to Version 7.0, copy the C++ debugger resource file using the following command:

   $ COPY DECW$SYSTEM_DEFAULTS:CXXVMSDEBUG.DAT - DECW$SYSTEM_DEFAULTS:VMSDEBUG.DAT

If you do not want the special C++ debugger to be the default debugger for the system, enter the following command from a privileged account and add it to the system startup procedure (SYS$STARTUP:SYSTARTUP_VMS.COM):

@SYS$STARTUP:DEBUG$STARTUP.COM VMS

Regardless of which debugger you select as the default system debugger, individual users can choose the other debugger. See the DIGITAL C++ release notes for more information.

This appendix contains a sample installation for the DIGITAL C++ for OpenVMS Alpha kit. This is only a sample. Sometimes the installation procedure is modified in maintenance updates of this product.

Because this installation guide is not usually revised for maintenance updates, be sure to read the applicable Read Before Installing or Using DEC C++ letter before you install this product. This letter notes any significant changes to the installation sample shown here. Such information also appears in the online release notes.

The following sample was installed on a system where DIGITAL C++ for OpenVMS Alpha was not previously installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation.

This sample installation assumes that DECnet has been shut down, that no users are logged in to your system, and that OPTIONS N is specified to print the release notes. The Installation Verification Procedure (IVP) runs at the end of the installation.

Example A-1 shows a sample installation of DIGITAL C++ Version 6.1 on an OpenVMS Alpha system.

Example A-1 Sample DIGITAL C++ for OpenVMS Alpha Installation on OpenVMS Alpha

$ @sys$update:vmsinstal OpenVMS AXP Software Product Installation Procedure K7.2 It is 21-JAN-1999 at 13:39. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Y * Where will the distribution volumes be mounted: DKA400:[CXX061] Enter the products to be processed from the first distribution volume set. * Products: CXX061 * Enter installation options you wish to use (none): N The following products will be processed: CXX V6.1 Beginning installation of CXX V6.1 at 13:39 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Digital C++ Version V6.1 for OpenVMS Alpha Systems Copyright Digital Equipment Corporation 1999. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? Y This kit contains an Installation Verification Procedure (IVP) to verify the correct installation of the DEC DIGITAL C++ compiler component and class library headers. IVP will be placed in: SYS$TEST:CXX$IVP.COM After the installation is complete, you can invoke the command file at any time to reverify that DIGITAL C++ is installed and working correctly. If you wish to invoke it automatically at the completion of this installation procedure, answer Yes to the following question. * Do you want to run the IVP after the installation [YES]? Y The DIGITAL C++ kit contains four components: Compiler (includes help text, command definition, IVP) C Runtime Library Header files (includes OpenVMS system symbol definitions) C++ Class Library Header files CXXLINK facility If you want a more detailed description of any component that you are prompted for, answer with a question mark "?"; after the explanation is displayed, you will be prompted again for a response. * Do you want to install the compiler component [YES]? Y The C RTL is always provided. The C++ Class Library headers are always provided. The C Runtime Library, and C++ Class Library, headers will be installed as Text Libraries (.TLBs). If you also wish to install the traditional text form of the headers (.H and .HXX files) for reference purposes, please answer yes to the following question. The text headers will be placed in a subdirectory that will not be searched by the compiler. Instead, they will be placed the subdirectory tree: SYS$COMMON:[CXX$LIB.REFERENCE...] ( SYS$COMMON:[DECC$LIB.REFERENCE...] for the DEC C RTL header library, DECC$RTLDEF, and the system definition header library, SYS$STARLET_C.) Note that doing this may double the disk space used for the headers. * Do you want to install the text form of the headers? [YES]? Y * Do you want to install the CXXLINK facility? [YES]? Y The DIGITAL C++ compiler component requires a Product Authorization Key (PAK) for DIGITAL C++ to be registered and loaded. Answer the following question with YES if a PAK with the specified product name and a date equal to or later than the date shown is registered and loaded, otherwise answer NO. Product: CXX-V Producer: DEC Version: 6.1 Release Date: 21-JAN-1999 * Does this product have an authorization key registered and loaded? Y All questions and validations regarding the installation of DIGITAL C++ kit components have now been asked. Depending upon your configuration, time estimates for the installation(s) are as follows: All questions and validations regarding the installation of Digital C++ kit components have now been asked. Depending upon your configuration, time estimates for the installation(s) are as follows: Compiler: 1 minute C RTL: 2 minutes Class Library: 1 minute CXXLINK: 1 minute IVP: 2 minutes Providing Startup Procedure Please add the SYS$STARTUP:CCXX$STARTUP.COM to the system startup procedure. To use Digital C++ for OpenVMS Alpha on other Alpha nodes of a VMScluster, from a privileged account on each such node enter the command "$ @SYS$STARTUP:CCXX$STARTUP.COM". This will install images and define system-wide logical names. Your OpenVMS system will now be updated to include the following new and modified file(s): VMI$ROOT:[SYSHLP]CXX061.RELEASE_NOTES [new] VMI$ROOT:[SYSHLP]CXX061_RELEASE_NOTES.PS [new] VMI$ROOT:[SYSTEST]CXX$IVP.COM [new] VMI$ROOT:[SYSEXE]CXX$COMPILER.EXE [new] VMI$ROOT:[SYSLIB]LIBCXXSTD.OLB [new] VMI$ROOT:[SYSMSG]CXX$COMPILER_MSG.EXE [new] ALPHA$LIBRARY:DCLTABLES.EXE [modified] SYS$COMMON:[CXX$LIB]CXX$CLD.CLD [new] SYS$HELP:HELPLIB.HLB [modified] VMI$ROOT:[SYSHLP.CXX$HELP]INTZLN.PDF [new] VMI$ROOT:[SYSHLP.CXX$HELP]IOSTREAMS.PDF [new] VMI$ROOT:[SYSHLP.CXX$HELP]INTZLN.PS [new] VMI$ROOT:[SYSHLP.CXX$HELP]IOSTREAMS.PS [new] VMI$ROOT:[SYS$STARTUP]CCXX$STARTUP.COM [new] VMI$ROOT:[SYSLIB]DECC$CRTL.OLB [new] VMI$ROOT:[SYSLIB]DECC$CRTL.EXE [new] VMI$ROOT:[SYSLIB]DECC$CRTL.README [new] VMI$ROOT:[SYSLIB]DECC$RTLDEF.TLB [new] VMI$ROOT:[SYSLIB]CXXL$ANSI_DEF.TLB [new] VMI$ROOT:[SYSEXE]CXX$LINK.EXE [new] VMI$ROOT:[SYSMSG]CXX$LINK_MSG.EXE [new] SYS$COMMON:[CXX$LIB]CXXLINK.CLD [new] VMI$ROOT:[SYSEXE]CXX$DEMANGLE.EXE [new] SYS$COMMON:[CXX$LIB]CXXDEMANGLE.CLD [new] %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Beginning Digital C++ Installation Verification Procedure Copyright (c) Digital Equipment Corporation, 1999. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Test compiler operation and error messages... Test Class Library operation... Digital C++ V6.1 Installation Verification Procedure completed successfully End of Digital C++ Installation Verification Procedure Installation of CXX V6.1 completed at 13:48 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]CXX061.VMI_DATA VMSINSTAL procedure done at 13:48

The DIGITAL C++ installation procedure installs and modifies a number of files on your system, as listed in Table B-1.

Table B-1 Files Installed or Modified

File	New or Modified
VMI$ROOT:[SYSHLP]CXX061.RELEASE_NOTES	new
VMI$ROOT:[SYSHLP]CXX061_RELEASE_NOTES.PS	new
VMI$ROOT:[SYSTEST]CXX$IVP.COM	new
VMI$ROOT:[SYSEXE]CXX$COMPILER.EXE	new
VMI$ROOT:[SYSLIB]LIBCXXSTD.OLB	new
VMI$ROOT:[SYSMSG]CXX$COMPILER_MSG.EXE	new
ALPHA$LIBRARY:DCLTABLES.EXE	modified
SYS$COMMON:[CXX$LIB]CXX$CLD.CLD	new
SYS$HELP:HELPLIB.HLB	modified
VMI$ROOT:[SYSHLP.CXX$HELP]INTZLN.PDF	new
VMI$ROOT:[SYSHLP.CXX$HELP]IOSTREAMS.PDF	new
VMI$ROOT:[SYSHLP.CXX$HELP]INTZLN.PS	new
VMI$ROOT:[SYSHLP.CXX$HELP]IOSTREAMS.PS	new
VMI$ROOT:[SYS$STARTUP]CCXX$STARTUP.COM	new
VMI$ROOT:[SYSLIB]DECC$CRTL.OLB	new
VMI$ROOT:[SYSLIB]DECC$CRTL.EXE	new
VMI$ROOT:[SYSLIB]DECC$CRTL.README	new
VMI$ROOT:[SYSLIB]DECC$RTLDEF.TLB	new
VMI$ROOT:[SYSLIB]CXXL$ANSI_DEF.TLB	new
VMI$ROOT:[SYSEXE]CXX$LINK.EXE	new
VMI$ROOT:[SYSMSG]CXX$LINK_MSG.EXE	new
SYS$COMMON:[CXX$LIB]CXXLINK.CLD	new
VMI$ROOT:[SYSEXE]CXX$DEMANGLE.EXE	new
SYS$COMMON:[CXX$LIB]CXXDEMANGLE.CLD	new

Contents