DEC_C_________________________________________ Installation Guide for OpenVMS VAX Systems Order Number: AA-PXWXD-TE December 1998 This guide contains instructions for installing DEC C on a VAX processor system running the OpenVMS operating system. Revision/Update Information: This revised manual supersedes the DEC C Installation Guide for OpenVMS VAX Systems, (Order No. AA-PXWXC-TE) Operating System & Version: OpenVMS VAX Version 5.5-2 or higher. Future maintenance releases may require higher versions. Software Version: DEC C Version 6.0 or higher for OpenVMS VAX Systems Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Printing, May 1993 Revised, June 1995 Revised, June 1996 Revised, December 1998 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. © Digital Equipment Corporation 1993, 1998. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, Digital, OpenVMS, VAX, VAX C, VAX DOCUMENT, VMS, VAXcluster, VAXstation, and the DIGITAL logo. The following are third-party trademarks: Internet is a registered trademark of Internet Inc. PostScript is a trademark of Adobe Systems, Inc. ZK6337 This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. v 1 Preparing for DEC C Installation 1.1 Required Operating System Components......... 1-1 1.2 Prerequisite Software........................ 1-2 1.3 Optional Software............................ 1-2 1.4 License Registration......................... 1-2 1.5 Installation Procedure Requirements.......... 1-3 1.5.1 Privileges and Disk Space................ 1-4 1.5.2 Process Account Quotas................... 1-4 1.5.3 System Parameters........................ 1-5 1.5.3.1 Calculating the Values for CONTIG_GBLPAGES and FREE_GBLSECTS...... 1-6 1.5.3.2 Changing System Parameter Values with AUTOGEN................................ 1-7 1.5.4 Backing Up Your System Disk.............. 1-8 2 Installing DEC C 2.1 Installation Procedure....................... 2-1 2.2 Error Recovery............................... 2-11 3 After Installing DEC C 3.1 Running the Installation Verification Procedure Separately......................... 3-2 3.2 Editing and Organizing System Files.......... 3-2 3.3 VAXcluster Considerations.................... 3-4 3.4 User Account Requirements.................... 3-5 3.4.1 Privileges............................... 3-5 3.4.2 User Account Quotas...................... 3-6 iii 3.5 Enhancing DEC C Performance.................. 3-6 3.5.1 Tuning Your System....................... 3-6 3.5.2 Installing DEC C as a Shared Image....... 3-6 3.6 Getting Help and Reporting Problems.......... 3-7 A Sample Installation Tables 1 Conventions Used in this Guide........... vii 1-1 Disk Space Requirements.................. 1-4 1-2 Process Account Quotas for the Installing Account.................................. 1-4 1-3 Global Sections and Pages Required....... 1-6 iv ________________________________________________________________ Preface Purpose of this Guide This guide describes how to install DEC C on VAX processors that are 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. At the back of this guide are two Reader's Comments forms. If you have any comments about this guide, fill out one form and mail it; your comments will be considered for the next revision of the installation guide. You may also send comments or suggestions regarding this guide, or any DEC C document, by electronic mail to the following Internet address: decc_docs@bookie.zko.dec.com Intended Audience The audience for this guide is the system manager who installs DEC C software. Structure of this Document This guide is organized as follows: o Chapter 1 describes the operating system and hardware requirements for DEC C installation and related procedures that you complete before installing DEC C. o Chapter 2 describes the step-by-step instructions for the installation. v o Chapter 3 describes actions and considerations after the installation, including running the Installation Verification Procedure (IVP). o Appendix A contains a sample listing for DEC C installation. Manuals in the DEC C Documentation Set In addition to this guide, the DEC C documentation set for OpenVMS VAX systems includes the following books: o DEC C Migration Guide for OpenVMS VAX Systems o DEC C User's Guide for OpenVMS Systems o DEC C Run-Time Library Reference Manual for OpenVMS Systems o DEC C Language Reference Manual Related Manuals For information on OpenVMS system management, see the following documents in the OpenVMS documentation set: o OpenVMS System Manager's Manual o Guide to Maintaining a VMS System o OpenVMS License Management Utility Manual o 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. Conventions Table 1 lists the conventions used in this guide. vi Table_1_Conventions_Used_in_this_Guide____________________ Convention_____________Description________________________ UPPERCASE TEXT Uppercase letters indicate the name of a command, a file, a parameter, a procedure, or utility. $ @SYS$UPDATE:VMSINSTALMonospace boldface text represents user input in interactive examples in the hardcopy and online versions of this guide. $ The dollar sign is used to indicate the DCL prompt. This prompt may be different on your system. Ctrl/x The key combination Ctrl/X indicates that you must press the key labeled Ctrl while you simultaneously press another key, for example, Ctrl/Y or Ctrl/Z. In procedures, a key name is shown enclosed to indicate that you press a key on the keyboard. . Vertical ellipsis in an example . means that information not directly . related to the example has been omitted. file-spec, . . . Horizontal ellipsis indicates that additional parameters, values, or information can be entered. [ ] Square brackets indicate 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.) VMS system All references to VMS system refer _______________________to_the_OpenVMS_operating_system.___ vii 1 ________________________________________________________________ Preparing for DEC C Installation This chapter discusses the preparations and requirements necessary for installing DEC C for OpenVMS VAX Systems. This guide applies to DEC C for OpenVMS VAX Version 6.0 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 Compaq representative. DEC C provides separate online release notes. The release notes contain installation-related notes and a summary of technical changes, known problems, restrictions, and incompatibilities. 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. 1.1 Required Operating System Components DEC C for OpenVMS VAX Systems, Version 6.0 requires OpenVMS VAX Version 5.5-2 or higher. The OpenVMS VAX (formerly VAX/VMS) operating system comes with a variety of support options, including such features as networking and RMS journaling. To use DEC C, your system should be running a version of OpenVMS that includes the following: o Programming support o Utilities Preparing for DEC C Installation 1-1 1.2 Prerequisite Software If you are installing DEC C on OpenVMS VAX Version 5.5-2 or Version 6.0, you must first install the DEC C/C++ Run- Time Components kit. See the DEC C/C++ Run-Time Components for OpenVMS VAX Reference and Installation Guide . 1.3 Optional Software See the Software Support Addendum (SSA) that comes with the Software Product Description (SPD) for a complete list of prerequisite and optional software products and their required version numbers. Note that DEC C and VAX C can coexist on your system. The CC command is used to invoke either the VAX C or DEC C compiler. If your system has a VAX C compiler already installed on it, you have the option of specifying which compiler will be invoked by default whenever just the CC command verb is used. To invoke the compiler that is not the default, use the CC command with the appropriate qualifier: /DECC for the DEC C compiler, or /VAXC for the VAX C compiler. See the DEC C release notes for more information. 1.4 License Registration Before you install and run DEC C Version 6.0 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 PAK status and install the PAKs for any prerequisite or optional software before you install DEC C. 1-2 Preparing for DEC C Installation You must register and load your license for DEC C before you start the installation to run the Installation Verification Procedure (IVP) and use the software. To register a license under OpenVMS VAX, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. o 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 DEC C on more than one node in a VAXcluster, 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 LMF, see the VMS License Management Utility Manual. 1.5 Installation Procedure Requirements This section discusses various requirements for installing DEC C. Each installation takes approximately 10 to 60 minutes, depending on your type of media and your system configura- tion. Installing DEC C and running the Installation Verification Procedure (IVP) on a standalone VAXstation 4000-60 system takes approximately 15 minutes. 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. Preparing for DEC C Installation 1-3 1.5.1 Privileges and Disk Space To install DEC C, you must be logged in to an account that has SETPRV or at least the following privileges: o CMKRNL o WORLD o SYSPRV VMSINSTAL turns off BYPASS privilege at the start of the installation. The DEC C requirements for free disk storage space are different during installation and after installation. Table 1-1 summarizes the storage requirements. Table_1-1_Disk_Space_Requirements_________________________ Blocks During Blocks After Kit______________Installation__________Installation_______ DEC_C_compiler___34,000________________27,000_____________ To determine the number of free disk blocks on the current system disk, enter the following DCL command: $ SHOW DEVICE SYS$SYSDEVICE 1.5.2 Process Account Quotas The account you use to install DEC C must have sufficient quotas to enable you to perform the installation. Table 1-2 summarizes the process quotas required for the installation account. Table 1-2 Process Account Quotas for the Installing __________Account_________________________________________ ASTLM 190 BIOLM 160 DIOLM 160 (continued on next page) 1-4 Preparing for DEC C Installation Table 1-2 (Cont.) Process Account Quotas for the __________________Installing_Account______________________ ENQLM 4000 FILLM 300 PGFLQUOTA________20,480___________________________________ User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change process quotas for the installation account. (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: $ RUN SYS$SYSTEM:AUTHORIZE UAF> MODIFY account-name/BIOLM = 160 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.5.3 System Parameters Installing DEC C requires certain system parameter settings. The minimum number of contiguous free global pages and global sections needed for the installation depends on whether SYS$SYSTEM:DECC$COMPILER.EXE was previously installed as a shared known image. See Table 1-3. Preparing for DEC C Installation 1-5 Table_1-3_Global_Sections_and_Pages_Required______________ Previously Installed as Global Shared?________Sections_____Global_Pages__________________ No 1 Sufficient number of contiguous free global pages to contain the file SYS$LIBRARY:DCLTABLES.EXE Yes 4 Approximately 2000 contiguous free global pages plus a sufficient number of contiguous free global pages to contain the file ____________________________SYS$LIBRARY:DCLTABLES.EXE_____ These values represent the number of contiguous free global pages 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 page and global section SYSGEN quotas for the installation. Failure to do so could cause the DCL tables to be corrupted in some situations. _____________________________________________________ 1.5.3.1 Calculating the Values for CONTIG_GBLPAGES and FREE_GBLSECTS To install and run DEC C, you must have sufficient contiguous free global pages and free global sections. You must first find out how many free global pages and sections you have on your system. Use AUTOGEN if you need to increase the CONTIG_GBLPAGES and FREE_GBLSECTS system parameters. Enter the following DCL command to determine the number of global pages required by SYS$LIBRARY:DCLTABLES.EXE: $ DIR/SIZE SYS$LIBRARY:DCLTABLES.EXE 1-6 Preparing for DEC C Installation This command returns the size (in blocks) of SYS$LIBRARY:DCLTABLES.EXE. As an approximation, use this figure as the number of global pages needed for the file. You can use the WRITE command with the F$GETSYI lexical function to find the number of contiguous free global pages 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 contiguous free global pages or free global sections is less than the value required (see Section 1.5.3), you must increase the system parameter setting. Section 1.5.3.2 describes the procedures for increasing these values using AUTOGEN. 1.5.3.2 Changing System Parameter Values with AUTOGEN If you do not have enough contiguous free global pages or free global sections to install DEC C, you can do either of the following: o Delete an existing known image using the OpenVMS Install Utility. o 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: 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. Preparing for DEC C Installation 1-7 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_GBLPAGES and ADD_GBLSECTIONS, respectively. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 Be aware that when you set the page file quota, you should 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. Enter the following command to recalculate your system parameters and reboot the system: $ @SYS$UPDATE:AUTOGEN SAVPARAMS 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. 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.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. 1-8 Preparing for DEC C Installation 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. Preparing for DEC C Installation 1-9 2 ________________________________________________________________ Installing DEC C This chapter explains how to install DEC C: o Section 2.1 contains a step-by-step description of the installation procedure. o Section 2.2 covers error recovery considerations. 2.1 Installation Procedure The DEC C installation procedure consists of a series of questions and informational messages. See Appendix A for a sample installation. 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. Defaults appear in brackets ([]) throughout the installa- tion procedure. 1. Log in to a privileged account and set your default device and directory to SYS$UPDATE, where VMSINSTAL resides. Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE 2. Invoke VMSINSTAL. @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N Installing DEC C 2-1 saveset-name The installation name for the component. For DEC C, use the following installation name: CC06n Where n represents the minor (point) release number of DEC C, such as CC060 for Version 6.0. Refer to the label on the DEC C distribution kit or the DEC C BOM or BIL for the maintenance update number of your kit. device-name The name of the device on which you plan to mount the media, or the name of the device:[directory] that contains the save sets. For example, DKA400: is the device name used in examples in this guide. The directory is [CC06n.KIT], where n is the minor release number. To specify the device name on the @VMSINSTAL command line, type: DKA400:[CC06n.KIT] OPTIONS N An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, 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 OPTIONS N. There are several other options you can select when you invoke VMSINSTAL: o Auto_answer (A): Initially creates a file that contains your answers to VMSINSTAL questions and prompts. This option, and the answer file it produces, can save time during a reinstallation (typically after upgrading your system). o Get save set (G): Stores product save sets temporarily on a magnetic tape or in a disk directory. 2-2 Installing DEC C o File log (L): Logs all activity to the terminal during installation. o Alternate root (R): Installs the product to a system root other than that of the running system. See the OpenVMS documentation on software installation in the OpenVMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (for example: OPTIONS A,N). The following example invokes VMSINSTAL to install DEC C and shows the system response. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL CC06n DKA400:[CC06n.KIT] OPTIONS N OpenVMS VAX Software Product Installation Procedure V5.5-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. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation. When you invoke VMSINSTAL, it checks for the following requirements: o Whether you 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. o Whether you have adequate quotas for installation. VMSINSTAL checks for the quota values shown in Section 1.5. o Whether any users are logged in to the system. If users are logged in, you are asked whether you want to continue the installation. If you want to continue, enter YES. If you want to stop the installation, press Return. Installing DEC C 2-3 3. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. 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. 4. Mount the media. If you omitted the device name in the VMSINSTAL command line, the following prompt appears: Where will the distribution volumes be mounted: DKA400:[CC06n.KIT] If this prompt appears, enter the name of the distribution (media) device and directory the contains the DEC C kit (save set). For example, if the media is contained on a CD located on unit DKA400:, enter DKA400:[CC06n.KIT] in reply to this question (where n is the minor release number.) Depending on the type of device and whether the device is already mounted, the following prompt may or may not appear: Please mount the first volume of the set on DKA400:. * Are you ready? YES %MOUNT-I-MOUNTED, DEC C mounted on DKA400: If you have not already done so, you should now insert the distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. If you enter YES to indicate that you are ready, VMSINSTAL displays a message that the media containing DEC C has been mounted on the specified device and that the installation has started. If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press Ctrl/Y. 2-4 Installing DEC C 5. Verify the product being installed The following products will be processed: CC V6.n Beginning installation of CC V6.n at 20:00 %VMSINSTAL-I-RESTORE, Restoring product saveset A... The product name and version are displayed. The save set (A) is restored to a subdirectory of SYS$UPDATE. 6. Select a release notes option. Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you specified OPTIONS N when you invoked VMSINSTAL, you are asked to choose one of the four options for reviewing the release notes. o Select option 1 to immediately display the release notes online. You can terminate the display at any time by pressing Ctrl/C. o Select option 2 to print the release notes. You are prompted for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: Either press Return to send the file to the default output print device (SYS$PRINT) or enter another queue name. o Select option 3 to immediately display the release notes online and then be prompted for a queue name for the printed version. o Select option 4 if you have already reviewed the release notes and are restarting the installation. Installing DEC C 2-5 Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press Return. In either case, the release notes are copied to the following file in the SYS$HELP directory (where n is the minor version number): SYS$HELP:CC06n.RELEASE_NOTES ________________________Note ________________________ The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do not delete release notes for previous versions of DEC C (if any). _____________________________________________________ 7. Respond to license registration queries. DEC C supports the OpenVMS License Management Facility (LMF). The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK) for DEC C. The following is an example of such information: DEC C Version 6.0 for OpenVMS VAX Systems Copyright Digital Equipment Corporation 1993, 1998. 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. This kit contains a file summarizing the new features, changes, restrictions, and compatibility issues in this release of DEC C. This file is named CC06n.RELEASE_NOTES and has been placed in SYS$HELP:. 2-6 Installing DEC C This file contains information valuable to DEC C programmers. Please inform your user community of this file's existence. Product: C Producer: DEC Version: 6.0 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 PAK to run the Installation Verification Procedure (IVP). If you have not done so, you should stop the installation, register and load your PAK, and then restart the installation. 8. Choose the IVP option. The installation procedure asks if you want to run the IVP. The IVP for DEC C checks to be sure that the installation is successful. It is recommended that you run the IVP by answering YES to the following prompt: This kit contains an Installation Verification Procedure (IVP) to verify the correct installation of DEC C. The IVP will be left in: SYS$COMMON:[SYSTEST]DECC$IVP.COM After the installation is complete, you can invoke the command file at any time to verify that DEC C is installed and working correctly. * Do you want to run the IVP after the installation [YES]? After DEC C 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 DEC C. 9. Choose the default for the CC command. You will see the prompts described in this step only if your system has a VAX C compiler installed. Installing DEC C 2-7 The CC command is used to invoke either the VAX C or DEC C compiler. If your system has a VAX C compiler already installed on it, you have the option of specifying which compiler will be invoked by default whenever just the CC command verb is used. To invoke the compiler that is not the default, use the CC command with the appropriate qualifier: /DECC for the DEC C compiler, or /VAXC for the VAX C compiler. If VAX C is installed on your system, you can choose the default to use for the CC command: A VAX C compiler was found on your system. The CC command will have the capability to invoke DEC C compiler via the command CC/DECC. The CC command will also have the capability to invoke the VAX C compiler via the command CC/VAXC. You have the choice of the CC command defaulting to execute either: - the DEC C compiler [DECC] - the VAX C compiler [VAXC] If you choose DECC as the default, existing command files using CC to invoke VAX C may not work. Other layered products expecting CC to invoke VAX C during their installation procedure may not install. * The default compiler when only CC is specified, VAXC or DECC [DECC]: Either press Return to accept DECC as the default, or enter VAXC. If VAX C is not installed on the system, the following information is displayed: VAX C is not installed on the system. Should you install VAX C at some future time, you must reinstall DEC C to provide a command line definition for the CC command that can invoke either product. 10.Purge files. * Do you want to purge files replaced by this installation [YES]? The directories SYS$HELP, SYS$MESSAGE, SYS$SYSTEM, DECC$LIBRARY, and SYS$TEST may contain previous versions of DEC C files. These files are replaced during the installation with new files, but the old files are not automatically purged. Purging is recommended. In response to the purging prompt, press Return to purge the files or enter NO to keep them. 2-8 Installing DEC C 11.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. If you chose to have files purged, that work is done now. The following messages are displayed: You have answered all of the questions for this installation. The installation will now execute in 1 to 5 minutes without further intervention, depending on your configuration, installation media, and so forth. The C Runtime Library headers and Starlet headers are installed as a Text Library (.TLB). The traditional text form of the headers (.H files) are also provided for reference purposes only) in the directories: SYS$COMMON:[DECC$LIB.REFERENCE.DECC$RTLDEF] and SYS$COMMON:[DECC$LIB.REFERENCE.SYS$STARLET_C]. Please note that the compiler does not search the reference areas SYS$COMMON:[DECC$LIB.REFERENCE.DECC$RTLDEF] and SYS$COMMON:[DECC$LIB.REFERENCE.SYS$STARLET_C] during compilation. Instead headers are taken from the text library. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.DECC]. Your OpenVMS system will now be updated to include the following new and modified files: Installing DEC C 2-9 [SYSEXE]DECC$COMPILER.EXE [new] [SYSHLP]HELPLIB.HLB [modified] [SYSHLP]CC$HELP*.HTML [new] [SYSHLP]CC06n.RELEASE_NOTES [new] [SYSHLP]CC060_RELEASE_NOTES.PS [new] [SYSLIB]DCLTABLES.EXE [modified] [SYSLIB]DECC$RTLDEF.TLB [new] [SYSLIB]DECC$COMPILED_PRINTF.OLB [new] [DECC$LIB.REFERENCE.SYS$STARLET_C]*.H [new] [DECC$LIB.REFERENCE.DECC$RTLDEF]*.H [new] [SYSMSG]DECC$MSG_SHR.EXE [new] [SYS$STARTUP]DECC$STARTUP.COM [new] [SYSTEST]DECC$IVP.COM [new] [SYSTEST.DECC]DECC$IVP*.* [new] The file SYS$STARTUP:DECC$STARTUP.COM contains commands to be executed at system startup to allow for the best compilation performance. You may want to invoke this command file from your system's site specific startup file. This command file does not have to be invoked for correct operation of DEC C. The end of the installation is indicated by the following message: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... Copyright Digital Equipment Corporation 1993, 1998. 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. 12.Observe the IVP. If you chose to run the IVP, VMSINSTAL now invokes the IVP to verify that DEC C was installed successfully: 2-10 Installing DEC C *-------------------------------------------* * Installation Verification Procedure * * for DEC C * *-------------------------------------------* ***** DEC C Installation Verification Procedure SUCCESSFUL ****** 13.End the installation procedure. Installation of CC V6.n completed at hh:mm Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]CC06n.VMI_DATA VMSINSTAL procedure done at hh:mm $ LOGOUT SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.ss When the installation is complete, you can choose to install more products or to log out (as shown here). If you removed any media from the console drive before beginning the installation, you should replace it now. Be aware that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. 2.2 Error Recovery 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 see the following message: %VMSINSTAL-E-INSFAIL, The installation of DEC C V6.n has failed. If the IVP fails, you see these messages: The DEC C V6.n Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for DEC C V6.n has failed. Installing DEC C 2-11 Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A prerequisite software version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The OpenVMS help library is currently in use. o 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 Section 1.5. If the installation fails, you must restart the in- stallation procedure from step 2 in Section 2.1. 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 DIGITAL field service representative. 2-12 Installing DEC C 3 ________________________________________________________________ After Installing DEC C DEC C is now installed and can be invoked by all users with the CC command. The installation procedure modifies the DCL command table so that the CC 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 CC command must log out and log in again, or use the following DCL command: $ SET COMMAND /TABLES=SYS$LIBRARY:DCLTABLES You can perform the following system management tasks after DEC C is installed: o Running the Installation Verification Procedure (IVP) separately o Editing the system startup and shutdown files o Modifying system parameter settings o Making the product usable on a VAXcluster o Setting user account quotas o Tailoring your system o Enhancing performance o Reporting problems After Installing DEC C 3-1 3.1 Running the Installation Verification Procedure Separately You usually run the IVP during installation. If you want to run the DEC C IVP separately to ensure the integrity of installed files should system problems occur, execute the following command procedure: $ @SYS$SYSROOT:[SYSTEST]DECC$IVP If the IVP fails for any reason, the following message is displayed: DEC C VERSION 6.n TEST FAILED 3.2 Editing and Organizing System Files To provide for automatic startup of DEC C when your system is rebooted, add the command line that starts DEC C to the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM (V5.0 and later) or SYS$MANAGER:SYSTARTUP_V5.COM (V5.x systems): $ @SYS$STARTUP:CCXX$STARTUP.COM You must invoke this command procedure to define the logical names that the compiler needs to find the DEC C header source files and any DEC C++ class library header files. ________________________Note ________________________ SYS$STARTUP:CCXX$STARTUP.COM initializes the DEC C and DEC C++ compile-time environment only. To initialize the DEC C/C++ Run-Time Components environment on applicable OpenVMS VAX systems, execute SYS$STARTUP:CRT$STARTUP.COM according to the instructions in the installation guide for that kit. _____________________________________________________ If your system has DEC C++ for OpenVMS VAX Version 1.1 installed, be sure to note the following changes and required actions: o DEC C++ for OpenVMS VAX Version 1.2 has succeeded Version 1.1. DIGITAL recommends that you upgrade to Version 1.2, which has many problem fixes and a new 3-2 After Installing DEC C installation and startup procedure that cooperates with the procedures used by this DEC C installation. o Beginning with DEC C++ for OpenVMS VAX Version 1.2 and and DEC C for OpenVMS VAX Version 4.0, the default locations for the top-level directories dev:[DECC$LIBRARY] and dev:[CXX$LIBRARY] have changed to SYS$COMMON:[DECC$LIB] and SYS$COMMON:[CXX$LIB], respectively. After installing DEC C for OpenVMS VAX Version 4.0 or higher, the system logical DECC$LIBRARY_INCLUDE points to a new header area. Therefore, if your system has DEC C++ for OpenVMS VAX Version 1.1 installed, be sure to take note of the old location before installing DEC C. o With DEC C Version 4.0 and higher, the location for the library form of the DEC C headers has changed from that used in previous DEC C and DEC C++ versions. The old location was dev:[DECC$LIBRARY.INCLUDE]. The new location is SYS$LIBRARY. o The DEC C Version 4.0 and higher startup is called CCXX$STARTUP.COM and is shared by DEC C and DEC C++. This startup file obsoletes both CC$STARTUP.COM (used in previous test versions of DEC C) and CXX$STARTUP.COM (if DEC C++ for OpenVMS VAX Version 1.1 is installed on your system). Delete CC$STARTUP.COM and CXX$STARTUP.COM and remove them from SYS$STARTUP:SYSTARTUP_xxx.COM. As a reminder to do this, the DEC C installation creates stub copies of both CC$STARTUP.COM and CXX$STARTUP.COM that do nothing but announce that the old versions of these files are obsolete and should be deleted. In summary, unless you want to reuse the obsolete default directories for DECC$LIBRARY_INCLUDE, you should remove the following files from the old areas (dev is selected during DEC C++ Version 1.1 installation; it defaults to SYS$SYSDEVICE): After Installing DEC C 3-3 dev:[DECC$LIBRARY...]*.*;* dev:[000000]DECC$LIBRARY.dir;* SYS$STARTUP:CXX$STARTUP.COM SYS$STARTUP:CC$STARTUP.COM SYS$COMMON[SYSTEST.DECC...]*.*;* SYS$COMMON[SYSTEST]DECC.dir;* SYS$HELP:CC013.RELEASE_NOTES;* If you are installing the DEC C Version 4.0 (or higher) files into the same areas as you chose for the C header files when installing DEC C++ Version 1.1, you can either delete the entire directory tree dev:[DECC$LIBRARY...] before installing the new version, or delete only the following files after installing DEC C: SYS$STARTUP:CXX$STARTUP.COM;* SYS$STARTUP:CC$STARTUP.COM;* dev:[DECC$LIBRARY.SYSTEM]*.*;* dev:[DECC$LIBRARY]SYSTEM.dir;* dev:[DECC$LIBRARY.CRTL]*.*;* dev:[DECC$LIBRARY]CRTL.dir;* dev:[DECC$LIBRARY.INCLUDE]DECC$RTLDEF.TLB_OLD;* SYS$COMMON[SYSTEST.DECC...]*.*;* SYS$COMMON[SYSTEST]DECC.dir;* If you have a system logical or one or more options files that point to the old linker and the old run-time li- braries (RTLs) that resided in dev:[CXX$LIBRARY.SYSTEM]LINK.EXE and dev:[DECC$LIBRARY.CRTL]*.*, you should remove them. That linker is obsolete and the RTLs are made obsolete by the new DEC C/C++ Run-Time Components Version 6.0 for OpenVMS VAX kit (or by your Version 6.0 or later OpenVMS VAX system). 3.3 VAXcluster Considerations If you want to run DEC C on multiple nodes of a VAXcluster, first check to see that you have the appropriate software license (see Section 1.4). Then perform the following steps after you install DEC C: 1. Enter the LICENSE LOAD command, as described in the OpenVMS License Management Utility Manual, to activate the license on each node in the VAXcluster on which DEC C is to be executed. 3-4 After Installing DEC C 2. Log in to the installation node and use the OpenVMS INSTALL Utility to determine whether DECC$COMPILER.EXE is a known image: $ INSTALL INSTALL> LIST SYS$SYSTEM:DECC$COMPILER.EXE If the output of the preceding LIST command shows DECC$COMPILER.EXE to be a known image, perform all of the following steps. Otherwise, perform all of the following steps except step 5. 3. Log in to a node on the cluster. 4. Update the DCL tables on all nodes, if enough global pages are available: SYSMAN>SET ENV/CLUSTER SYSMAN>DO - IF F$GETSYI("CONTIG_GBLPAGES").GT.F$FILE("SYS$SHARE:DCLTABLES.EXE","EOF") - THEN INSTALL REPLACE SYS$SHARE:DCLTABLES 5. If DECC$COMPILER.EXE was established as a known image using the INSTALL utility, enter the following commands: $INSTALL INSTALL> REPLACE SYS$SYSTEM:DECC$COMPILER.EXE This command replaces the INSTALL entry for DECC$COMPILER.EXE. Repeat this step only for those nodes of the cluster on which you activated the DEC C license in step 1. (In most cases, all the nodes will be licensed.) 3.4 User Account Requirements To work with DEC C, user accounts on your system must have certain privileges and quotas. The following sections contain information on these requirements. 3.4.1 Privileges To use DEC C, 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. After Installing DEC C 3-5 3.4.2 User Account Quotas To use DEC C, 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 working set (WSDEF, WSQUOTA, WSEXTENT) and pagefile (PGFLQUOTA) account quotas to improve performance. See Section 1.5.2 for a description of how to verify and change account quotas. 3.5 Enhancing DEC C Performance The following sections include information on system tuning and explain how to install DEC C as a shared image. 3.5.1 Tuning Your System After you install DEC C, you might want to adjust your system to enhance performance or lower the use of some system resources. Information about tuning your system is included in the Guide to OpenVMS Performance Management. 3.5.2 Installing DEC C as a Shared Image If you expect DEC C to be used extensively on your system, you can reduce the system overhead and memory requirements by installing it as a shared image. To install DEC C as a shared image on a system that is currently running, use the OpenVMS INSTALL utility. DIGITAL recommends that you install DEC C as shared on a system that has been rebooted recently, because the available space in the global page table is less likely to be fragmented. To install DEC C as a shared image: 1. Make sure your system has the required number of available global pages and global sections. See Section 1.5.3.1. 2. After you have reset the system parameter values, invoke the OpenVMS INSTALL utility from a privileged account and install DEC C as a shared image by entering the following commands: 3-6 After Installing DEC C $ INSTALL INSTALL> ADD SYS$SYSTEM:DECC$COMPILER.EXE/OPEN/SHARED/HEADER_RESIDENT INSTALL> ADD SYS$MESSAGE:DECC$MSG_SHR.EXE/OPEN/SHARED/HEADER_RESIDENT INSTALL> EXIT 3. Add the following lines to the appropriate system startup command file so that DEC C 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 for OpenVMS Version 5.5-2, for example, is SYS$STARTUP:SYSTARTUP_V5.COM. $ INSTALL ADD SYS$SYSTEM:DECC$COMPILER.EXE/OPEN/SHARED/HEADER_RESIDENT ADD SYS$MESSAGE:DECC$MSG_SHR.EXE/OPEN/SHARED/HEADER_RESIDENT EXIT When you install DEC C as a shared image you need to increase the global pages and global sections parameters as described in Section 1.5.3.1. 3.6 Getting Help and Reporting Problems If an error occurs while DEC C 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: o The name and version number of the operating system you are using o The version number of DEC C you are using o The hardware system you are using (such as a model number) o A brief description of the problem (one sentence if possible) After Installing DEC C 3-7 o 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 DEC C 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 DEC C 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 DEC C documentation to the following Internet address: decc_docs@bookie.zko.dec.com To obtain information about purchasing a DIGITAL Software Product Services Support Agreement or other support services, please contact your local DIGITAL sales representative. 3-8 After Installing DEC C A ________________________________________________________________ Sample Installation This appendix contains a sample installation of the components on the DEC C kit. Be aware that this is only a sample. Sometimes the installation procedure is modified in maintenance updates of this product. Because this installation guide is not always revised for maintenance updates, be sure to read the Read Before Installing DEC C for OpenVMS VAX Systems, Version 6.n letter before you install this product. This letter notes any significant changes to the installation sample shown here. This sample was run on a system that had no previous version of DEC C installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. The sample installation assumes that DECnet has been shut down, that no users are logged on 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. $ @VMSINSTAL CC06n [KITS] OPTIONS N OpenVMS VAX Software Product Installation Procedure V6.1 It is 23-October-1998 at 11:39. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: CC V6.0 Beginning installation of CC V6.0 at 11:39 Sample Installation A-1 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 4 * Do you want to continue the installation [NO]? yes %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. DEC C V6.0-000 for OpenVMS VAX Copyright Digital Equipment Corporation 1993, 1998. 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]? DEC C requires a Product Authorization Key (PAK) be registered and loaded. Answer the following question with YES if at least one 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: C Producer: DEC Version: 6.0 Release Date: dd-mmm-yyyy * Does this product have an authorization key registered and loaded? yes This kit contains an Installation Verification Procedure (IVP) to verify the correct installation of the DEC C compiler. The IVP will be placed in: SYS$TEST:DECC$IVP.COM A-2 Sample Installation After the installation is complete, you can invoke the command file at any time to reverify that DEC C is installed and working correctly. * Do you want to run the IVP after the installation [YES]? A VAX C compiler was found on your system. The CC command will have the capability to invoke DEC C compiler via the command CC/DECC. The CC command will also have the capability to invoke the VAX C compiler via the command CC/VAXC. You have the choice of the CC command defaulting to execute either: - the DEC C compiler [DECC] - the VAX C compiler [VAXC] If you choose DECC as the default, existing command files using CC to invoke VAX C may not work. Other layered products expecting CC to invoke VAX C during their installation procedure may not install. * The default compiler when only CC is specified should be [DECC]: Choose a location to place the primary header files used for interfacing with the DEC C Run Time Library and with OpenVMS system services. Answer To place files in ------- --------------------------------------------------------- D SYS$COMMON:[DECC$LIB.INCLUDE] E In the existing DECC$LIBRARY_INCLUDE: SYS$COMMON:[DECC$LIB.INCLUDE] A An alternative location you specify in the next question. You may want to use an alternative location to save space on the system device and to reduce disk I/O traffic during compilations. * DECC$LIBRARY_INCLUDE location, [D]efault, [A]lternative, or [E]xisting [E]: DECC$LIBRARY_INCLUDE will be SYS$COMMON:[DECC$LIB.INCLUDE]. All questions regarding the installation of DEC C have been asked. The installation will now continue for between 10 minutes and one hour, depending on your CPU type and the installation options you have chosen. DEC C V6.0-000 : providing help and the command line. DEC C V6.0-000 : providing images and libraries. %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.DECC]. Sample Installation A-3 Please add the SYS$STARTUP:CCXX$STARTUP.COM to the system startup procedure called SYS$STARTUP:SYSSTARTUP_xxx. To use DEC C for OpenVMS VAX on other nodes of a VAXcluster: 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 files: [SYSEXE]DECC$COMPILER.EXE [new] [SYSHLP]HELPLIB.HLB [modified] [SYSHLP]CC$HELP*.HTML [new] [SYSHLP]CC06n.RELEASE_NOTES [new] [SYSHLP]CC060_RELEASE_NOTES.PS [new] [SYSLIB]DCLTABLES.EXE [modified] [SYSLIB]DECC$RTLDEF.TLB [new] [SYSLIB]DECC$COMPILED_PRINTF.OLB [new] [DECC$LIB.REFERENCE.SYS$STARLET_C]*.H [new] [DECC$LIB.REFERENCE.DECC$RTLDEF]*.H [new] [SYSMSG]DECC$MSG_SHR.EXE [new] [SYS$STARTUP]DECC$STARTUP.COM [new] [SYSTEST]DECC$IVP.COM [new] [SYSTEST.DECC]DECC$IVP*.* [new] %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Beginning DEC C Installation Verification Procedure ... Copyright Digital Equipment Corporation 1993, 1998. 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 standard headers... Test DEC C Run Time Library operation... Successful installation of DEC C Version C V6.1 A-4 Sample Installation End of DEC C Installation Verification Procedure Installation of CC V6.0 completed at 12:15 VMSINSTAL procedure done at 12:16 Sample Installation A-5