NAG fl90, Release 4

FNL6404DCL - License Managed

Intel Itanium 64-bit Linux, Intel Fortran

Installer's Note



Contents


1. Introduction

This document is essential reading for whoever is responsible for the installation of the NAG fl90 implementation specified in the title. The installer will be supplied with a printed copy of this document. Both this (in.html) and the Users' Note (un.html) are supplied in the doc directory on the distribution medium.

Whenever the NAG fl90 has been supplied in compiled form, that form is considered to be the standard library file. The use of all supplied software must be in accordance with the terms and conditions of the Software Licence signed by NAG and each site. Any request to use NAG software on a computer other than the one licensed must be referred to NAG (see Section 6).

2. Implementation Provided

2.1. Applicability

This implementation is a compiled, tested, ready-to-use version of NAG fl90 that is considered suitable for operation on the computer systems detailed below:

hardware:         Itanium-based systems 
operating system: Linux 2.4.3-12smp (RedHat 7.1) or compatible
Fortran compiler: Intel Fortran Compiler for Itanium-based applications,
                  Version 8.0 Build 20040212 or compatible

For information about implementations of NAG fl90 for use on other computer systems please contact NAG.

2.2. Derivation

This implementation was produced at NAG Ltd., Oxford on the computing system detailed below:

hardware:       : SGI 750 Itanium workstation (2 processor, 733 MHz, 950 Mb)
operating system: Linux 2.4.3-12smp (RedHat 7.1 (Seawolf))
Fortran compiler: Intel Fortran Compiler for Itanium-based applications,
                  Version 8.0 Build 20040212
                  Package ID: l_fc_pc_8.0.039_pl042
compiler options: -fpic

This implementation was tested using the above compiler on the following two systems:

    SGI 3700, Itanium 2 under SGI ProPack v2.3 for Linux
    HPZX 2000, Itanium 2 under RedHat Advanced Server release 2.1AS

The entire NAG fl90 library, Release 4, was compiled with optimization level (-O3), except for the following underlying procedures, which had to be compiled with less optimization:

e02aez_9d (-O0)   e02daz_7d (-O2)   e04mfm_7d (-O2)   e04uhm_8d (-O2)
e04ums_8d (-O2)   f06qrf_7d (-O2)   f06qvf_7d (-O2)   f06qxf_7d (-O0)
g01hbf_9d (-O2)   m01daf_7d (-O0)

3. Distribution Medium

The software is ordinarily distributed in tar format on CD-ROM.

3.1. Contents

The following shows the directory/file organization of the library materials as they will be installed.
                      |-- in.html
            |-- doc --|-- un.html
            |         |-- nag_fn_un.3
            |
            |         |-- libnagfl90.a
            |         |-- libnagfl90_noblas.a
            |-- lib --|-- libnagfl90.so
            |         |-- libnagfl90_noblas.so
fnl6404dcl--|
            |-- nag_mod_dir --|-- *.mod
            |
            |              |-- source ---|-- *.f90
            |-- examples --|-- data -----|-- *.dat
            |              |-- results --|-- *.r
            |
            |-- scripts ---|-- nagexample*
            |
            |              |-- bin ------|-- * (directories of FLEXlm binaries
            |              |                    for supported platforms)
            |-- license ---|-- README.TXT
                           |
                           |-- htmlman --|-- flexuser --|-- * (End User Guide)
where
  libnagfl90.a         is a compiled static library including NAG BLAS/LAPACK
  libnagfl90_noblas.a  is a compiled static library without NAG BLAS/LAPACK
  libnagfl90.so        is a compiled shareable library including NAG BLAS/LAPACK
  libnagfl90_noblas.so is a compiled shareable library without NAG BLAS/LAPACK

libnagfl90_noblas.a and libnagfl90_noblas.so do not contain the NAG version of BLAS and LAPACK. They MUST be used with other libraries that provide BLAS and LAPACK procedures such as the Intel Math Kernel Library (MKL).

MKL 64 bit version 7.0 beta for Linux was used for testing this implementation. libnagfl90_noblas.a was tested using the libraries libguide.a, libmkl_lapack.a and libmkl_ipf.a, while libnagfl90_noblas.so was tested using libguide.so, libmkl_lapack64.so and libmkl_itp.so.

The examples results given in the directory results are those obtained using libnagfl90.a. Using any of the other libraries may produce slightly different results.

The following shows the directory/file organization of the PDF documentation materials as they will be installed.

         |-- images --|-- *.gif
         |
         |                   |-- release4.html  (main index)
         |                   |
         |                   |-- genint --|-- *.html  (introductory material)
NAGdoc --|        |-- html --|
         |        |          |-- library_contents --|-- *.html
         |        |          |
         |        |          |-- [c01-c29]_fn04.html  (chapter indexes)
         |-- fn --|
                  |         |-- genint --|-- *.pdf  (introductory material)
                  |         |
                  |         |-- library_contents --|-- *.pdf
                  |-- pdf --|
                            |-- indexes --|-- *.pdf  (KWIC and GAMS)
                            |
                            |-- [c01-c29] --|-- *.pdf  (chapter, module and
                                                        procedure files)

3.2. File Sizes

The files require approximately the following disk space:
compiled libraries:
  libnagfl90.a:              36.7 Mb
  libnagfl90_noblas.a:       31.9 Mb
  libnagfl90.so:             28.5 Mb
  libnagfl90_noblas.so:      24.7 Mb
module information files:     6.5 Mb
example program material:     4.3 Mb
scripts:                        7 Kb
library documentation files:   34 Kb
PDF documentation files:     20.2 Mb
Licensing materials:         50.1 Mb

4. Installation

4.1. Library Installation

To install all library material use the Unix tar utility, e.g.

tar xvf /cdrom/fn04.tar
(assuming the CD-ROM has been mounted as /cdrom).

This implementation contains 4 object libraries. You could install any number of them as required for your system.

The installed libraries should be moved to a directory, such as /usr/lib, in the default search path of the linker, if possible, so that linkage is convenient. Alternatively, symbolic links could be made to them, e.g.

ln -s /fnl6404dcl/lib/libnagfl90.a          /usr/lib/libnagfl90.a
ln -s /fnl6404dcl/lib/libnagfl90_noblas.a   /usr/lib/libnagfl90_noblas.a
ln -s /fnl6404dcl/lib/libnagfl90.so         /usr/lib/libnagfl90.so
ln -s /fnl6404dcl/lib/libnagfl90_noblas.so  /usr/lib/libnagfl90_noblas.so

The module information files (nag_mod_dir/*) are supplied in pre-compiled module form. They should be moved to a suitable location so that access is convenient, e.g.

mkdir /usr/local/lib/fl90_modules
mv nag_mod_dir/* /usr/local/lib/fl90_modules
or, a symbolic link can be made, e.g.
ln -s /fnl6404dcl/nag_mod_dir  /usr/local/lib/fl90_modules

The -I"pathname" option should then be specified on each compiler invocation (where "pathname" is /usr/local/lib/fl90_modules) to tell the compiler where to find the modules.

Alternatively, you could include the -I"pathname" option in the compiler configuration file ifort.cfg.

The script nagexample uses the static library libnagfl90.a. It refers to the local directory containing the example programs. If libnagfl90.a is installed, the script file should be copied to (for example) /usr/local/bin, modified to reflect the local installation, and its protection set to world execute.

The script nagexample_dynamic uses the shareable library libnagfl90.so. It refers to the local directory containing the example programs. If libnagfl90.so is installed, the script file should be copied to (for example) /usr/local/bin, modified to reflect the local installation, and its protection set to world execute.

The script nagexample_noblas uses the static library libnagfl90_noblas.a and the MKL libraries. It refers to the local directories containing the NAG example programs and the MKL libraries (version 7.0 beta). If libnagfl90_noblas.a is installed, the script file should be copied to (for example) /usr/local/bin, modified to reflect the local installation for both the NAG library and MKL, and its protection set to world execute. (Check the MKL User Notes on how to link with MKL).

The script nagexample_noblas_dynamic uses the shareable library libnagfl90_noblas.so and the MKL shareable libraries. It refers to the local directories containing the NAG example programs and the MKL libraries (version 7.0 beta). If libnagfl90_noblas.so is installed, the script file should be copied to (for example) /usr/local/bin, modified to reflect the local installation for both the NAG library and MKL, and its protection set to world execute. (Check the MKL User Notes on how to link with MKL).

The man page, which directs users to the HTML form of the Users' Note, should be moved to a directory in the man search path, e.g.

cd doc
mv nag_fn_un.3 /usr/man/man3

4.1.1. License Management

The use of the NAG fl90 Library is controlled by the FLEXlm network license management system (FLEXlm is a registered trademark of Macrovision Corporation). This release of the NAG fl90 Library uses version 9.2 of FLEXlm.

In order to enable the software, NAG will issue you with a license key. The license key is a simple text file containing details of the software that will be enabled.

To request a license key, locate and run the program key_rqst in the appropriate platform specific subdirectory under the license/bin/ subdirectory of the software distribution. This is utility does not have a GUI and must be run from a command prompt. Complete the form that it displays and e-mail (or FAX) it to NAG.

A short term (demonstration or trial) license key contains one or more lines like the following:

FEATURE NAG_FN NAG 4.000 30-mar-2004 0 CBDA2041DC1BC45D2B68 "ANY" DEMO
Specifically, it does not have any lines starting with the word SERVER and is referred to here as an uncounted license key. Longer term uncounted license keys must be locked to a specific computer, i.e. they will enable the software on one computer only. These license keys include the FLEXlm hostid of the computer instead of the word DEMO above.

Once you have obtained the license key, store the text of it in a file, say /opt/nag/license.lic.

If the license file contains one or more SERVER lines, the FLEXlm daemons must be started before you can use the license. Refer to the FLEXlm End Users Guide supplied in the license/htmlman/flexuser/ subdirectory (start at the file TOC.htm).

For an uncounted license, the location of the license file must be made known to the NAG application by setting the environment variable LM_LICENSE_FILE to the full pathname of the file before the application is invoked.

For example, in the C-shell, type:

   setenv LM_LICENSE_FILE /opt/nag/license.lic
or in the Bourne shell, type:
   LM_LICENSE_FILE=/opt/nag/license.lic
   export LM_LICENSE_FILE
No other actions are required to install an uncounted license.

Further details about FLEXlm and how it may be configured to suit your local circumstances are included in the FLEXlm End Users Guide.

4.2. PDF Documentation Installation

To install all PDF documentation material, use the Unix tar utility, e.g.
tar xvf /cdrom/pdf.tar
(assuming the CD-ROM has been mounted as /cdrom).

You may wish to move the PDF documentation files to the same location as that for other NAG products. You are encouraged to make them readily available to users, but in such a way that they are not generally accessible from outside your site.

4.3. Checking Accessibility

The installer should ensure that the advice given to users in Section 3.1 of the Users' Note (un.html) is suitable for the installation. This can be done by running a few example programs following that advice. The installation can also be tested using the nagexample* scripts.

4.4. Release to Users

The Users' Note (un.html) should be checked and amended as necessary (particularly Section 3.1). It can then be made available to users directly, or be absorbed into local access information.

The following material should also be made accessible to users:

compiled libraries:

libnagfl90.a
libnagfl90_noblas.a
libnagfl90.so
libnagfl90_noblas.so
module information files:
nag_mod_dir/*.mod
example program material:
examples/source/*.f90
examples/data/*.dat
examples/results/*.r
scripts/nagexample*
pdf documentation files

Note that the example material has been adapted, if necessary, from that printed in the NAG fl90 Manual, so that programs are suitable for execution with this implementation with no further changes. Making the example material directly available to users provides them with easily adaptable templates for their own problems.

4.5. Maintenance Level

The maintenance level of the library can be determined by writing a simple program to call procedure nag_lib_ident, which prints out details of the implementation, including title and product code, compiler and precision used, release and maintenance level.

5. Documentation

Each supported NAG fl90 site is currently provided with a printed copy of the NAG fl90 Manual (or Update). Additional copies are available for purchase; please refer to the NAG documentation order form (available on the NAG websites, see Section 6 (c)) for details of current prices.

Online documentation is provided, in PDF form, with this implementation. Please see the Readme file on the distribution medium for further information.

6. Support from NAG

(a) Contact with NAG

Queries concerning this document or the implementation generally should be directed initially to your local Advisory Service. If you have difficulty in making contact locally, you can contact NAG directly at one of the addresses given in the Appendix. Users subscribing to the support service are encouraged to contact one of the NAG Response Centres (see below).

(b) NAG Response Centres

The NAG Response Centres are available for general enquiries from all users and also for technical queries from sites with an annually licensed product or support service.

The Response Centres are open during office hours, but contact is possible by fax, email and phone (answering machine) at all times.

When contacting a Response Centre please quote your NAG site reference and NAG product code (in this case FNL6404DCL).

(c) NAG Websites

The NAG websites provide information about implementation availability, descriptions of products, downloadable software, product documentation and technical reports. The NAG websites can be accessed at

http://www.nag.co.uk/, http://www.nag.com/ (in North America) or http://www.nag-j.co.jp/ (in Japan)

(d) NAG Electronic Newsletter

If you would like to be kept up to date with news from NAG then please register to receive our free electronic newsletter, which will alert you to special offers, announcements about new products or product/service enhancements, customer stories and NAG's event diary. You can register via one of our websites, or by contacting us at nagnews@nag.co.uk.

7. User Feedback

Many factors influence the way NAG's products and services evolve and your ideas are invaluable in helping us to ensure that we meet your needs. If you would like to contribute to this process we would be delighted to receive your comments. Please contact your local NAG Response Centre (shown below).

Appendix - Contact Addresses

NAG Ltd
Wilkinson House
Jordan Hill Road
OXFORD  OX2 8DR                         NAG Ltd Response Centre
United Kingdom                          email: support@nag.co.uk
 
Tel: +44 (0)1865 511245                 Tel: +44 (0)1865 311744
Fax: +44 (0)1865 310139                 Fax: +44 (0)1865 310139
 
NAG Inc
1431 Opus Place, Suite 220
Downers Grove
IL 60515-1362                           NAG Inc Response Center
USA                                     email: infodesk@nag.com
 
Tel: +1 630 971 2337                    Tel: +1 630 971 2345
Fax: +1 630 971 2706                    Fax: +1 630 971 2706
 
Nihon NAG KK
Hatchobori Frontier Building 2F
4-9-9
Hatchobori
Chuo-ku
Tokyo
104-0032
Japan
email: help@nag-j.co.jp

Tel: +81 (0)3 5542 6311
Fax: +81 (0)3 5542 6312

Trademarks

All other trademarks are acknowledged.