|
|
|
|
HP C
|
| Previous | Contents |
This chapter explains how to install HP C:
The installation procedure loads HP C product distribution files onto the system disk on the system where you perform the installation.
Follow these steps to install HP C from the OpenVMS I64 Software Products Library CD-ROM set:
$ SET PROCESS/PRIVILEGE=(BYPASS,CMKRNL,SYSLCK,SYSPRV) |
$ SHOW PROCESS/PRIVILEGES |
$ SHOW DEVICE DKA400 |
DKA400 is the device name used in examples in this document to show where the appropriate media CD-ROM has been mounted. |
$ MOUNT DKA400 label |
$ DIRECTORY *.PCSI Directory DKA400:[dir.subdir] HP-I64VMS-C-V0701-nnnn-1.PCSI Total of 2 files. |
$ PRODUCT EXTRACT RELEASE_NOTES C /SOURCE=disk:[dir] |
$ TYPE/PAGE CC.RELEASE_NOTES |
$ PRODUCT INSTALL C /SOURCE=node::disk:[kit_dir] |
1 - HP I64VMS C V7.1-002 Layered Product
2 - All products listed above
? - Help
E - Exit
Choose one or more items from the menu: 1
The following product has been selected:
HP I64VMS C V7.1-002 Layered Product
Do you want to continue? [YES] [Return]
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
HP I64VMS C V7.1-002: HP C for OpenVMS Industry Standard
Copyright 2004 Hewlett-Packard Development Company, L.P.
This software product is sold by Hewlett-Packard Company
PAKs used: C-USER
Do you want the defaults for all options? [YES]
Copyright 2004 Hewlett-Packard Development Company, L.P.
HP, the HP logo, Alpha and OpenVMS are trademarks of
Hewlett-Packard Development Company, L.P. in the U.S. and/or
other countries.
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 Date for Commercial
Items are licensed to the U.S. Government under vendor's
standard commercial license.
Do you want to review the options? [NO] [Return]
Execution phase starting . . .
The following product will be installed to destination:
HP I64VMS C V7.1-002 DISK$ICCSYS:[VMS$COMMON.]
Portion done: 0%...90%...100%
The following product has been installed:
HP I64VMS C V7.1-002 Layered Product
%PCSI-I-IVPEXECUTE, executing test procedure for HP I64VMS C V7.1-002 ...
%PCSI-I-IVPSUCCESS, test procedure completed successfully
HP I64VMS C V7.1-002: HP C for OpenVMS Industry Standard 64 for
Integrity Servers
The compiler is now available from the command line of newly created processes.
To enable access to the compiler from the command line of a currently
running process (such as this one), execute:
SET COMMAND/TABLE=SYS$COMMON:[SYSLIB]DCLTABLES
The release notes are located in the file SYS$HELP:CC.RELEASE_NOTES
for the text form and SYS$HELP:CC_RELEASE_NOTES.PS for the postscript form.
$
|
$ PRODUCT SHOW OBJECT /PRODUCT=C |
To use other features of the PCSI utility, see the POLYCENTER Software Installation Utility User's Guide.
Errors can occur during the installation if any of the following conditions exist:
For descriptions of error messages generated by these and related conditions, see the OpenVMS I64 documentation on system messages and software installation or the online HELP/MESSAGE command. Take the appropriate action described in the message.
For information on system requirements for installing HP C, see Section 1.4.
To report a problem to HP, see Section 3.7.
You can perform the following tasks after HP C is installed:
The HP C Installation Verification Procedure (IVP) runs automatically during HP C installation.
If system problems occur, you should run the HP C IVP separately to ensure the integrity of the installed files. To run the IVP, enter the following command:
$ @SYS$TEST:DECC$IVP.COM |
If any problems are encountered, a message like one of the following appears:
HP C VERSION 7.n Installation Verification FAILED HP C VERSION 7.n Installation Verification did not run HP C VERSION 7.n Installation Verification ABORTED |
You must edit the system-wide startup file to provide for automatic startup of HP C when your system is rebooted.
Add the command line that starts HP C to the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM. HP C cannot start until after the network has started, so 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:
$ @SYS$MANAGER:STARTNET.COM |
If you want to run HP C on multiple nodes of an OpenVMS cluster, first check to see that you have the appropriate software license (see Section 1.6). Then perform the following steps after you install HP C:
$ INSTALL INSTALL> LIST SYS$SYSTEM:DECC$COMPILER.EXE |
INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE |
INSTALL> REPLACE SYS$SYSTEM:DECC$COMPILER.EXE |
HP 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 |
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 HP C.
To use HP C, each account must have TMPMBX and NETMBX privileges. Use the OpenVMS AUTHORIZE utility to determine whether users have the privileges they require.
To use HP 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.
Use the OpenVMS Authorize Utility from a suitably privileged account to change the process quotas in the user authorization file (UAF). Some sites may restrict the use of the Authorize Utility to certain accounts or people.
After the quotas for the account have been changed, the user should log out of the account and log in again for the new quotas to take effect.
For information on using the Authorize Utility, see the OpenVMS System Manager's Manual: Essentials.
The following sections include information on system tuning and explain how to install HP C as a shared image.
After you install HP 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.
If you expect HP 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 HP C as a shared image on a system that is currently running, use the OpenVMS INSTALL utility. It is recommended that you install HP 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 HP C as a shared image, determine the number of available global pagelets and global sections on your system. You will need to increase them. Section 1.7.2 contains guidelines for showing and setting these parameters.
If you encounter a problem while using HP C, see the release notes. If the problem is unresolved, report it to HP. Depending on the type of support you have and the nature of the problem, take one of the following actions:
This appendix lists the files that are added to or updated on your OpenVMS system during installation. Note that some files may not be installed depending on selected options or your system's configuration or operating system version.
[SYS$SYSTEM]DECC$COMPILER.EXE [new] [SYS$MESSAGE]DECC$COMPILER_MSG.EXE [new] [SYS$LIBRARY]DECC$CLD.CLD [new] [SYS$HELP]HELPLIB.HLB [modified] [SYS$SYSTEM]CXX$DEMANGLE.EXE [new] [SYS$LIBRARY]DCLTABLES.EXE [modified] [SYS$HELP.CC$HELP]*.* [new] [SYS$HELP]CC.RELEASE_NOTES [new] [SYS$HELP]CC_RELEASE_NOTES.PS [new] [SYSTEST]DECC$IVP.COM [new] |
This appendix lists the more common diagnostic messages you might see during product installation. If you encounter a message not shown here, use the HELP/MESSAGE command to display information about it. If you add the /LOG qualifier to the PRODUCT INSTALL command, many additional informational messages will be displayed, which can be ignored.
FAILCONF, failed to resolve conflicting requirements for 'object-type'
'object-name'
Explanation: More than one product supplies a managed object of the same
name, type, and scope. They cannot coexist because of a
conflict in the objects' properties. Files, directories, and
library modules are examples of managed objects.
User Action: Report the problem to HP.
INSTALLERR, error executing DCL INSTALL command
Explanation: The POLYCENTER Software Installation utility installs a file
as a known image by having the DCL command INSTALL execute in
a subprocess. The INSTALL command failed.
User Action: Take action based on the accompanying messages. If you specify
the /TRACE qualifier when you retry the operation, you can
view the command sent to the subprocess.
IVPFAILURE, test procedure completed with an error status
Explanation: The installation verification test procedure for the product
completed with an exit status that indicates a failure. If you
were executing a PRODUCT INSTALL command, the product has been
completely installed, but its test procedure failed.
User Action: Take action based on the accompanying messages. If you specify
the /TRACE qualifier when you retry the operation, you can
view the commands sent to the subprocess and the output
generated when these commands are executed.
RETAIN, 'object' 'object-name' was not replaced because 'object'
from kit does not have higher generation number
Explanation: During installation of a software product (or a patch to
a software product), the specified object (either a file
or a library module) was not copied from the kit to the
destination disk. The installation utility found an object
with the same name already installed on the destination disk
and that object's generation (sequencing) number was the same
or greater than the generation number of the object from the
kit. Therefore, the object with the latest generation number
(the previously installed item) was left on your destination
disk.
This condition typically occurs when you install multiple
patches or updates to the same product. The installation
utility performs conflict detection and resolution so that
your system will always retain the most current files even if
updates are not installed in chronological order.
User Action: None.
|
| Contents |
|
|||||||||||