Your attention is drawn to the terms and conditions of the Software License 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 SMP Library that is considered suitable for operation on the computer systems detailed below:
hardware: IA64 (Itanium2) systems
operating system: Linux RHEL3 Kernel 2.4.21-9.EL (glibc-2.3.2.95.6) and compatible
including Linux RHEL4 Kernel 2.6.9-5.EL (glibc-2.3.4-2)
Fortran compiler: Intel(R) Fortran Itanium(R) Compiler for Itanium(R)-based applications
version 8.1 and compatible including versions 9.0 and 9.1
Vendor library: Intel MKL version 8.0 and compatible
This implementation was produced at NAG Ltd., Oxford on the computing system detailed below:
hardware: Intel Itanium2 operating system: Red Hat Enterprise Linux AS release 3 (Taroon Update 1)
Kernel 2.4.21-9.EL on an ia64
glibc-2.3.2-95.6 Fortran compiler: Intel(R) Fortran Itanium(R) Compiler for Itanium(R)-based applications
version 8.1 Build 20050826 Package ID: l_fc_pc_8.1.030 Vendor library: Intel MKL version 8.0 Compiler options: -O3 -tpp2 -fPIC -auto -implicitnone -openmp -fpp -w
This implementation has also been tested at NAG Ltd., Oxford for use with:
hardware: Intel Itanium2 operating system: Red Hat Enterprise Linux AS release 3 (Taroon Update 1)and
Kernel 2.4.21-9.EL on an ia64
glibc-2.3.2-95.6 Fortran compiler: Intel(R) Fortran Itanium(R) Compiler for Itanium(R)-based applications
version 9.1 Build 20060323 Package ID: l_fc_p_9.1.032 Vendor library: Intel MKL version 8.0
hardware: HP ZX2000 operating system: Red Hat Enterprise Linux WS release 4 (Nahant)
Kernel 2.6.9-5.EL on an ia64
glibc-2.3.4-2 Fortran compiler: Intel(R) Fortran Itanium(R) Compiler for Itanium(R)-based applications
version 8.1 Build 20050826 Package ID: l_fc_pc_8.1.030 Vendor library: Intel MKL version 8.0
Most source files were compiled with optimization flags -O3 -openmp -fpp. It was necessary to compile some code with different optimization flags.
These source files were compiled with optimization flags -O0 -openmp -fpp
c02agtn.f f06bcfn.f m01dafn.f s17deun.f x03aayn.f
These source files were compiled with optimization flags -O1 -openmp -fpp
f11mfyn.f f11mfzn.f m01defn.f m01dffn.f m01djfn.f m01dkfn.f m01dzfn.f
These source files were compiled with optimization flags -O2 -openmp -fpp
c06hcfn.f c06hdfn.f c06lazn.f e04nmwn.f f02bjyn.f f04fffn.f f04yayn.f f06clfn.f g03fazn.f g11sazn.f g12bazn.f
In this implementation calls to BLAS and LAPACK routines are implemented by calls to Intel MKL, except for the routines reported in Users' Note, Routine-specific Information. The library has been tested with MKL version 8.0. This version of MKL is supplied as a part of this product (see contents).
|- doc -|- in.html (Installer's Note, (this document))
| |- un.html (Users' Note)
|
| |- libnagsmp.a (static library requiring
|- lib -| vendor BLAS/LAPACK)
| |- libnagsmp.so (shareable library requiring
| vendor BLAS/LAPACK)
fsl6421dcl -|
|- nag_interface_blocks -|- *
|
| |- source --|- ??????e.f
|- examples -|- data ----|- ??????e.d
| |- results -|- ??????e.r
|
|- scripts -|- nagsmp_example*
|
|- mkl8.0 --|- * (Intel Math Kernel Library)
|
| |- bin -|- * (directories of binaries
| | for supported platforms)
|- license -|- README.TXT
|
|- doc -|- * (End User Guide)
The following shows the directory/file organization of the NAG Mark 21 Library Manual, which we will refer to as the Library Manual, as they will be installed.
nagdoc_mk21 -|- examples -|- baseresults -|- ??????*.r
| |- source -|- ??????*.f
| |- data -|- ??????*.d
|
|
|- html -|- mark21.html (main HTML index)
| |
| |- [A00-X05] -|- *conts.html (chapter contents)
| |
| |- frontmatter -|- *.html (foreword & copyright)
| |
| |- genint -|- *.html (general introductory material
| | and online help document)
| |
| |- indexes -|- gams -|- fl_gams.html (GAMS index)
| | | |- *.html (GAMS files)
| | |
| | |- kwic -|- fl_kwic.html (KWIC index)
| | |- *.html (KWIC files)
| |
| |- styles -|- libdoc.css (main CSS stylesheet)
|
|- pdf -|- frontmatter -|- mark21.pdf (NAG copyright and main
| | pdf page)
| |- foreword.pdf
|
|- [A00-X05] -|- *conts.pdf (chapter contents)
| |- *intro.pdf (chapter introduction)
| |- *f.pdf (routine documents)
|
|- genint -|- *.pdf (general introductory material
| and online help document)
|
|- indexes -|- *.pdf (bookmarked file containing links
| to fl_kwic.html and fl_gams.html)
|
|- INUNs -|- *.pdf (implementation specific note)
compiled libraries: libnagsmp.a 64 MB libnagsmp.so 47 MB interface blocks: 4 MB Intel MKL library: 88 MB example program material: 15 MB scripts: 12 KB implementation specific documentation: 28 KB Library Manual: 213 MB licensing materials: 2 MB
./install.shBy default, the materials will be installed in /opt/NAG/ or /usr/local/NAG/ depending on your system. The installer may choose a different location. In this document we refer to the directory /opt/NAG/fsl6421dcl or /usr/local/NAG/fsl6421dcl as [INSTALL_DIR].
The directory [INSTALL_DIR] is referenced in the Users' Note (un.html).
The directory [INSTALL_DIR]/scripts contains one or more scripts to show how to use the libraries provided with this implementation. See Users' Note, Example Programs. Subsequent to the installation, if the installer moves the library to some other location then these scripts must be changed to reflect that fact.
To simplify access to the libraries you may wish to create symbolic links in a system location such as /usr/lib pointing at the installed libraries. They would then be in the default search path of the linker during the link phase, and be available for execution at run time (in the case of shareable libraries). Note that if both the static and shareable version of a library are placed in a directory then the shareable version is usually used by default.
The NAG SMP Library Interface Blocks define the type and arguments of each user callable NAG SMP Library routine. These are not essential to calling the NAG SMP Library from Fortran 90/95 programs. Their purpose is to allow the Fortran 90/95 compiler to check that NAG SMP Library routines are called correctly.
The interface block files (nag_interface_blocks/*) are supplied in both source form and pre-compiled module form.
The -Ipathname option should then be specified on each f90/f95 invocation (where pathname is [INSTALL_DIR]/nag_interface_blocks) to tell the compiler where to find the modules.
The install script can install the Library Manual in the same location as the NAG Library material or at some other location of the installer's choice.
You may wish to move the Library Manual to the same location as that for other NAG products. You are encouraged to make them readily available to users.
The libraries can be installed manually by following the instructions below:
Use the tar utility to extract the materials, e.g.
tar xvf /cdrom/fs21.tar(assuming the CD-ROM has been mounted as /cdrom).
Each library is provided in both static and shareable format. You may choose to install some or all of the libraries.
To simplify access to the libraries you may wish to create symbolic links in a system location such as /usr/lib pointing at the installed libraries. Then they would be in the default search path of the linker during the link phase, and be available for execution at run time (in the case of shareable libraries). Note that if both the static and shareable version of a library are placed in a directory then the shareable version is usually used by default.
The NAG SMP Library Interface Blocks define the type and arguments of each user callable NAG SMP Library routine. These are not essential to calling the NAG SMP Library from Fortran 90/95 programs. Their purpose is to allow the Fortran 90/95 compiler to check that NAG SMP Library routines are called correctly.
The interface block files (nag_interface_blocks/*) are supplied in both source form and pre-compiled module form.
The -Ipathname option should then be specified on each f90/f95 invocation (where pathname is [INSTALL_DIR]/nag_interface_blocks) to tell the compiler where to find the modules.
The directory [INSTALL_DIR]/scripts contains one or more scripts to show how to use the libraries provided with this implementation. These scripts refer to the local directory containing the example programs. The files should be copied to (for example) /usr/local/bin, modified to reflect the local installation, and their protection set to world execute.
To install the Library Manual, use the tar utility, e.g.
tar xvf /cdrom/mk21_doc.tar(assuming the CD-ROM has been mounted as /cdrom).
You may wish to move the Library Manual to the same location as that for other NAG products. You are encouraged to make them readily available to users.
In order to enable the software, NAG will issue you with a license key. The license key is contained in a text file consisting of details of the software that will be enabled.
To request a license key, run the program khostid located in the license/bin/ia64/ subdirectory of the software distribution. This utility must be run from a command prompt. Return the information that it displays, together with the product code (in this case FSL6421DC), by e-mail (or FAX) to NAG. Alternatively, direct the output from this utility to a file and send both the file and the product code to NAG.
A short term (demonstration or trial) license key contains one or more lines like the following:
FSL6421DC TRIAL 2005/11/12 "EMnxidA3oeoj0F1Yvi5ibxPjB7"Specifically, it has a line containing the word TRIAL. Longer term 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 word NODE instead of the word TRIAL above.
Once you have obtained one of the above license keys, store the text of it in a file, say
[INSTALL_DIR]/license.lic.The location of the license file must be made known to the NAG application by setting the environment variable NAG_KUSARI_FILE to the full pathname of the file before the application is invoked.
For example, in the C-shell, type:
setenv NAG_KUSARI_FILE [INSTALL_DIR]/license.licor in the Bourne shell, type:
NAG_KUSARI_FILE=[INSTALL_DIR]/license.lic export NAG_KUSARI_FILE
Further details about Kusari and how it may be configured to suit your local circumstances are included in the Kusari License Management documentation in the license/doc/ subdirectory of the software distribution.
The following material should also be made accessible to users:
documentation files:
The nagdoc_mk21 directory contains the Library Manual. This should be made available to users.
compiled libraries:
libnagsmp.a libnagsmp.so Intel Math Kernel libraries supplied by NAGinterface block files:
nag_interface_blocks/*example program material:
examples/source/??????e.f examples/data/??????e.d examples/results/??????e.r scripts/nagsmp_example*
Note that the example material has been adapted, if necessary, from that published in the Library Manual, so that programs are suitable for execution with this implementation with no further changes (but see Section 4.3.1 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 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 scripts nagsmp_example*.
On-line documentation is bundled with this implementation. Please see Section 4.
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, it helps us deal with your enquiry quickly if you can quote your NAG site reference and NAG product code (in this case FSL6421DCL).
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 the following URLs:
http://www.nag.co.uk/, http://www.nag.com/ or http://www.nag-j.co.jp/
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: support@nag.com Tel: +1 630 971 2337 Tel: +1 630 971 2337 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