Previous | Contents |
This chapter describes:
Before you start the installation, read Chapter 1, which describes
the general options and requirements for installing Compaq Fortran.
After you complete installation, see Chapter 3.
2.1 Compaq Fortran Installation Instructions
The installation procedure loads Compaq Fortran product distribution files on to the system disk on the system where you perform the installation.
You must first install the Compaq Fortran Run-Time Library (RTL) before you install the Compaq Fortran compiler. |
Follow these steps to install Compaq Fortran from the OpenVMS Alpha Software Products Library CD-ROM set:
$ SET PROCESS/PRIVILEGE=(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] DEC-AXPVMS-FORRTL-Vnnnn-x-1.PCSI DEC-AXPVMS-FORTRAN-Vnnnn-x-1.PCSI Total of 2 files. |
$ PRODUCT EXTRACT RELEASE_NOTES FORTRAN /SOURCE=disk:[dir] - $_/FILE=FORTRAN.RELNOTES |
$ TYPE/PAGE FORTRAN.RELNOTES |
$ PRODUCT INSTALL FORRTL /SOURCE=disk:[dir] /HELP |
If the installation fails, repeat the PRODUCT INSTALL command(s) adding the qualifiers /LOG/TRACE to the command line. The additional output will help Compaq support analyze the problem. The following product has been selected: DEC AXPVMS FORRTL 7.n Layered Product Do you want to continue? [YES][Return] *** DEC AXPVMS FORRTL 7.n Layered Product Copyright © Digital Equipment Corporation 1992-1999 - All rights reserved This software is produced by Digital Equipment Corporation This software is licensed under the OpenVMS product license Do you want all the default values for this product? [YES] [Return] Do you want to view the values? [NO] [Return] %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS FORRTL 7.n %PCSI-I-VOLINFO, estimated space information for volume DISK$vvvvvvvv -PCSI-I-VOLSPC, nnnn required; nnnnnn available; nnnnnn net Portion Done: 0%...20%...70%...90%...100% The following product has been installed: DEC AXPVMS FORRTL 7.n Layered Product *** DEC AXPVMS FORRTL 7.n Layered Product Release notes are in SYS$HELP:FORRTL.RELEASE_NOTES Do INSTALL REPLACE SYS$LIBRARY:DEC$FORRTL.EXE on all other cluster nodes $ |
$ PRODUCT SHOW PRODUCT FORTRAN90 |
PRODUCT ------- DEC AXPVMS FORTRAN90 Vn.n 1 item found |
PRODUCT ------- 0 items found |
$ PRODUCT REMOVE FORTRAN90 |
The following product has been selected: DEC AXPVMS FORTRAN90 V2.0 %PCSI-E-CONREMUNR, optionally remove product DEC AXPVMS FORRTL V2.0 that is no longer required by another product Do you want to take this action? [NO][Return] Do you want to continue? [YES][Return] The following product will be removed: DEC AXPVMS FORTRAN90 V2.0 %PCSI-I-VOLINFO, estimated space information for volume DISK$vvvvvvvv -PCSI-I-VOLSPC, -nnnnn required; nnnnnnn available; nnnnnnn net Portion done: 0%...50%...60%...70%...80%...100% The following product has been removed: DEC AXPVMS FORTRAN90 V2.0 |
$ PRODUCT INSTALL FORTRAN /SOURCE=disk:[dir] /HELP |
The following product has been selected: DEC AXPVMS FORTRAN V7.n 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. DEC AXPVMS FORTRAN V7.n: Compaq Fortran for OpenVMS Alpha Systems Copyright © Digital Equipment Corporation 1992-1999 - All rights reserved This software product is sold by Compaq Computer Corporation PAKs used: FORTRAN, FORTRAN90, FORTRAN-USER or FORTRAN90-USER Do you want all the default values for this product? [YES] |
By default, the FORTRAN command invokes Fortran 95 Starting with version V7.2 of this product, the FORTRAN command verb, by default, invokes the Fortran 95 compiler. This is different from previous versions where FORTRAN invoked the Fortran 77 compiler. While we have made the Fortran 95 compiler highly compatible with the Fortran 77 compiler, there are some differences and some users may prefer to use the older compiler. With the default installation, the Fortran 77 compiler may be invoked using FORTRAN/OLD_F77. Command definition files are provided which allow system managers and individual users to select the previous arrangement where FORTRAN invokes Fortran 77 and F90 invokes Fortran 95. (The F90 verb invokes Fortran 95 in either case.) Please read, and ask your Fortran users to read, the release notes for more details on this change and how it may affect applications and build scripts. Do you want to continue? [YES] [Return] |
Do you want to review the options? [NO] [Return] |
Execution phase starting ... The following product will be installed: DEC AXPVMS FORTRAN V7.n DISK$VOLUMExxx:[VMS$COMMON] The following product has been removed: DEC AXPVMS FORTRAN V7.n DISK$VOLUMExxx:[VMS$COMMON] %PCSI-I-IVPEXECUTE, executing test procedure for DEC AXPVMS FORTRAN V7.n.. %PCSI-I-IVPSUCCESS, test procedure completed successfully DEC AXPVMS FORTRAN V7.n: Compaq Fortran for OpenVMS Alpha Systems Execute SYS$STARTUP:FORT$STARTUP.COM on all other VMScluster nodes Type HELP FORTRAN Release_notes for release notes location Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @SYS$STARTUP:FORT$STARTUP $ |
$ PRODUCT SHOW OBJECT /PRODUCT=(FORTRAN, FORRTL) |
To use other features of the PCSI utility, see the POLYCENTER Software Installation Utility User's Guide.
2.2 Installing 64-Bit Tools Support
If you will be using 64-bit address space data in your applications, you should install the enhanced 64-bit OpenVMS tools on your system, which include the OpenVMS Debugger (DEBUG64) and OpenVMS Linker (LINKER64).
If your system has OpenVMS Version 7.2 installed, and you want to use the ability to allocate static data (local variables and COMMON) in 64-bit address space, you must install the DEBUG64 (ADX072) kit as it provides a new linker, LINKER64, which supports this new feature.
OpenVMS Version 7.2 supports 64-bit allocation of static data, but does not provide LINKER64. OpenVMS versions prior to Version 7.2 do not support 64-bit allocation of static data.
If you have a version of OpenVMS later than Version 7.2, please check its release notes to see if DEBUG64 and LINKER64 functionality is already included. If the DEBUG64 kit is installed, LINKER64 is made the system default linker. It can be used as a general replacement for the OpenVMS-supplied linker.
DEBUG64 may be installed on OpenVMS Versions 6.2 and later. (Note that Compaq Fortran supports OpenVMS Version 7.1 and later.) The DEBUG64 kit is provided on your media CD-ROM in the same directory where the Fortran compiler kit files are located.
For more details on the capabilities of DEBUG64, see the release notes file ADX072.RELEASE_NOTES. You can view the release notes before installation (see below). After installation, the release notes are installed on the system in SYS$HELP:ADX072.RELEASE_NOTES.
Follow these steps to install DEBUG64:
$ SET PROCESS/PRIVILEGE=(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 ADX*.* Directory DKA400:[dir.subdir] ADX072.A ADX072.B ADX072.C Total of 3 files. |
$ @SYS$UPDATE:VMSINSTAL ADX072 disk:[dir] OPTIONS N |
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]: [Return] |
$ @sys$update:vmsinstal adx072 disk:[dir] |
OpenVMS AXP Software Product Installation Procedure V7.2 It is 19-APR-1999 at 15:43. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? [Return] |
The following products will be processed: ADX V7.2 Beginning installation of ADX V7.2 at 15:43 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ************************************************************** OpenVMS Alpha Debug V7.2X COPYRIGHT (C) 1978, 1999 BY DIGITAL EQUIPMENT CORPORATION, MAYNARD MASSACHUSETTS. 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 FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED. THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY COMPAQ COMPUTER CORPORATION. COMPAQ ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY COMPAQ. ********************************************************************* This kit installs Debug version V7.2X. It will install on Alpha OpenVMS V6.2 to V7.2 systems. This kit requires an installed DCE for its client/server configurations (see release motes). If DCE is not installed, the "server" portion of the debugger cannot be linked and a warning is printed during the installation, for example, "%ADX-W-LINKABORT, NO DEBUGSRVSHR linked, SYS$LIBRARY:DCE$LIB_SHR missing (install DCE)". You can safely ignore this message. The normal operation of the debugger is not affected, however, the client/server mode will NOT be operational. A new Heap Analyzer will be also installed on V7.1 or later systems. If your system is later upgraded from V6 to V7 or if DCE or MOTIF are later installed, then this kit MUST be rerun, i.e. the V7.2X debugger MUST be reinstalled. System Code Debugger features will NOT be installed as part of this kit, use the system supplied debugger for that. This installation will NOT replace your current OpenVMS system supplied debugger. However, it will replace any previous versions of the V7.2X debugger that may be installed AND it will remove any earlier network kit debuggers, e.g. V71C. This installation takes ~5 minutes. * Do you want to run the IVP after the installation [YES]? [Return] Do you want to run the interactive DECwindows Motif IVP? [NO]? [Return] Do you want to purge files replaced by this installation [YES]? [Return] %ADX-I-DONEASK, No further questions will be asked during this installation. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %ADX-I-ENDRESTORE, All Debugger savesets have been restored. %ADX-I-LINKING, Linking V7 images. %ADX-I-LINKDONE, DEBUGSHR has been linked. %ADX-I-LINKDONE, DEBUG has been linked. %ADX-I-LINKDONE, DEBUGUISHR has been linked. %ADX-I-LINKDONE, DEBUGSRVSHR has been linked. %ADX-I-LINKDONE, HA_MAIN has been linked. %ADX-I-LINKDONE, HA_KERNEL has been linked. %ADX-I-LINKDONE, TRACE has been linked. %ADX-I-CLEANUP, Cleanup has been performed. %ADX-I-PROHELP, Providing Debugger Help files... %ADX-I-PROMSG, Providing Debugger message image... %ADX-I-PROMSG, Providing Debugger .CLD file... %ADX-I-PROEXE, Providing Debugger files... %ADX-I-PROEXE, Providing Heap Analyzer files... %ADX-I-PROMSG, Providing startup files ... If you want the debugger installed by this kit to be the default system debugger: - Add the following line to the system startup procedure: $ @SYS$STARTUP:DEBUG$STARTUP_V72X.COM V72X You should remove any other *DEBUG$STARTUP*.COM reference. - Enter the following command from a privileged account: @SYS$STARTUP:DEBUG$STARTUP_V72X.COM V72X To install the images and define the default system debugger on other Alpha nodes of a VMScluster, enter this command on each such node. Note, however, that this is a /SYSTEM setup (also see SYS$STARTUP:DEBUGSETUP.COM) and also modifies and install/replaces your SYS$SHARE:DCLTABLES.EXE. If you want the regular system debugger installed to be the default system debugger, then do the same as above but use "VMS" as the input parameter, for example: @SYS$STARTUP:DEBUG$STARTUP_V72X.COM VMS Users can also dynamically switch debuggers by using SYS$STARTUP:DEBUGSETUP.COM. It's input options are VMS, V72X, V72, V71C, or UNSET. It also needs the logical table switch /JOB or /SYSTEM. For example: @SYS$STARTUP:DEBUGSETUP.COM V72X /JOB %ADX-I-PROIVP, Providing test files for IVP... The Debugger IVP has been moved to the SYS$TEST directory. To run the IVP after installation, first setup to use the V72X debugger by executing the command "@SYS$STARTUP:DEBUGSETUP V72X /JOB" Then, run the character cell IVP by executing the command "@SYS$TEST:DBG$IVP.COM" or, if DECWindows Motif has been installed on your system, run the interactive DECWindows Motif IVP by executing the command "@SYS$TEST:DBG$DW$IVP.COM" %ADX-I-INSTALLDONE, OpenVMS Alpha Debug V7.2X installation done %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Beginning the Debug V7.2X Verification Procedure COPYRIGHT (c) 1988, 1998 BY DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS. ALL RIGHTS RESERVED. Debug verification procedure successful. Installation of ADX V7.2 completed at 15:49 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]ADX072.VMI_DATA VMSINSTAL procedure done at 15:49 |
Previous | Next | Contents |