Make sure you have downloaded the latest kit file. For example, AXPVMS-C-Xnnnn-nnn.ZIP.?

Use the UNZIP utility to extract the installation files.

SYS$COMMON:[SYSHLP.UNSUPPORTED.ZIP]
SYS$COMMON:[SYSHLP.UNSUPPORTED.UNZIP]

To be able to use the UNZIP command, create a foreign command that will run the UNZIP utility, for example:

$ UNZIP == "$SYS$COMMON:[SYSHLP.UNSUPPORTED.UNZIP]UNZIP.EXE"

For information on how to use this utility, execute UNZIP.

Log in to a privileged account on the system (or cluster) where you will install VSI C. This account must have the SETPRV privilege enabled.

You can check what privileges are enabled for your process by entering the following command:

$ SHOW PROCESS/PRIVILEGES

Invoke the VMSINSTAL command procedure.

You should invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. The VMSINSTAL procedure resides in the SYS$UPDATE directory. Set your default directory to SYS$UPDATE. For example:

Username: SYSTEM
Password:

$ SET DEFAULT SYS$UPDATE
$ @SYS$UPDATE:VMSINSTAL saveset-name device-name [OPTIONS option-list]

$ @SYS$UPDATE:VMSINSTAL CC07n $1$DGA700:[KITS] OPTIONS N

    OpenVMS  Software Product Installation Procedure V8.4-2L1

It is 2-NOV-2023 at 12:26.

Enter a question mark (?) at any time for help.

If you do not supply 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 whatever option you want on the VMSINSTAL command line.

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 the Return key. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation.

* Where will the distribution volumes be mounted:

If this prompt is displayed, type the name of the device and directory that contain the VSI C installation files.

Verify the product being installed.

The following products will be processed:

  CC V7.n


        Beginning installation of CC V7.n at 12:26

    **********************************************************************
%VMSINSTAL-I-VALSIGN, Performing product kit validation of signed kits ...
Success

%VMSINSTAL-I-VALPASSED, validation of $1$DGA700:[KITS]CC07n.A_VNC succeeded
Success

%VMSINSTAL-I-VALPASSED, validation of $1$DGA700:[KITS]CC07n.B_VNC succeeded
%VMSINSTAL-I-RESTORE, Restoring product save set A ...

The product name and version are displayed. The save set (A) is restored to a subdirectory of SYS$UPDATE.

Select a release notes option.

If you specified OPTIONS N when you invoked VMSINSTAL, you are asked to choose one of the four options for reviewing the release notes:

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]:

$ HELP C RELEASE_NOTES

* Do you want to continue the installation [NO]?: YES 
%VMSINSTAL-I-RELMOVED, The product's release notes have been
successfully moved to SYS$HELP. 

SYS$HELP:CC07n.RELEASE_NOTES

Respond to VSI C multiple-version queries.

The installation procedure detects any previous version of the VSI C compiler installed on your system, 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 V7.n-nnn 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 V7.n-nnn.

* Should the existing V7.n-nnn 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:

  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 V7.n-nnn system compiler remain the default when cc is typed [NO]:

Respond to license registration query for the new compiler.

If you have not registered and loaded your PAK, you must answer NO to the following question:

        Product:      C
        Producer:     VSI
        Version:      7.n
        Release Date: dd-mm-yyyy


* Does this product have an authorization key registered and loaded? NO
%CC-I-NOLICENSE, DEC C V7.n Product Authorization Key (PAK) is not registered and loaded.
%CC-I-NOLICENSE2, The IVP cannot be run without the PAK.

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.

Choose the IVP option.

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

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

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

Decide whether to install the documentation.

    HTML, postscript and text versions of the VSI 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

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

Read release-notes informational message.

    This kit contains a file summarizing the new features, changes,
    restrictions, and compatibility issues in this release of VSI C.
    This file is named CC07n.RELEASE_NOTES and has been placed in
    SYS$HELP:.

    This file contains information valuable to VSI C programmers.
    Please inform your user community of this file's existence.

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 VSI 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 Enter to purge the files or enter NO to keep them.

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 minutes without further
intervention, depending on your configuration, 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_V07_04-001.EXE [renamed]
  [SYSMSG]DECC$COMPILER_MSG_V07_04-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 VSI C.

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

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

Observe the IVP.

If you chose to run the IVP, VMSINSTAL now invokes the IVP to verify that VSI 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 VSI 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

    VSI C V7.n Installation Verification Procedure Successful

The installation procedure ends.

        Installation of CC V7.n completed at 12:28

    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

    Creating installation data file: VMI$ROOT:[SYSUPD]CC07n.VMI_DATA


        VMSINSTAL procedure done at 12:28

Make sure you have downloaded the latest kit file. For example, X86VMS-C-Xnnnn-nnn.ZIP

Use the UNZIP utility to extract the installation files.

SYS$COMMON:[SYSHLP.UNSUPPORTED.ZIP]
SYS$COMMON:[SYSHLP.UNSUPPORTED.UNZIP]

To be able to use the UNZIP command, create a foreign command that will run the UNZIP utility, for example:

$ UNZIP == "$SYS$COMMON:[SYSHLP.UNSUPPORTED.UNZIP]UNZIP.EXE"

For information on how to use this utility, execute UNZIP.

Log in to a privileged account on the system (or cluster) where you will install VSI C. This account must have the following privileges enabled:

If your process has the SETPRV privilege, you can enable these privileges by entering the following command:

$ SET PROCESS/PRIVILEGE=(BYPASS,CMKRNL,SYSLCK,SYSPRV)

To check whether your process has these privileges enabled, enter the following command:

$ SHOW PROCESS/PRIVILEGES

$ PRODUCT EXTRACT RELEASE_NOTES C /SOURCE=disk:[directory]

In this command, disk:[directory] is the specification of the disk and directory containing the product installation files. If your process default directory is the same directory that contains the VSI C product distribution files, you can specify the source directory as /SOURCE=[].

$ TYPE/PAGE CC.RELEASE_NOTES

Set the default directory to a writeable directory to allow the IVP to succeed. Then run the PRODUCT INSTALL command, pointing to the kit location. For example:

$ SET DEFAULT SYS$MANAGER
$ PRODUCT INSTALL C /SOURCE=kit-device:[kit-location]

Installation takes about 2-5 minutes, depending on your system. When installation has been completed, the DCL $ prompt reappears.

To obtain a list of files installed, enter the following command:

$ PRODUCT SHOW OBJECT /PRODUCT=C

Enter the LICENSE LOAD command, as described in the VSI OpenVMS License Management Utility Guide, to activate the license on each node in the cluster on which VSI C is to be executed.

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.

Log in to a node on the cluster.

Run the OpenVMS INSTALL utility as described in Section 3.6.2, “Installing VSI C as a Shared Image”, with the following exceptions:

Repeat Step 3 and Step 4 for each node of the cluster.