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).
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: Intel Pentium or compatible PCs operating system: Linux 2.2.17-14 (Red Hat 6.2 "Zoot") or compatible Linux 2.4.2-2 (Red Hat 7.1 "Seawolf") or compatible Linux 2.4.20-8 (Red Hat 9 "Shrike") or compatible Fortran compiler: NAGWare F95 Release 4.2(464) or compatible NAGWare F95 Release 5.0(253) or compatible
For information about implementations of NAG fl90 for use on other computer systems please contact NAG.
This implementation was produced at NAG Ltd., Oxford on the computing system detailed below:
hardware: DELL OptiPlex GX1 with Intel Pentium III operating system: Linux 2.4.2-2 (Red Hat 7.1 "Seawolf") Fortran compiler: NAGWare Fortran 95 compiler Release 4.2(553) C compiler: gcc version 2.96 20000731
The entire NAG fl90 library, Release 4, was compiled with maximal optimization (-O4).
The implementation was also tested on the following systems:
NAGWare F95 compiler Release 4.2(464) and Release 4.2(553) under Linux 2.2.17-14 (Red Hat 6.2 "Zoot") using gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) NAGWare F95 compiler Release 5.0(253) and Release 5.0(288) under Linux 2.4.2-2 (Red Hat 7.1 "Seawolf") using gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81) NAGWare F95 compiler Release 5.0(253) and Release 5.0(288) under Linux 2.4.20-8 (Red Hat 9 "Shrike") using gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) NAGWare F95 compiler Release 4.2(464) and Release 4.2(542) under Linux 2.4.20-8 (Red Hat 9 "Shrike") using gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
|-- in.html |-- doc --|-- un.html | |-- nag_fn_un.3 | |-- lib --|-- libnagfl90.a | |-- libnagfl90_rh9.a | |-- nag_mod_dir --|-- *.mod fnlux04d9l--| | |-- 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)
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)
compiled libraries: libnagfl90.a 11.0 Mb (for Red Hat 6 and 7) libnagfl90_rh9.a 11.0 Mb (for Red Hat 9) module information files: 2.2 Mb example program material: 4.3 Mb scripts: 2 Kb library documentation files: 27 Kb PDF documentation files: 20.2 Mb Licensing materials: 50.1 Mb
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).
According to the operating system on your machine, one of the object libraries (libnagfl90.a or libnagfl90_rh9.a) 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, a symbolic link can be made, e.g.
ln -s /fnlux04d9l/lib/libnagfl90.a /usr/lib/libnagfl90.a or ln -s /fnlux04d9l/lib/libnagfl90_rh9.a /usr/lib/libnagfl90.a
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_modulesor, a symbolic link can be made, e.g.
ln -s /fnlux04d9l/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, the files may be moved to the same directory as the pre-defined modules supplied with the compiler.
The script nagexample refers to the local directory containing the example programs. The file should be copied to (for example) /usr/local/bin, modified to reflect the local installation, and its protection set to world execute.
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
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 utility does not have a GUI and must be run from a command prompt. Complete the form that it displays and email (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" DEMOSpecifically, 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.licor in the Bourne shell, type:
LM_LICENSE_FILE=/opt/nag/license.lic export LM_LICENSE_FILENo 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.
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. Further information is contained in the readme file on the distribution medium.
The following material should also be made accessible to users:
one of the compiled libraries:
libnagfl90.a or libnagfl90_rh9.a (renamed as libnagfl90.a)module information files:
nag_mod_dir/*.modexample program material:
examples/source/*.f90 examples/data/*.dat examples/results/*.r scripts/nagexamplepdf 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.
Online documentation is provided, in PDF form, with this implementation. Please see Section 4.2.
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 FNLUX04D9L).
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)
NAG Ltd Wilkinson House Jordan Hill Road OXFORD OX2 8DR NAG Ltd Response Centre United Kingdom email: firstname.lastname@example.org 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: email@example.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: firstname.lastname@example.org Tel: +81 (0)3 5542 6311 Fax: +81 (0)3 5542 6312