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:

• Running the Installation Verification Procedure (IVP) separately
• Editing the system startup files
• Making the product usable on an OpenVMS cluster
• Setting user account privileges and quotas
• Enhancing performance
• Reporting problems

The following sections describe these tasks in detail.

3.1 Running the Installation Verification Procedure Separately

You usually run the IVP during installation. If you want to run the IVP separately to ensure the integrity of installed files if system problems should occur, execute the following command procedure:

$ @SYS$TEST:DECC$IVP.COM

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

DEC C VERSION V5.n TEST FAILED

3.2 Editing the System Files

You must edit the system startup file 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. DEC C cannot start until after the network has started. You must position this new command line after the line that invokes the network startup command procedure. The following example shows the network startup command line followed by the DEC C startup command line:

$ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:DECC$STARTUP.COM

3.3 OpenVMS Cluster Considerations

If you want to run DEC C on multiple nodes of an OpenVMS cluster, first check to see that you have the appropriate software license (see Section 1.3). 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 cluster on which DEC C is to be executed.
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 4b.

3. Log in to a node on the cluster.
4. Run the OpenVMS INSTALL utility as described in Section 3.5.2, with the following exceptions:
   1. After invoking the OpenVMS INSTALL utility, enter the following command:

      INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE

      
      This command updates the DCL tables. It should be entered on each node in the cluster, regardless of whether you activated the DEC C license (step 1) on all of the nodes.

   2. If DECC$COMPILER.EXE was established as a known image using the INSTALL utility, enter the following command:

      INSTALL> REPLACE SYS$SYSTEM:DECC$COMPILER.EXE

      
      This command replaces the INSTALL entry for DECC$COMPILER.EXE. It should be entered only on those nodes on which you activated the DEC C license in step 1. (In most cases, all of the nodes will be licensed.)

5. Repeat steps 3 and 4 for each node of the cluster.

Some 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 DEC C.

3.4.1 User Privileges

To use DEC C, each account must have 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 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.4.3.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 explains 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. General information about tuning an OpenVMS 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. It is recommended 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. Determine the number of available global pagelets and global sections on your system. You will need to increase them. Section 1.4.2 contains guidelines for showing and setting these parameters.
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:

   $ INSTALL INSTALL> ADD SYS$SYSTEM:DECC$COMPILER.EXE/OPEN/SHARED/HEADER_RESIDENT INSTALL> ADD SYS$MESSAGE:DECC$COMPILER_MSG.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 is SYS$MANAGER:SYSTARTUP_VMS.COM.

   $ INSTALL :== $INSTALL/COMMAND_MODE $ INSTALL ADD SYS$SYSTEM:DECC$COMPILER.EXE/OPEN/SHARED/HEADER_RESIDENT ADD SYS$MESSAGE:DECC$COMPILER_MSG.EXE/OPEN/SHARED/HEADER_RESIDENT EXIT

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:

• The name and version number of the operating system you are using
• The version number of DEC C 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 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@casdoc.enet.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.

This appendix contains a sample installation of the components on the DEC C kit. 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 Alpha Systems Version 5.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.

$ @sys$update:vmsinstal CC053 DKA400:[CC053.KIT] options n OpenVMS Alpha Software Product Installation Procedure X5F7-SSB It is 10-April-1996 at 14:07. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? yes The following products will be processed: CC V5.3 Beginning installation of CC V5.3 at 14:07 %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]: 2 * Queue name [SYS$PRINT]: * Do you want to continue the installation [NO]? yes %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. DEC C Version V5.3 for OpenVMS Alpha Systems Copyright Digital Equipment Corporation 1993, 1994, 1995, 1996. 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 CC053.RELEASE_NOTES and has been placed in SYS$HELP:. This file contains information valuable to DEC C programmers. Please inform your user community of this file's existence. Product: C Producer: DEC Version: 5.3 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 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]? * Do you want to purge files replaced by this installation [YES]? yes 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 modified to include the following new and modified files: [SYSEXE]DECC$COMPILER.EXE [new] [SYSHLP]HELPLIB.HLB [modified] [SYSHLP]CC053.RELEASE_NOTES [new] [SYSLIB]DCLTABLES.EXE [modified] [SYSLIB]DECC$RTLDEF.TLB [new] [DECC$LIB.REFERENCE.SYS$STARLET_C]*.H [new] [DECC$LIB.REFERENCE.DECC$RTLDEF]*.H [new] [SYSMSG]DECC$COMPILER_MSG.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. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Copyright Digital Equipment Corporation 1993, 1994, 1995, 1996. 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. *-------------------------------------------* * Installation Verification Procedure * * for DEC C * *-------------------------------------------* ****** DEC C Installation Vertification Procedure SUCCESSFUL ****** *** DEC C Installation Verification Procedure *** ***** Ending at 10-APR-1996 13:05:03.81 ***** Installation of CC V5.3 completed at 13:05 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]CC053.VMI_DATA VMSINSTAL procedure done at 13:05

Previous

Contents

Contents