In addition, NAG recommends that before calling any Library routine you should read the following reference material (see Section 6):
(a) Essential Introduction
(b) Chapter Introduction
(c) Routine Document
for details of any new information related to the applicability or usage of this implementation.
Fortran 90/95/2003 users are advised that the compiled *.mod files (the interface blocks) have been compiled with the Intel Fortran Compiler 11.1 and are intended for use with that compiler. Users may have to compile the interface blocks themselves if they wish to use them with a different compiler.
When the DLL is used with a non-Intel compiler, please note that two input/output systems are in use: those of Intel for library routines and of course the compiler's own input/output routines for the calling program. This means that programs like the E04UDF example program cannot read the data from just one file. This is because the program reads some of the data using its input/output system. When the option setting routine tries to read the data file, the Intel input/output routines are used. The two input/output systems are completely disjoint and so in particular Intel has no knowledge of the position in the data file that the program input/output system has reached. The problem is circumvented by having two separate data files. Routines affected by this are mainly the option setting routines in chapters H02 and E04.
In this section we assume that the library has been installed in the default folder:
If this folder does not exist, please consult the system manager (or the person who did the installation). In some of the following subsections, this folder is referred to as install dir.
We also assume that the default shortcut for the command prompt is placed in the Start Menu under:
Start|All Programs|NAG|FS22|NAG Library (FSW3222DCL) for SMP and Multicore |FSW3222DCL Command Prompt
If this shortcut does not exist, please consult the system manager (or the person who did the installation). (Other shortcuts created as part of the Library installation procedure are also assumed to be in this location.)
To ensure that the NAG DLL is accessible at runtime, the install dir\bin folder must be on the path. The install dir\MKL_ia32_10.2\bin folder must also be on the path, but should appear later in the path than the install dir\bin folder, since the NAG versions of some linear algebra routines (BLAS or LAPACK) are included in FSW3222DC.dll. (See Section 5 for details.)
To check the accessibility of the NAG DLL, run the program NAG_Fortran_DLL_info.exe which is available from the Start Menu shortcut
Start|All Programs|NAG|FS22|NAG Library (FSW3222DCL) for SMP and Multicore |Check NAG DLL Accessibility (FSW3222DCL)See Section 4.2.3 of the Installer's Note for details of this utility.
To access this implementation from a command window some environment variables need to be set (if you chose not to allow the installation program to set them for you).
Start|All Programs|NAG|FS22|NAG Library (FSW3222DCL) for SMP and Multicore |FSW3222DCL Command Promptmay be used to start a command prompt window with the correct settings for the INCLUDE, LIB and PATH environment variables for the Library and the supplied MKL.
If the shortcut is not used, you can set the environment variables by running the batch file envvars.bat for this implementation. The default location of this file is:
c:\Program Files\NAG\FS22\fsw3222dcl\batch\envvars.batIf the file is not in the default location, you can locate it by searching for the file envvars.bat containing fsw3222dcl.
You may then compile and link to the NAG Fortran SMP Library on the command line using one of the following commands:
ifort /iface:cvf /MD /Qopenmp driver.f FSW3222DC_static.lib mkl_intel_s.lib mkl_intel_thread.lib mkl_core.lib user32.libwhere driver.f is your application program; or
ifort /iface:cvf /MD /Qopenmp driver.f FSW3222DC.libif the DLL version of the library is required. Note that in the DLL case it is not necessary to explicitly link to the MKL libraries. Notice that in both cases we compile using the /iface:cvf compiler flag. This tells the compiler that we wish to use the CVF calling convention. We also use the /MD compiler flag. This tells the compiler that we wish to link to multi-threaded DLL versions of compiler run-time libraries. Both these flags are important to ensure compatibility with this implementation of the NAG Library for SMP and Multicore. If you do not use them - particularly /iface:cvf - it is likely that your programs will fail to run correctly.
The /Qopenmp flag tells the compiler to heed any OpenMP directives that may be present in your own code. It also causes the linker to link to the compiler threading library, libiomp5md.lib. For older versions of the Intel compiler, a different threading library (named libguide) was used by default. If you are using an older compiler (such as ifort 10.1) then you may need to add libiomp5md.lib explicitly to the compile line, e.g.
ifort /iface:cvf /MD /Qopenmp driver.f FSW3222DC_static.lib mkl_intel_s.lib mkl_intel_thread.lib mkl_core.lib user32.lib libiomp5md.libor
ifort /iface:cvf /MD /Qopenmp driver.f FSW3222DC.lib libiomp5md.libto avoid error messages at link or run time.
More information on calling NAG Fortran or C DLLs is available on the NAG web site at
http://www.nag.co.uk/numeric/Num_DLLhelp.aspMore information specific to this product may be available from the Post Release Information page:
To ensure that the NAG DLLs are accessible at runtime, the PATH environment variable must be set such that the location of the NAG DLLs, specifically the folder install dir\bin, is on the path. If the MKL version of the DLL is required, the location of the MKL DLLs, install dir\MKL_ia32_10.2\bin must also be on the path, but should appear after the install dir\bin folder.
Once Visual Studio has been opened, it is possible to set up the directories for use with Intel Fortran in this and all subsequent projects which use this compiler. One way to do so is:
Having done this, if an Intel Fortran project requires a library or NAG interface block during the compilation and linking process then the full path to the library and interface block do not need to be specified.
The interface block is simply accessed by inserting a USE statement as described in greater detail in Section 4.3.
Whilst the above changes will apply to every Intel Fortran project, the following tasks need to be performed for each individual Intel Fortran project.
The library is intended to be run in fully optimised mode, so to avoid any warning messages, you might decide to set the active configuration to Release. You can do this from the Toolbar or alternatively via the Build|Configuration Manager menus. Note that if you work in Debug mode, you may receive a warning message about conflicting C run-time libraries.
There are a number of ways to add the NAG Library to the project. We describe just two; choose the one that most suits you.
If the Solution Explorer window is open then make sure that the group project (the first line) is NOT selected. From the Project menu, choose the project Properties item. (Alternatively right-click on a specific single project in the Solution Explorer and choose Properties.)
From the form, click/expand Linker in the leftmost panel and then choose Input. The right hand panel will now have an Additional Dependencies entry, and you need to type FSW3222DC.lib in this location. Press the OK button.
You will also need to set the calling convention to "CVF". From the Properties form, click/expand Fortran and then choose External Procedures. Click on the Calling Convention entry in the right hand panel and select CVF from the drop-down list. Selecting this option will automatically change the entry for String Length Argument Passing to After Individual String Argument when you click on Apply or OK; this is the convention required by this implementation of the NAG Library.
We also recommend that you use the multithreaded DLL version of the runtime library. From the Properties form, click/expand Fortran in the leftmost panel and then choose Libraries. Click on the Runtime Library entry in the right hand panel and select Multithread DLL from the drop-down list.
For a multithreaded application, as well as selecting a multithreaded run-time library, you should set the /automatic (or /Qauto) compiler flag, to ensure that all local variables are allocated on the stack. To set this option, from the Properties form click/expand Fortran and then choose Data. Click on the Local Variable Storage entry in the right hand panel and select Local Variables AUTOMATIC from the drop-down list. Press the OK button to accept the changes and close the form.
As described earlier when compiling from the command line, you may also wish to tell the compiler to use the /Qopenmp switch. From the Properties form, click/expand Fortran in the leftmost panel and then choose Language. Click on the Process OpenMP Directives entry in the right hand panel and select Generate Parallel Code (/QopenMP) from the drop-down list.
The Properties information may also be accessed via the Toolbar. With the project selected in Solution Explorer, choose the Properties Window button on the Toolbar. In the ensuing window choose then the rightmost Property Pages icon. Select the appropriate settings as detailed in the paragraphs above.
The project should now compile and link using the appropriate choice from the Build menu.
To run a program that does not require input or output redirected from standard input or standard output, from within the Microsoft Development Environment, the program may be executed via the Debug menu (by selecting Start Without Debugging, for example).
If a data file needs to be attached to the standard input or the output of a program needs to be redirected to the standard output, we recommend that you run the executable from a command prompt window to avoid the limitations of Visual Studio.
The samples folder of the library installation contains various subfolders which may help if you wish to call the library from C, C++, Microsoft Excel, Microsoft Visual Basic or VB.NET, or the Absoft, Lahey or gfortran Fortran compilers. We do not give detailed information on how to do that here, but more information may appear on the Post Release Information page:
Otherwise please contact NAG for advice.
set OMP_NUM_THREADS=Nwhere N is the number of processors required. OMP_NUM_THREADS may be re-set between each execution of the program, as desired.
(a) subroutines are called as such;
(b) functions are declared with the right type;
(c) the correct number of arguments are passed; and
(d) all arguments match in type and structure.
These interface blocks have been generated automatically by analysing the source code for the NAG Library for SMP & Multicore. As a consequence, and because these files have been thoroughly tested, their use is recommended in preference to writing your own declarations.
The NAG Library for SMP & Multicore Interface Block files are organised by Library chapter. The module names are:
nag_f77_a_chapter nag_f77_c_chapter nag_f77_d_chapter nag_f77_e_chapter nag_f77_f_chapter nag_f77_g_chapter nag_f77_h_chapter nag_f77_m_chapter nag_f77_p_chapter nag_f77_s_chapter nag_f77_x_chapterThese are supplied in pre-compiled form (.mod files) and they can be accessed by specifying the -module:pathname option on each compiler invocation, where pathname (install dir/nag_interface_blocks) is the path of the directory containing the compiled interface blocks. The interface block files are also supplied in source form, but these are only required if the precompiled form is incompatible with the compiler in use.
In order to make use of these modules from existing Fortran 77 code, the following changes need to be made:
The above steps need to be done for each unit (main program, function or subroutine) in your code.
These changes are illustrated by showing the conversion of the Fortran 77 version of the example program for NAG Library for SMP & Multicore routine D01DAF. Please note that this is not exactly the same as the example program that is distributed with this implementation. Each change is surrounded by comments boxed with asterisks.
* D01DAF Example Program Text * Mark 14 Revised. NAG Copyright 1989. ***************************************************** * Add USE statements for relevant chapters * USE NAG_F77_D_CHAPTER, ONLY: D01DAF * * ***************************************************** * .. Parameters .. INTEGER NOUT PARAMETER (NOUT=6) * .. Local Scalars .. DOUBLE PRECISION ABSACC, ANS, YA, YB INTEGER IFAIL, NPTS * .. External Functions .. DOUBLE PRECISION FA, FB, PHI1, PHI2A, PHI2B EXTERNAL FA, FB, PHI1, PHI2A, PHI2B * .. External Subroutines .. ****************************************************** * EXTERNAL declarations need to be removed. * * EXTERNAL D01DAF * * ****************************************************** * .. Executable Statements .. WRITE (NOUT,*) 'D01DAF Example Program Results' YA = 0.0D0 YB = 1.0D0 ABSACC = 1.0D-6 WRITE (NOUT,*) IFAIL = 1 * CALL D01DAF(YA,YB,PHI1,PHI2A,FA,ABSACC,ANS,NPTS,IFAIL) * IF (IFAIL.LT.0) THEN WRITE (NOUT,99998) ' ** D01DAF returned with IFAIL = ', IFAIL ELSE * WRITE (NOUT,*) 'First formulation' WRITE (NOUT,99999) 'Integral =', ANS WRITE (NOUT,99998) 'Number of function evaluations =', NPTS IF (IFAIL.GT.0) WRITE (NOUT,99998) 'IFAIL = ', IFAIL WRITE (NOUT,*) WRITE (NOUT,*) 'Second formulation' IFAIL = 1 * CALL D01DAF(YA,YB,PHI1,PHI2B,FB,ABSACC,ANS,NPTS,IFAIL) * WRITE (NOUT,99999) 'Integral =', ANS WRITE (NOUT,99998) 'Number of function evaluations =', NPTS IF (IFAIL.GT.0) WRITE (NOUT,99998) 'IFAIL = ', IFAIL END IF * 99999 FORMAT (1X,A,F9.4) 99998 FORMAT (1X,A,I5) END * DOUBLE PRECISION FUNCTION PHI1(Y) * .. Scalar Arguments .. DOUBLE PRECISION Y * .. Executable Statements .. PHI1 = 0.0D0 RETURN END * DOUBLE PRECISION FUNCTION PHI2A(Y) * .. Scalar Arguments .. DOUBLE PRECISION Y * .. Intrinsic Functions .. INTRINSIC SQRT * .. Executable Statements .. PHI2A = SQRT(1.0D0-Y*Y) RETURN END * DOUBLE PRECISION FUNCTION FA(X,Y) * .. Scalar Arguments .. DOUBLE PRECISION X, Y * .. Executable Statements .. FA = X + Y RETURN END * DOUBLE PRECISION FUNCTION PHI2B(Y) ***************************************************** * Add USE statements for relevant chapters * USE NAG_F77_X_CHAPTER, ONLY: X01AAF * * ***************************************************** * .. Scalar Arguments .. DOUBLE PRECISION Y * .. External Functions .. ****************************************************** * Function Type declarations need to be removed. * * DOUBLE PRECISION X01AAF * * ****************************************************** ****************************************************** * EXTERNAL declarations need to be removed. * * EXTERNAL X01AAF * * ****************************************************** * .. Executable Statements .. PHI2B = 0.5D0*X01AAF(0.0D0) RETURN END * DOUBLE PRECISION FUNCTION FB(X,Y) * .. Scalar Arguments .. DOUBLE PRECISION X, Y * .. Intrinsic Functions .. INTRINSIC COS, SIN * .. Executable Statements .. FB = Y*Y*(COS(X)+SIN(X)) RETURN END
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. The distributed example programs should be used in preference to the versions in the Library Manual wherever possible.
The example programs are most easily accessed by the batch files nagsmp_example_static.bat or nagsmp_example_dll.bat which are in the folder install dir\batch.
The batch files need the environment variable NAG_FSW3222DCL.
As mentioned in Section 4.1.1, the installation procedure provides a shortcut which starts a Command Prompt with local environment variables. The environment variables include NAG_FSW3222DCL. This shortcut is placed in the Start Menu under
Start|All Programs|NAG|FS22|NAG Library (FSW3222DCL) for SMP and Multicore |FSW3222DCL Command PromptIf the shortcut is not used, you need to set this environment variable. You can set this environment variable by running the batch file envvars.bat for this implementation. The default location of this file is:
c:\Program Files\NAG\FS22\fsw3222dcl\batch\envvars.batIf the file is not in the default location, you can locate it by searching for the file envvars.bat containing FSW3222DCL.
The batch script nagsmp_example_static.bat will provide you with a copy of an example program (and its data, if any), compile the program and link it with the library FSW3222DC_static.lib and the MKL. Finally, the executable program will be run.
The example program concerned, and the number of OpenMP threads to use, are specified by the arguments to nagsmp_example_static.bat, e.g.
nagsmp_example_static e04ucf 4will copy the example program e04ucfe.f and its data file e04ucfe.d into the current directory and process them to produce the example program results in the file e04ucfe.r.
Alternatively you could use:
nagsmp_example_dll e04ucf 4
The difference between nagsmp_example_static.bat and nagsmp_example_dll.bat is that while nagsmp_example_static.bat links to the static version of the NAG SMP and MKL Libraries, nagsmp_example_dll.bat links to the DLL versions of the libraries.
In order to support all implementations of the Library, the Manual has adopted a convention of using bold italics to distinguish terms which have different interpretations in different implementations.
For this double precision implementation, the bold italicised terms used in the Library Manual should be interpreted as follows:
real means REAL double precision means DOUBLE PRECISION complex means COMPLEX complex*16 means COMPLEX*16 (or equivalent) basic precision means DOUBLE PRECISION additional precision means quadruple precision reduced precision means REAL
Another important bold italicised term is machine precision, which denotes the relative precision to which double precision floating-point numbers are stored in the computer, e.g. in an implementation with approximately 16 decimal digits of precision, machine precision has a value of approximately 1.0D-16.
The precise value of machine precision is given by the routine X02AJF. Other routines in Chapter X02 return the values of other implementation-dependent constants, such as the overflow threshold, or the largest representable integer. Refer to the X02 Chapter Introduction for more details.
The bold italicised term block size is used only in Chapters F07 and F08. It denotes the block size used by block algorithms in these chapters. You only need to be aware of its value when it affects the amount of workspace to be supplied – see the parameters WORK and LWORK of the relevant routine documents and the Chapter Introduction.
In Chapters F06, F07 and F08, alternate routine names are available for BLAS and LAPACK derived routines. For details of the alternate routine names please refer to the relevant Chapter Introduction. Note that applications should reference routines by their BLAS/LAPACK names, rather than their NAG-style names, for optimum performance.
C06PAF C06PCF C06PFF C06PJF C06PKF C06PPF C06PQF C06PRF C06PSF C06PUF C06PXF C06RAF C06RBF C06RCF C06RDFThe Intel DFTI routines allocate their own workspace internally, so no changes are needed to the size of workspace array WORK passed to the NAG C06 routines listed above from that specified in their respective library documents.
In this implementation calls to Basic Linear Algebra Subprograms (BLAS)
and the Linear Algebra PACKage (LAPACK) routines are implemented by calls to Intel MKL,
except for the following routines:
DBDSDC DGBRFS DGBSV DGBSVX DGEBRD DGEES DGEESX DGEEV DGEEVX DGELS DGELSD DGELSS DGELSY DGEQP3 DGERFS DGESDD DGESV DGESVD DGESVX DGETRF DGETRS DGGES DGGESX DGGEV DGGEVX DGGGLM DGGLSE DGGQRF DGGRQF DGTRFS DGTSVX DHSEIN DLALSD DLASDA DLASDQ DOPGTR DORGHR DORGQR DORGTR DORMBR DORMTR DPBRFS DPBSV DPBSVX DPBTRF DPBTRS DPORFS DPOSV DPOSVX DPOTRS DPPRFS DPPSV DPPSVX DPTEQR DPTRFS DPTSVX DSBEV DSBEVD DSBEVX DSBGV DSBGVD DSBGVX DSPEV DSPEVD DSPEVX DSPGV DSPGVD DSPGVX DSPRFS DSPSVX DSTEBZ DSTEDC DSTEGR DSTEIN DSTEQR DSTEV DSTEVD DSTEVR DSTEVX DSYEV DSYEVD DSYEVR DSYEVX DSYGV DSYGVD DSYGVX DSYRFS DSYSVX DTBRFS DTBTRS DTGSNA DTPRFS DTPTRS DTRRFS ZCGESV ZGBRFS ZGBSV ZGBSVX ZGBTRF ZGEES ZGEESX ZGEEV ZGEEVX ZGELS ZGELSD ZGELSS ZGELSY ZGEQP3 ZGERFS ZGESDD ZGESV ZGESVD ZGESVX ZGETRF ZGETRS ZGGES ZGGESX ZGGEV ZGGEVX ZGGGLM ZGGLSE ZGGQRF ZGGRQF ZGTRFS ZGTSVX ZHBEV ZHBEVD ZHBEVX ZHBGV ZHBGVD ZHBGVX ZHEEV ZHEEVD ZHEEVR ZHEEVX ZHEGV ZHEGVD ZHEGVX ZHERFS ZHESVX ZHPEV ZHPEVD ZHPEVX ZHPGV ZHPGVD ZHPGVX ZHPRFS ZHPSVX ZHSEIN ZLALSD ZPBRFS ZPBSV ZPBSVX ZPBTRF ZPBTRS ZPORFS ZPOSV ZPOTRS ZPPRFS ZPPSV ZPPSVX ZPTEQR ZPTRFS ZPTSVX ZSPRFS ZSPSVX ZSTEDC ZSTEGR ZSTEIN ZSTEQR ZSYRFS ZSYSVX ZTBRFS ZTBTRS ZTPRFS ZTPTRS ZTRRFS ZUNGBR ZUNGHR ZUNGQR ZUNGTR ZUNMBR ZUNMTR ZUPGTR
S07AAF F_1 = 1.0E+13 F_2 = 1.0E-14 S10AAF E_1 = 1.8715E+1 S10ABF E_1 = 7.080E+2 S10ACF E_1 = 7.080E+2 S13AAF X_hi = 7.083E+2 S13ACF X_hi = 1.0E+16 S13ADF X_hi = 1.0E+17 S14AAF IFAIL = 1 if X > 1.70E+2 IFAIL = 2 if X < -1.70E+2 IFAIL = 3 if abs(X) < 2.23E-308 S14ABF IFAIL = 2 if X > X_big = 2.55E+305 S15ADF X_hi = 2.65E+1 S15AEF X_hi = 2.65E+1 S15AFF underflow trap was necessary S15AGF IFAIL = 1 if X >= 2.53E+307 IFAIL = 2 if 4.74E+7 <= X < 2.53E+307 IFAIL = 3 if X < -2.66E+1 S17ACF IFAIL = 1 if X > 1.0E+16 S17ADF IFAIL = 1 if X > 1.0E+16 IFAIL = 3 if 0.0E0 < X <= 2.23E-308 S17AEF IFAIL = 1 if abs(X) > 1.0E+16 S17AFF IFAIL = 1 if abs(X) > 1.0E+16 S17AGF IFAIL = 1 if X > 1.038E+2 IFAIL = 2 if X < -5.7E+10 S17AHF IFAIL = 1 if X > 1.041E+2 IFAIL = 2 if X < -5.7E+10 S17AJF IFAIL = 1 if X > 1.041E+2 IFAIL = 2 if X < -1.9E+9 S17AKF IFAIL = 1 if X > 1.041E+2 IFAIL = 2 if X < -1.9E+9 S17DCF IFAIL = 2 if abs(Z) < 3.92223E-305 IFAIL = 4 if abs(Z) or FNU+N-1 > 3.27679E+4 IFAIL = 5 if abs(Z) or FNU+N-1 > 1.07374E+9 S17DEF IFAIL = 2 if imag(Z) > 7.00921E+2 IFAIL = 3 if abs(Z) or FNU+N-1 > 3.27679E+4 IFAIL = 4 if abs(Z) or FNU+N-1 > 1.07374E+9 S17DGF IFAIL = 3 if abs(Z) > 1.02399E+3 IFAIL = 4 if abs(Z) > 1.04857E+6 S17DHF IFAIL = 3 if abs(Z) > 1.02399E+3 IFAIL = 4 if abs(Z) > 1.04857E+6 S17DLF IFAIL = 2 if abs(Z) < 3.92223E-305 IFAIL = 4 if abs(Z) or FNU+N-1 > 3.27679E+4 IFAIL = 5 if abs(Z) or FNU+N-1 > 1.07374E+9 S18ADF IFAIL = 2 if 0.0E0 < X <= 2.23E-308 S18AEF IFAIL = 1 if abs(X) > 7.116E+2 S18AFF IFAIL = 1 if abs(X) > 7.116E+2 S18DCF IFAIL = 2 if abs(Z) < 3.92223E-305 IFAIL = 4 if abs(Z) or FNU+N-1 > 3.27679E+4 IFAIL = 5 if abs(Z) or FNU+N-1 > 1.07374E+9 S18DEF IFAIL = 2 if real(Z) > 7.00921E+2 IFAIL = 3 if abs(Z) or FNU+N-1 > 3.27679E+4 IFAIL = 4 if abs(Z) or FNU+N-1 > 1.07374E+9 S19AAF IFAIL = 1 if abs(X) >= 5.04818E+1 S19ABF IFAIL = 1 if abs(X) >= 5.04818E+1 S19ACF IFAIL = 1 if X > 9.9726E+2 S19ADF IFAIL = 1 if X > 9.9726E+2 S21BCF IFAIL = 3 if an argument < 1.583E-205 IFAIL = 4 if an argument >= 3.765E+202 S21BDF IFAIL = 3 if an argument < 2.813E-103 IFAIL = 4 if an argument >= 1.407E+102
X01AAF (pi) = 3.1415926535897932 X01ABF (gamma) = 0.5772156649015328
X02BHF = 2 X02BJF = 53 X02BKF = -1021 X02BLF = 1024 X02DJF = .TRUE.Derived parameters of the floating-point arithmetic
X02AJF = 1.11022302462516E-16 X02AKF = 2.22507385850721E-308 X02ALF = 1.79769313486231E+308 X02AMF = 2.22507385850721E-308 X02ANF = 2.22507385850721E-308Parameters of other aspects of the computing environment
X02AHF = 1.42724769270596E+45 X02BBF = 2147483647 X02BEF = 15 X02DAF = .TRUE.
The Library Manual is available as part of the installation or via download from the NAG website. The most up-to-date version of the documentation is accessible via the NAG website at http://www.nag.co.uk/numeric/FL/FSdocumentation.asp.
The Library Manual is supplied in the following formats:
The following main index files have been provided for these formats:
nagdoc_fl22/xhtml/FRONTMATTER/manconts.xml nagdoc_fl22/pdf/FRONTMATTER/manconts.pdf nagdoc_fl22/html/FRONTMATTER/manconts.htmlUse your web browser to navigate from here.
Advice on viewing and navigating the formats available can be found in the Online Documentation document.
In addition the following are provided:
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 or account number and NAG product code (in this case FSW3222DCL).
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/ http://www.nag-j.co.jp/ or http://www.nag-gc.com/
NAG Ltd Wilkinson House Jordan Hill Road OXFORD OX2 8DR NAG Ltd Response Centre United Kingdom email: email@example.com Tel: +44 (0)1865 511245 Tel: +44 (0)1865 311744 Fax: +44 (0)1865 310139 Fax: +44 (0)1865 310139 NAG Inc 801 Warrenville Road Suite 185 Lisle, IL 60532-4332 NAG Inc Response Center USA email: firstname.lastname@example.org 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 Nihon NAG Response Centre Japan email: email@example.com Tel: +81 3 5542 6311 Tel: +81 3 5542 6311 Fax: +81 3 5542 6312 Fax: +81 3 5542 6312 NAG Taiwan Branch Office 5F.-5, No.36, Sec.3 Minsheng E. Rd. Taipei City 10480 NAG Taiwan Response Centre Taiwan email: firstname.lastname@example.org Tel: +886 2 25093288 Tel: +886 2 25093288 Fax: +886 2 25091798 Fax: +886 2 25091798