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: all SPARC systems
operating system: Solaris 2.6 (SunOS 5.6), Solaris 7 and 8 or compatible
Fortran compiler: Sun Fortran 77 v4.2, 5.0, 5.2, 5.3 or compatible
Sun Fortran 90/95 v2.0, 6.1, 6.2 or compatible
This implementation is suitable for use on 32 bit or 64 bit Sun Solaris
systems. Separate implementations, FLSO620DA and FLSO620DT, are available
which have been compiled with the
Note that, except for the two routines X04ACF and X04ADF, the libraries in this
implementation are compatible with Sun Fortran 90/95, provided that the f90/95
compiler is called with the flag
This implementation was produced at NAG Ltd., Oxford on the computing system detailed below:
hardware: Sun UltraSPARC-30 and also tested using a
Sun UltraSPARC-80 and a Sun UltraSPARC-5_10
operating system: Solaris 2.6 (SunOS 5.6) and also tested using
Solaris 7 and 8
Fortran compiler: Sun WorkShop 4.2 FORTRAN 77 v4.2. Also tested using:
Sun WorkShop 5.0 FORTRAN 77 v5.0
Sun WorkShop 6 update 1 FORTRAN 77 5.2.
Sun WorkShop 6 update 2 FORTRAN 77 5.3
Sun WorkShop 5.0 FORTRAN 90 v2.0
Sun WorkShop 6 update 1 Fortran 95 6.1 with Patch 109503-05
(f90 is a link to f95)
Sun WorkShop 6 update 2 Fortran 95 6.2
compiler options: -dalign -fsimple=1 -stackvar -mt -PIC
The entire NAG Fortran Library, Mark 20, was compiled with full optimization
(
The
The libnag.a and libnag.so.20 object libraries have 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). The
|-- msserver.html
|-- unixserver.html
|-- in.html
|-- un.html
|-- doc --|-- nag_fl_un.3
| |-- blas_lapack_to_nag
| |-- nag_to_blas_lapack
flsol20dal--|
|-- libnag.a (compiled static library including NAG BLAS/LAPACK)
|-- libnag.so.20 (compiled dynamic library including NAG BLAS/LAPACK)
|-- libnag-spl.a (compiled static library using Sun BLAS/LAPACK)
|-- libnag-spl.so.20 (compiled dynamic library using Sun BLAS/LAPACK)
|
|-- interface_blocks --|-- *.mod
|
| |-- source ---|-- ??????e.f
|-- examples --|-- data -----|-- ??????e.d
| |-- results --|-- ??????e.r
|
|-- scripts ---|-- *
|
| |-- bin ------|-- * (directories of FLEXlm binaries
| | for supported platforms)
|-- license ---|-- README.TXT
|-- enduser.pdf
| |-- flexfaq ---|-- * (FLEXlm FAQs)
|-- htmlman --|-- flexuser --|-- * (End User Guide)
|-- index.htm
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: 19.4 Mb
libnag.so.20: 14.6 Mb
libnag-spl.a: 19.3 Mb
libnag-spl.so.20: 14.6 Mb
interface blocks: 3.1 Mb
example program material: 6.5 Mb
scripts: 24 Kb
library documentation files: 68 Kb
PDF documentation files: 105 Mb
licensing materials 21.0 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).
A site may not need to install all four of the object libraries provided in this distribution. After installing all material as described above, you may wish to delete some material if it is not required.
To decide which is the most suitable object library for your site, determine:
After taking the above remarks into consideration, you may decide to delete some of the libraries.
The object libraries (libnag.a, libnag.so.20, etc.) 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. If you decided to install the shareable versions of the libraries, then once the libraries are in place symbolic links should be made to point to the shareable libraries, e.g.
ln -s libnag.so.20 libnag.so ln -s libnag-spl.so.20 libnag-spl.soUnless this is done, the linker, ld, will not be able to find the shareable libraries.
If you do not wish to move the libraries to a system directory, you may use
the
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
In order to enable the software, NAG will issue you with a license key. The license key is a simple text file (usually called license.dat), containing details of the software that will be enabled.
A short-term (demonstration or trial) license key contains one or more lines like the following:
FEATURE NAG_FL NAG 20.000 10-apr-2002 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.
To apply for a longer term license key, contact one of the NAG Response Centres quoting the product to be licensed and the FLEXlm hostid for the computer. To obtain the FLEXlm hostid, select the appropriate lmutil program from the platform specific directory under the license/bin/ subdirectory, and run it with argument lmhostid:
license/bin/sun4_u5/lmutil lmhostid
On systems without an ethernet card, use the arguments lmhostid -long.
Once you have obtained the license key, store the text of it in a file, say /usr/local/lib/nag/license.dat.
The location of this 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 /usr/local/lib/nag/license.dator in the Bourne shell, type:
LM_LICENSE_FILE=/usr/local/lib/nag/license.dat export LM_LICENSE_FILENo other actions are required to install an uncounted license.
More flexible than an uncounted license key, a counted one is suitable for a network of computers and enables one computer to provide licensing services to all other computers on the local network, (i.e. to act as a license server to NAG applications). In this way licenses may be shared by different users/workstations. In addition to FEATURE lines like the above, a counted license key includes SERVER and DAEMON lines. You must tell NAG the hostname (the output from the 'hostname' command) and FLEXlm hostid of the server when applying for a counted license. Note that a license server must be one of the most stable systems, accessible at all times by the licensed applications. It does not need to be the same architecture or running the same operating system as the systems where NAG applications will run.
Information on how to set up a license server on unixis available in the file doc/unixserver.html on the distribution medium.
Information on how to set up a license server on Microsoft Windows is available in the file doc/msserver.html on the distribution medium.
Further details about FLEXlm and how it may be configured to suit your local circumstances are included in the FLEXlm End Users Guide and FAQ supplied in the license/htmlman/ subdirectory.
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_lapackcompiled library:
libnag.a libnag.so (symbolic link pointing at libnag.so.20) libnag-spl.a libnag-spl.so (symbolic link pointing at libnag-spl.so.20)interface 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 it helps us deal with your enquiry quickly if you can quote your NAG site reference and NAG product code (in this case FLSOL20DAL).
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: 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