NAG dco/c++ version 4.4

DBL6I04XNL - Licence Managed

Linux, 64-bit

Installer's Note



Contents


1. Introduction

This document provides implementation-specific information relating to the installation of dco/c++ base.

2. Implementation Provided

2.1. Applicability

This implementation is considered suitable for operation on the computer systems detailed below:

hardware:          Intel 64-bit systems and compatible
operating system:  Linux 64-bit editions
C++ compiler:      Any GNU >= 7.5 compatible compiler with GLIBC version >= 2.17

2.2. Supplementary Information

Please check the following URL:

https://www.nag.com/doc/inun/db04/l6ixnl/supplementary.html

for details of any new information related to the applicability or usage of this implementation. Details of any other systems on which it has been tested may also be found on this page.

3. Distribution

The software is distributed via NAG website.

3.1. Contents

The following shows the folder and file organization of the implementation materials after installation:
                 |- bin -|- (licence management tools)
                 |
                 |- case_studies -|- (more sophisticated examples from the
                 |                |   user guide, along with the corresponding CMakeLists.txt)
                 |
                 |- cmake -|- (auxiliary files required for building and testing with CMake)
                 |
                 |- doc   -|- in.html  (Installer's Note - this document)
                 |         |- userguide.pdf (User Guide as pdf)
                 |         |- nag_tsandcs.txt (terms and conditions)
                 |         |- licence -|- *  (licence management documentation)
dbl6i04xnl_v440 -|
                 |
                 |- examples -|- (directories containing various example programs
                 |            |   from the user guide, along with the CMakeLists.txt)
                 |
                 |- include -|- *.hpp  (C++ header files)
                 |
                 |- lib -|- libdcoc.a (static library file)
                 |
                 |- CMakeLists.txt -|- (used for building and testing)  

4. Installation on Linux

4.1. Normal Installation

Assuming you have downloaded the dco/c++ installer from our website, extract the installation materials using the following command:

  tar xvzf dbl6i04xnl_v440.tgz

This will extract the files in.html, install.sh, dbl6i04xnl_v440.tar.gz and nag_tsandcs.txt.

You can then install the materials from the download directory by executing the shell script install.sh in a command window as:

  ./install.sh

By default, the dco/c++ materials are installed in

  ${HOME}/NAG/dbl6i04xnl_v440

or the equivalent for your locale.

4.2. Silent Installation

It is also possible to run install.sh in unattended or silent modes. The installer takes command line switches for this purpose:

4.3. Licence Management

The use of this product is controlled by the Kusari licence management system. This release of dco/c++ uses version 2.2-88 of Kusari.

In order to enable the software, NAG will issue you with a licence key. The licence key is contained in a text file consisting of details of the software that will be enabled. For evaluation purposes a trial licence may be used. Before obtaining a full licence you need to know the Kusari hostid of the system on which you intend to use this product. How to do this is described below.

To request a licence key, run the program khostid located in the bin 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 DBL6I04XNL), by email 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) licence key contains one or more lines like the following:
<PRODUCT_CODE> TRIAL <EXPIRY_DATE> "EMnxidA3oeoj0F1Yvi5ibxPjB7"
Specifically, it has a line containing the word TRIAL. Longer term licence keys must be locked to a specific computer, i.e. they will enable the software on one computer only. These licence keys typically include the word NODE or FULL instead of the word TRIAL above and may contain extra fields.
Once you have obtained one of the above licence keys, the easiest way to install it is to store the text in a file,
  $HOME/nag.key
or
  /opt/NAG/nag.key
or
  /usr/local/NAG/nag.key
The licence software in this implementation automatically looks for these particular files and reads the first one found, so no further action is necessary. Alternatively, store the licence in a file with a name and location of your choice, say,
  dbl6i04xnl_v440/licence.lic
The location of the licence file, if it is not one of the default places listed above, 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 dbl6i04xnl_v440/licence.lic
or in the Bourne shell, type:
  NAG_KUSARI_FILE=dbl6i04xnl_v440/licence.lic
  export NAG_KUSARI_FILE
Further details about Kusari and how it may be configured to suit your local circumstances (e.g. how to install the licence key on a server) are included in the Kusari Licence Management documentation in the doc/licence/ subdirectory of the software distribution. See also the Kusari FAQ.

5. Example Programs

Access to the dco/c++ materials can be checked by running a few example programs following the advice given below. Detailed documentation on dco/c++ and examples is located in the User Guide which can be found in the dbl6i04xnl_v440/doc directory.

More sophisticated examples (case studies) are located in folders

5.1. Running from the Command Line

6. Contact NAG

To get maximum benefit of dco/c++ please contact the NAG Technical Support Service. We would be delighted to receive your feedback on NAG's products and services.