# 3 After Installing Digital Fortran

This chapter discusses the following post-installation tasks and considerations:

- How to run the Installation Verification Procedure separately (Section 3.1)

- How to make the product usable on a VMScluster (Section 3.2)

- How to make the newly installed FORTRAN compiler available to users who are currently logged in (Section 3.3)

- Which older files may now be obsolete (Section 3.4)

- How to set user account quotas (Section 3.5)

- How to enhance performance by tuning your system and installing Digital Fortran as a shared image (Section 3.6)

- Issues concerning OpenVMS upgrades (Section 3.7)

- How to read the release notes after installation (Section 3.8)

- How to remove Digital Fortran from your system (Section 3.9)

- Troubleshooting tips (Section 3.10)

- How to get help and report problems (Section 3.11)

# 3.1 Running the Installation Verification Procedure Separately

The Digital Fortran Installation Verification Procedure (IVP) runs automatically during Digital Fortran installation.

If system problems occur, you should run the IVP separately to ensure the integrity of the installed files. To run the IVP, enter the following command:

    $ @SYS$TEST:FORTRAN$IVP.COM

If any problems are encountered, a message such as the following appears:

    Digital Fortran Installation Verification Procedure Failed

# 3.2 VMScluster Considerations

If you want to run Digital Fortran on multiple nodes of a VMScluster, first check to see that you have the appropriate software license (see Section 1.5). Then perform the following steps after you install Digital Fortran:

1. Issue the LICENSE LOAD command, as described in the OpenVMS License Management Utility Manual, to activate the license on each node in the VMScluster on which Digital Fortran is to be executed.

2. The commands in this step should be executed on all cluster nodes, whether or not they are licensed to use Digital Fortran; failure to do so may cause unexpected errors for users.

   Note
     If you are using a dual- architecture (VAX and Alpha systems) heterogeneous cluster, before executing these commands, make sure the appropriate logical names have been set to define the scope of the SYSMAN DO commands. For more information, see the OpenVMS System Manager's Manual.

   While logged in as SYSTEM, or as another username that has the CMKRNL and SYSPRV privileges enabled, use the OpenVMS SYSMAN utility to set your environment, as follows:

       $ RUN SYS$SYSTEM:SYSMAN
       SYSMAN> SET ENVIRONMENT/CLUSTER
       %SYSMAN-I-ENV, current command environment:
               Clusterwide on local cluster
               Username SYSTEM       will be used on nonlocal nodes

3. Update the active DCL command tables (DCLTABLES.EXE) and Run-Time Library (DEC$FORRTL.EXE), as follows:

       SYSMAN> DO @SYS$UPDATE:FORTRAN$POST_INSTALL.COM
       %SYSMAN-I-OUTPUT, command execution on node NODE1
       %SYSMAN-I-OUTPUT, command execution on node NODE2

   Warning
     If you do not execute the SYS$UPDATE:FORTRAN$POST_INSTALL procedure on all nodes of the cluster immediately after installation, run-time errors can occur (such as SHRIDMISMAT: "ident mismatch with shareable image").

4. Then EXIT from SYSMAN, as follows:

       SYSMAN> EXIT
       $

   The SYSMAN utility will cause the post-installation procedure to be executed on each node of the local cluster.

# 3.3 Making the FORTRAN Command Available After Installation

The installation procedure modifies the DCL command table so that the FORTRAN command is recognized and processed.

After the new Digital Fortran compiler is installed, this command table is available to all users who log in after installation. 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 FORTRAN command and the new command table must log out and log in again, or use the DCL command:

    $ SET COMMAND /TABLES=SYS$LIBRARY:DCLTABLES

# 3.4 Removing Obsolete Files

If you have installed previous versions of VAX FORTRAN or VAX FORTRAN-HPO, there may be some obsolete files remaining on your system that are no longer used by the current version of Digital Fortran.

Table 3-1 lists these obsolete files:

### Table 3-1 Obsolete Files

File Specification | Description
--- | ---
SYS$SYSTEM:FORTRAN.EXE | VAX FORTRAN Version 5.n compiler
SYS$SYSTEM:FORTRAN- HPO.EXE | VAX FORTRAN-HPO compiler
SYS$HELP:FORTRAN$DWCI.HLB | DECwindows Compiler Interface
SYS$LIBRARY:FORTV5CLD.CLD | VAX FORTRAN Version 5 command definition
SYS$MESSAGE:FORTERR1.EXE | VAX FORTRAN Version 5 message file
SYS$MESSAGE:FORTERR2.EXE | VAX FORTRAN Version 5 message file
VUE$LIBRARY:FORTRAN$DWCI.EXE | DECwindows Compiler Interface
VUE$LIBRARY:FORTRAN$DWCI.UID | DECwindows Compiler Interface

You can delete these files if you are certain that they are no longer needed and you do not need a previous version of the compiler to coexist with the new compiler.

# 3.5 User Account Requirements

No special privileges are needed to use Digital Fortran. There is no benefit from installing the compiler with privileges.

To use Digital Fortran, a user account does not need to meet any special quota requirements. However, for parallel-processing applications or very large programs (many program units compiled together), consider adjusting the working set (WSDEF, WSQUOTA, WSEXTENT) and page file (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.

# 3.6 Enhancing Digital Fortran Performance

This section contains information on system tuning and explains how to install Digital Fortran as a shared image.

## 3.6.1 Tuning Your System

After installing Digital Fortran, you can adjust your system to enhance performance and lower the use of some system resources.

If users will be compiling parallel-processing applications or very large programs (many program units compiled together), consider the following:

- Adequate page file space must exist. Large programs (such as those using parallel processing) need more virtual memory during compilation and execution than small programs. Use the INSTALL command to extend an existing page file or create one or more new page files.

- The SYSGEN parameter virtual page count is related to the total amount of page file space. If you create more page file space, be sure to review the virtual page count parameter and increase it if necessary.

- The SYSGEN parameter working set maximum (WSMAX) can also be checked if a larger process working set is needed.

For more information about tuning your system, see the DEC Fortran Performance Guide for OpenVMS VAX Systems and the Guide to OpenVMS Performance Management.

## 3.6.2 Installing the Digital Fortran Compiler as a Shared Image

If you expect the Digital Fortran compiler to be used extensively on your system, you can reduce the system overhead and memory requirements by installing it as a shared image. This is done by using the OpenVMS Install Utility (INSTALL).

To install the compiler as a shared image on a system that is currently running, use a system that has been rebooted recently, because the available space in the global page table is less likely to be fragmented.

Before installing the compiler as a shared image, you must first determine the number of available global pagelets and global sections on your system. See Section 1.6.1.1 for information on how to verify and modify the number of global pagelets and global sections. Section 1.6.1 contains the guidelines for setting these parameters.

Once you reset the system parameter values, invoke the Install Utility from a privileged account and then install Digital Fortran as a shared image, as follows:

    $ INSTALL
    INSTALL> ADD SYS$SYSTEM:FORTRAN$MAIN.EXE/OPEN/SHARED/HEADER_RESIDENT
    INSTALL> EXIT

Add the following lines to the appropriate system startup command file so that the Digital Fortran compiler is available as a shared image each time the system is started:

    $ INSTALL
    ADD SYS$SYSTEM:FORTRAN$MAIN.EXE/OPEN/SHARED/HEADER_RESIDENT
    EXIT

If your site has modularized its startup procedures, be sure you add the lines to the correct file. The default startup command file for OpenVMS is SYS$MANAGER:SYSTARTUP_V5.COM.

When you install Digital Fortran as a shared image, you may need to increase the global pagelets and global sections parameters (see Section 1.6.1).

# 3.7 OpenVMS Upgrade Issues

You should always use the most recent version of the Digital Fortran Run-Time Library available.

When you are preparing for an upgrade of the OpenVMS operating system, be aware that the Digital Fortran Run-Time Library ships with the OpenVMS operating system. This means that an OpenVMS upgrade may install an older version of the Digital Fortran Run- Time Library.

The Run-Time Library provided with the most recent version of Digital Fortran contains changes that are not included in the version provided with OpenVMS VAX Version 5.4 and earlier; these changes will be included in a future version of OpenVMS VAX.

If you install a new version of OpenVMS (earlier than Version 7.0), it may overwrite the existing Digital Fortran Run-Time Library, replacing it with an earlier version. So, after every OpenVMS installation, reinstall Digital Fortran to keep the Run-Time Library current.

# 3.8 Reading the Release Notes After Installation

During installation, the text form of the release notes is copied to the following file in the SYS$HELP directory:

    SYS$HELP:FORT06n.RELEASE_NOTES

The n is replaced by the minor version of Digital Fortran, such as 4 (for Version 6.4).

After installation, you can enter the following command to review the release notes:

    $ TYPE/PAGE SYS$HELP:FORT06n.RELEASE_NOTES

The Digital Fortran kit also provides the release notes in PostScript and DECwindows Bookreader forms. These forms of the release notes can be accessed after the installation has completed by using the following file names:

    SYS$HELP:FORT06n_RELEASE_NOTES.PS
    SYS$HELP:FORT06n_RELEASE_NOTES.DECW$BOOK

Note
  Note that the name of the newly installed release notes file consists of the current product name and version number. Do not delete release notes for previous versions of Digital Fortran (if any).

# 3.9 Removing Digital Fortran

From a process that has SYSPRV and CMKRNL or SETPRV privileges, use one of the following methods to remove Digital Fortran from the system:

- If POLYCENTER (PCSI) was used to install Digital Fortran

  You can use PCSI to remove Digital Fortran by entering the following command:

      $ PRODUCT REMOVE FORTRAN

- If VMSINSTAL was used to install Digital Fortran

  You can use a SYS$UPDATE command procedure to remove Digital Fortran, by entering the following command:

      $ @SYS$UPDATE:FORTRAN$DEINSTALL

  This procedure removes all compiler-related files, modules, images and DCL commands from the system.

  The procedure also provides an option to remove the Digital Fortran-provided Run-Time Library images and replace them with those provided by OpenVMS. Digital does not recommend selecting this option, because any images linked against the newer Run-Time Library images may fail. Do not select this option unless you are willing to relink any applications that have been linked since Digital Fortran was installed.

If your system is a member of a VMScluster, you must then execute the following command on all other cluster members:

    $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES

The OpenVMS utility SYSMAN can be used for this purpose; see Section 3.2 for an example of using SYSMAN.

# 3.10 Troubleshooting Tips

If your installation is not successful, check for the following possible problems:

- The appropriate PAK must be available to the user performing the installation. The PAK must be registered and loaded before you can install Digital Fortran; for information about registering a PAK, see Section 1.5. Then reinstall Digital Fortran.

- The DCLTABLES.EXE file should be in the SYS$COMMON:[SYSLIB] directory. There should not be a copy of DCLTABLES.EXE in SYS$SPECIFIC:[SYSLIB].

  If a copy of DCLTABLES.EXE is found in a SYS$SPECIFIC root, rename it to DCLTABLES.OLD, do an INSTALL REPLACE SYS$LIBRARY:DCLTABLES, then reinstall Digital Fortran.

- The system logical name SYS$SYSROOT should not be modified from the preset definition provided by the OpenVMS VAX operating system.

# 3.11 Getting Help and Reporting Problems

If you encounter a problem while using Digital Fortran, report it to Digital.

If an error occurs while Digital Fortran is in use and you believe the error is caused by a problem with Digital Fortran, take one of the following actions:

- If you have a Software Product Services Support Agreement, consider contacting your Customer Support Center (CSC) by telephone (in the United States, 1-800-354-9000) or by using the electronic means provided with your support agreement. You can use DSNlink or other electronic means to report the problem to the CSC.

- If you do not have a service contract, you can arrange for per-call CSC support.

When you initially contact the CSC, please indicate the following:

- The name and version number of the operating system (OpenVMS VAX) you are using

- The name (Digital Fortran) and version number of Digital Fortran you are using

- The hardware system you are using (such as a model number)

- How critical the problem is

- A very brief description of the problem (one sentence if possible)

When you submit information electronically or are speaking on the phone to the appropriate support specialist, you can provide more detailed information, such as:

- The specific commands used to compile and link the program

- The error messages displayed

- Relevant detailed information (possibly including source program listings)

Please try to narrow the cause of the problem to a specific source module or lines of code.

CSC personnel may ask for additional information, such as:

- Listings of any command files

- INCLUDE files

- Relevant data files

If the program is longer than 50 lines, submit a copy of it electronically or provide machine-readable media (floppy diskette or magnetic tape).

Experience shows that problem reports sometimes do not contain enough information to duplicate or identify the problem. Concise, complete information helps Digital give accurate and timely service to software problems.

To obtain information about purchasing Digital support services, please contact your local Digital sales representative.

You can also send comments and questions about Digital Fortran to the following Internet mail address: `fortran@digital.com` .

Click to return to contents

Copyright © 1996, Digital Equipment Corporation -- All rights reserved.