Jump to 
content
HP.com Home Products and Services Support and Drivers Solutions How to Buy
»  Contact HP

 

HP C

HP C
Installation Guide for
OpenVMS Alpha Systems


Previous Contents

1.6.2 Side Effects and Restrictions on Multiple Versions

Installing this kit provides the latest DECC$RTLDEF.TLB file and the latest documentation, even if you select the option of having the new compiler as the alternate compiler. Because it is upwardly compatible, the new DECC$RTLDEF.TLB does not adversely impact a preexisting Version 6-based compiler.

If you run an older installation procedure, you should rerun the V7.n installation procedure to make sure you have all the files to support V7.n as a coexistent compiler.

Note that there are two logical names involved in establishing the compiler version: one for the compiler image and one for its message file. Beginning with HP C V6.4, the compiler issues a diagnostic if it is invoked with the wrong version of the message file; previous 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, use the $ SHOW LOGICAL DECC$COMPILER* command to check that you have matched versions of the files designated by the two logicals. 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 the message "%SHOW-S-NOTRAN, no translation for logical name DECC$COMPILER*".

1.6.3 Installation Procedure Changes

When you install HP C Version 6.4 or higher 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.


Chapter 2
Installing HP C

This chapter explains how to install HP C:

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

2.1 Installation Procedure

The HP 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 HP C, use the following installation name:


    CC07n
    

    Where n represents the minor (point) release number of HP C, such as CC065 for Version 6.5 or CC071 for Version 7.1. Refer to the label on the HP C distribution kit or the HP 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 [CC07n.KIT], where n is the minor release number.
    To specify the device name on the @VMSINSTAL command line, type:


    DKA400:[CC07n.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 HP C and shows the system response. This example uses the OPTIONS N release note parameter.


    $ @SYS$UPDATE:VMSINSTAL CC07n DKA400:[CC07n.KIT] OPTIONS N 
     
          OpenVMS Alpha Software Product Installation Procedure V7.3
     
     
    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.3.1.
    • 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:[CC07n.KIT]
    

    If this prompt appears, enter the name of the distribution (media) device and directory the contains the HP C kit (save set). For example, if the media is contained on a CD located on unit DKA400:, enter DKA400:[CC07n.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, HP 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 HP 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 V7.n
     
        Beginning installation of CC V7.n at hh:mm   
    %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:CC.RELEASE_NOTES
    

    Note

    Do not delete release notes for previous versions of HP C (if any).
  7. Read license information.


      HP C Version 7.n for OpenVMS Alpha Systems 
      
      Copyright 2005 Hewlett-Packard Development Company, L.P. 
     
      Confidential computer software. Valid license from HP 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. 
    

  8. Respond to HP C multiple-version queries.
    The installation procedure detects any previous version of the HP C compiler installed on your system (back to Version 6.0), and asks if you want to keep it or supersede it with the new version you are installing. Enter YES to keep the previous version, or enter NO to supersede it with the new version:


       A C V6.0-001 compiler was found on your system. 
       Type YES to keep this compiler on your system either as 
       the default system compiler or as an alternate compiler. 
       Type NO to supersede C V6.0-001. 
    


    * Should the existing V6.0-001 system compiler be preserved [NO]: YES
    

    If you answer YES to the previous question, the installation procedure then asks if you want the currently installed ("old") compiler to remain the default compiler on your system. Enter YES to keep the "old" version as the system default compiler. Enter NO to make the "new" version the default system compiler:


       Type NO to have the compiler on this kit become the default system compiler 
       and to have the currently installed compiler saved as an alternate compiler. 
       Type YES to keep the current system compiler as the default compiler 
       and to have the compiler on this kit available as an alternate compiler. 
       Alternate compilers can be invoked with the cc command after invoking 
       sys$system:decc$set_version.com passing a version_number. 
    


    Should this V6.0-001 system compiler remain the default when cc is 
    typed [NO]: [Return]
    

  9. Respond to license registration query for the new compiler.
    HP C supports the OpenVMS License Management Facility (LMF). The installation procedure displays license information about your product and asks if you have registered and loaded your Product Authorization Key (PAK) for HP C. The following is an example of such information:


         Product:       C 
         Producer:      DEC 
         Version:       7.1 
         Release Date:  dd-mmm-yyyy 
    


    * Does this product have an authorization key registered and loaded?: yes [Return]
    

    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.

  10. Choose the IVP option.
    The installation procedure asks if you want to run the IVP. The IVP for HP C checks to be sure that the installation is successful. It is recommended that you run the IVP; answer YES to the following prompt:


        This kit contains an Installation Verification Procedure (IVP) 
        to verify the correct installation of HP 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 HP C is installed and 
        working correctly. 
     
    * Do you want to run the IVP after the installation [YES]? 
    

    After HP 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 HP C.

  11. Decide whether to install the documentation.


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


    * Should these manuals be provided [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$ALPHA_HELP_07n]INDEX.HTM 
    

  12. Read release-notes informational message.


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

  13. 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 HP 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.

  14. 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 5 to 15 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_V06_00-001.EXE      [renamed] 
        [SYSMSG]DECC$COMPILER_MSG_V06_01-001.EXE  [renamed] 
        [SYSEXE]DECC$COMPILER.EXE                 [new] 
        [SYSMSG]DECC$COMPILER_MSG.EXE             [new] 
        [SYSHLP]HELPLIB.HLB                       [modified] 
        [SYSHLP]CC$HELP*.HTML                     [new] 
        [SYSHLP.CC$ALPHA_HELP_07n]                [new] 
        [SYSHLP]CC.RELEASE_NOTES                  [new] 
        [SYSHLP]CC_RELEASE_NOTES.PS               [new] 
        [SYSLIB]DCLTABLES.EXE                     [modified] 
        [SYSLIB]DECC$COMPILED_PRINTF.OLB          [new] 
        [SYSLIB]DECC$RTLDEF.TLB                   [new] 
        [DECC$LIB.REFERENCE.SYS$STARLET_C]*.H     [new] 
        [DECC$LIB.REFERENCE.DECC$RTLDEF]*.H       [new] 
        [SYS$STARTUP]DECC$STARTUP.COM             [modified] 
        [SYSTEST]DECC$IVP.COM                     [new] 
        [SYSEXE]DECC$SET_VERSIONS.COM             [new] 
        [SYSEXE]DECC$SHOW_VERSIONS.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 HP C. 
    

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


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

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


       Copyright 2005 Hewlett-Packard Development Company, L.P. 
     
       Confidential computer software. Valid license from HP 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. 
     
       Beginning HP C V7.n Installation Verification Procedure 
     
       Image Check Complete 
       License Check Complete 
       Version Check Complete 
       Help Check Complete 
       Message Check Complete 
       Header Check Complete 
       Run Time Library Check Complete 
     
       HP C V7.n Installation Verification Procedure Successful 
    

  16. The installation procedure ends.


       Installation of CC V7.n completed at hh:mm
     
    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
     
    Creating installation data file: VMI$ROOT:[SYSUPD]CC07n.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.


Previous Next Contents

Privacy statement Using this site means you accept its terms
© 2007 Hewlett-Packard Development Company, L.P.