Your attention is drawn to the terms and conditions of the Software Licence regarding the use of NAG software. Any request to use this software other than on the licensed computer must be referred to NAG, as should requests for information about the availability of other implementations.
This implementation is a compiled, tested, ready-to-use version of the NAG Fortran Library that is considered suitable for operation on the computer systems detailed below:
hardware: IBM RS/6000 Power systems operating system: AIX v4.3 or compatible Fortran compiler: XL Fortran f77/f90/f95 v7.1 or compatible
This implementation was produced at NAG Ltd., Oxford on the computing system detailed below:
hardware: IBM RS/6000 Power3 system 44P Model 270 operating system: AIX v4.3 Fortran compiler: XLF 7.1.0.0 compiler options: -O3 -q64 -qstrict
The entire NAG Fortran Library, Mark 20, was compiled with full optimization
(
x05abz
This library has been tested using the Basic Linear Algebra Subprograms (BLAS) and linear algebra routines (LAPACK) provided by NAG (see the Chapter Introductions for F06, F07 and F08 in the NAG Fortran Library Manual). It has also been tested with the BLAS subset provided in the vendor's Engineering and Scientific Subroutine Library (ESSL) version 3.2.0.0.
Additionally, libnag.a has been tested using xlf90.
|-- in.html
|-- un.html
|-- doc --|-- nag_fl_un.3
| |-- blas_lapack_to_nag
| |-- nag_to_blas_lapack
flib320da --|
|-- libnag.a
|-- libnag_sh.a
|-- libnag_use_essl.a
|
|-- interface_blocks --|-- *.mod
|
| |-- source ---|-- ??????e.f
|-- examples --|-- data -----|-- ??????e.d
| |-- results --|-- ??????e.r
|
|-- scripts ---|-- *
Both libnag.a (a static object archive) and libnag_sh.a (a shared object archive) were compiled to include the NAG version of the BLAS procedures, whilst the static library libnag_use_essl.a does not contain BLAS entries and MUST be used with the IBM library ESSL (Engineering and Scientific Subroutine Library). Should a shared version of libnag_use_essl be required, this may be produced using the script make_shlib, followed by the script rmobjs.
The examples results given in the directory results are those obtained using libnag.a. Using libnag_sh.a, or libnag_use_essl.a and ESSL, may produce slightly different results.
The following shows the directory/file organization of the PDF documentation materials as they will be installed.
NAGdoc -|- fl -|- html -|- mark20.html (main index)
| |
| |- frontmatter -|- *.html (sundry information)
| |
| |- genint -|- *.html (introductory material)
| |
| |- images -|- *.gif (nag images)
| | |
| | |- topbar -|- *.gif (Fortran Library images)
| |
| |- indexes -|- gams -|- gams.html (main GAMS index)
| | | |
| | | |- *.html (GAMS files)
| | |
| | |- kwic -|- kwic.html (main KWIC index)
| | |
| | |- *.html (KWIC files)
| |
| |- toc -|- [A02-X05].html (chapter indexes)
|
|- pdf -|- genint -|- *.pdf (introductory material)
| |
|- [A02-X05] -|- *.pdf (chapter and routine files)
compiled libraries, libnag.a: 21.6 Mb
libnag_sh.a: 17.9 Mb
libnag_use_essl.a: 21.6 Mb
interface blocks: 3.1 Mb
example program material: 13.6 Mb
scripts: 0.1 Mb
library documentation files: 0.1 Mb
PDF documentation files: 105 Mb
To install all material use the Unix tar utility, e.g.
tar xvf /cdrom/fl20.tar(assuming the CD-ROM has been mounted as /cdrom).
The appropriate object library (libnag*.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.
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 modified to reflect the local installation, and moved to a directory in the man search path, e.g.
cd doc mv nag_fl_un.3 /usr/local/man/man3The NAG Fortran Library Interface Blocks define the type and arguments of each user callable NAG Fortran Library routine. These are not essential to calling the NAG Fortran Library from Fortran 90/95 programs. Their purpose is to allow the Fortran 90/95 compiler to check that NAG Fortran Library routines are called correctly.
The interface block files (interface_blocks/*.mod) 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/fl77_modules mv interface_blocks/* /usr/local/lib/fl77_modules
The
Alternatively, the files may be moved to the same directory as the pre-defined modules supplied with the compiler
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:
documentation files:
The NAGdoc directory contains the online documentation. This should be made available to users, in addition to the following:
doc/blas_lapack_to_nag doc/nag_to_blas_lapackthe appropriate compiled library - one of:
libnag.a libnag_sh.a libnag_use_essl.ainterface block files:
interface_blocks/*.modexample program material:
examples/source/??????e.f examples/data/??????e.d examples/results/??????e.r scripts/nagexample
Note that the example material has been adapted, if necessary, from that published in the NAG Fortran Library Manual, so that programs are suitable for execution with this implementation with no further changes (but see Section 4.4.2 for comments about possible differences in results obtained). Making the example material directly available to users provides them with easily adaptable templates for their own problems.
The "example programs" for the routines in the F06 chapter are not typical example programs and they are not in the Library Manual. They are test programs, which are supplied to sites for use in an installation test of the Library. Some of them take much longer to run than other example programs. Routines which are equivalent to BLAS, are tested twice: once when called by their NAG F06 names, and once when called by their BLAS names.
On-line documentation is bundled 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 (FLIB320DA).
The NAG websites are an information service providing items of interest to users and prospective users of NAG products and services. The information is reviewed and updated regularly and includes implementation availability, descriptions of products, downloadable software, product documentation and technical reports. The NAG websites can be accessed at
or
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: 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 Japan email: help@nag-j.co.jp Tel: +81 (0)3 5542 6311 Fax: +81 (0)3 5542 6312