HP OpenVMS Systems

When you install this kit, it provides the latest CLD file (to established DCL tables), the latest decc$rtldef.tlb, and the latest documentation, even if you select the option of having the new compiler as the alternate compiler. The new CLD file and the new decc$rtldef.tlb do not adversely impact a preexisting Version 6-based compiler because they are upwardly compatible. However, if you attempt to use a new compiler option with an older compiler, you will no longer get a DCL error that the option is not supported. Instead, the option will be silently ignored. For example, note that before installation of Version 6.4, the following would have produced: "%DCL-W-IVQUAL, unrecognized qualifier ...."

$@sys$system:decc$set_version.com 6.2
$ cc /first_include foo.c  ! /first_include new in 6.4
$ !No complaint

And because you must have the newest CLD file and header files in order to use the newest compiler, if you run an older installation procedure to put an older compiler back on your system, you must then re-run the Version 6.4 installation to get the newest files.

Note that there are two logical names involved in establishing the compiler version: one for the compiler image and one for its message file. This version of the compiler issues a diagnostic if it is invoked with the wrong version of the message file, but prevous versions of the compiler do not detect this situation. If you find that an older version of the compiler is issuing diagnostics that do not make sense for the code construct they are attached to, or if the message text is missing and only a message number is issued, check that you have matched versions of the files designated by the two logicals using the command "$ show logical decc$compiler*". The response should show matching version-numbered files as in the example that selects the Version 6.2 compiler. Or if you are using the system compiler, the response should be "%SHOW-S-NOTRAN, no translation for logical name DECC$COMPILER*".

1.6.3 Installation Procedure Changes

When you install Compaq C Version 6.4 on a system that already has a Version 6.0 or higher compiler installed, you are given the chance to preserve the currently installed system compiler. To do this, answer YES to the following question (the xxx will be replaced by the full version number of the existing system compiler):

"Should the existing xxx system compiler be preserved [NO]:"

If you answer NO, the installation proceeds in the traditional manner, overwriting the currently installed system compiler.

If you answer YES, you are then asked an additional question. To get the traditional behavior of installing the kit compiler as the system default, answer NO to the question:

"Should this xxx system compiler remain the default when cc is typed [NO]:"

Because you have previously asked to preserve the existing system compiler, that compiler is made an alternate compiler before the new system compiler is installed from the kit. If you answer YES to the question, the kit compiler is installed as an alternate compiler with a name that is based on its ident, and the existing system default compiler remains the default.

This chapter explains how to install Compaq C:

• Section 2.1 contains a step-by-step description of the installation procedure.
• Section 2.2 covers error recovery considerations.

The Compaq C installation procedure consists of a series of questions and informational messages. See Appendix A for sample installations.

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 installation 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

   saveset-name

   The installation name for the component. For Compaq C, use the following installation name:

   CC06n

   
   Where n represents the minor (point) release number of Compaq C, such as CC064 for Version 6.4. Refer to the label on the Compaq C distribution kit or the Compaq 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:

   • 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).
   • Get save set (G): Stores product save sets temporarily on a magnetic tape or in a disk directory.
   • File log (L): Logs all activity to the terminal during installation.
   • 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 Compaq 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:
   • Whether you logged in to a privileged account. We recommend 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 Section 1.5.
   • 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.
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 Compaq 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, Compaq 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 Compaq 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.
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.
   • Select option 1 to immediately display the release notes online. You can terminate the display at any time by pressing Ctrl/C.
   • 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.
   • Select option 3 to immediately display the release notes online and then be prompted for a queue name for the printed version.
   • Select option 4 if you have already reviewed the release notes and are restarting the installation.
   
   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 Compaq C (if any).

7. Respond to license registration queries.
   Compaq C supports the OpenVMS License Management Facility (LMF). The installation procedure displays license information about your product, asks if you want Compaq C documentation installed, and asks if you have registered and loaded your Product Authorization Key (PAK) for Compaq C. The following is an example of such information:

   Compaq C Version 6.4 for OpenVMS VAX Systems Copyright 2001 Compaq Computer Corporation Compaq and the Compaq logo Registered in U.S. Patent and Trademark Office. Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Product: C Producer: DEC Version: 6.4 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. Decide whether to install the documentation.

   HTML, postscript and text versions of the Compaq C Users Guide, Language Reference Manual and RTL Reference Manual may be optionally installed into SYS$COMMON:[SYSHLP.CC$VAX_HELP_064]. These documents consume approximately 40000 blocks.

   * Should these manuals be provided [NO]: yes [NO]? yes [Return]

   
   If you have adequate disk space and wish to install the C documentation, enter Yes. Once the documentation is installed, you can browse the HTML version by opening the following file from your browser:

   SYS$COMMON:[SYSHLP.CC$VAX_HELP_064]INDEX.HTM

9. Read information about Release Notes.

   This kit contains a file summarizing the new features, changes, restrictions, and compatibility issues in this release of Compaq C. This file is named CC064.RELEASE_NOTES and has been placed in SYS$HELP:. This file contains information valuable to Compaq C programmers. Please inform your user community of this file's existence.

10. Choose the IVP option.
    The installation procedure asks if you want to run the IVP. The IVP for Compaq 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 Compaq 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 Compaq C is installed and working correctly. * Do you want to run the IVP after the installation [YES]?

    
    After Compaq 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 Compaq C.
11. 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.
    The CC command is used to invoke either the VAX C or Compaq 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 Compaq 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 the Compaq 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 Compaq 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 Compaq C to provide a command line definition for the CC command that can invoke either product.

12. 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 Compaq 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.
13. 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 10 to 60 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: [SYSEXE]DECC$COMPILER.EXE [new] [SYSHLP]HELPLIB.HLB [modified] [SYSHLP]CC$HELP*.HTML [new] [SYSHLP]CC06n.RELEASE_NOTES [new] [SYSHLP]CC06n_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 Compaq C.

    
    The end of the installation is indicated by the following message:

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

14. Observe the IVP.
    If you chose to run the IVP, VMSINSTAL now invokes the IVP to verify that Compaq C was installed successfully:

    Beginning COMPAQ C V6.n Installation Verification Procedure Copyright 2001 Compaq Computer Corporation Compaq and the Compaq logo Registered in U.S. Patent and Trademark Office. Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Image Check Complete License Check Complete Version Check Complete Message Check Complete Header Check Complete Run Time Library Check Complete COMPAQ C V6.n Installation Verification Procedure Successful Installation of CC V6.n completed at hh.mm VMSINSTAL procedure done at hh:mm

15. The installation procedure ends.

    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.