Q. Do I need to run a licence server for my Kusari key?

A. You only need to run a licence server for FLOATING and SITE keys. All other keys are simply placed in a file and the environment variable NAG_KUSARI_FILE set to the name of this file.

Q. How do I create my licence file?

A. If you have been sent, for example, a trial key for a NAG product, please follow the procedure detailed below

• Choose a name for your licence file
• Open a text editor to create this file, e.g. on Windows use Notepad (not Microsoft Word) and on Unix use vi or emacs (and not a word processor)
• Cut and paste the key from the email message, ensuring that a new line is added at the end of the last (or only) line
• Ensure that the entire line or lines of the key are copied
• Feel free to copy any comments surrounding your key (these are lines beginning with an exclamation mark)
• Save this file
• On Unix, ensure the file permissions allow all users read access
• Set the environment variable NAG_KUSARI_FILE to the name of this file

Q. How do you set the NAG_KUSARI_FILE environment variable on Microsoft Windows?

A. E.g. to set NAG_KUSARI_FILE to "c:\nag\fl.licence,myserver:" Under Microsoft Windows XP, right click "My computer" then select

Properties -> Advanced tab -> Environment variable button

Under Microsoft Vista, find "Computer" on the Start menu, and right click it, choosing "Properties" from the pop-up menu. On the left-hand side of the resulting window you should see "Advanced System Settings". Clicking that will bring up the "Advanced" tab of "System Properties", and once again you should see a button labelled "Environment Variables". On Microsoft Windows 10, Click on Start, then Settings, then search for “environment variables”. Click on “Edit the system environment variables” in the search results. Click "New" (under user variables), set the variable name to NAG_KUSARI_FILE and value to c:\nag\fl.licence,myserver:
N.B. Even if the licence file name contains spaces you should not surround the name in quotes.
 

Q. Why is my licence rejected with "Format error in licence file"?

A. This may be because the last line in the file is not terminated by a carriage return. Please add a carriage return to the last line of your licence file or server control file. Kusari 2.2 fixes this problem.
 

Q. Can I have multiple keys in one file?

A. Yes, say you have node-locked and trial keys for different NAG products you can put one key per line into the licence file. Comments can be added with an exclamation mark in the first character position of the line and blank lines may be used to make the file easier to read. E.g.

! Licence file for NAG products.

! A full licence for the NAG Fortran Compiler, Release 7.1
NPW3271NA FULL "qfrdwhyMoQFkfpm5e6ESprJmtE"

! A trial licence for the NAG Fortran Compiler, Release 7.1
NPL6A71NA TRIAL 2023/07/30 "EMnxidA3oeojOFlYvi5ibxPjB7"

! A licence for the NAG Library on this machine, Mark 29:
NLL6I29XB NODE 2024/12/31 "xhhhTkzEiUPgdIpwIbCHgrBjjv"
! End

Q. How do I specify more than one licence file and/or server?

A. Set the NAG_KUSARI_FILE environment variable to a comma separated list of files and servers. E.g, if you have your Fortran Library key in /etc/fl.licence and your NAG Fortran Compiler licences are on the server called myserver.

With Bourne shell -

  NAG_KUSARI_FILE=/etc/fl.licence,myserver:
  export NAG_KUSARI_FILE

With bash -

  export NAG_KUSARI_FILE=/etc/fl.licence,myserver:

With csh or similar shells like tcsh -

  setenv NAG_KUSARI_FILE /etc/fl.licence,myserver:

For Microsoft Windows, please see Question 5 for how to do this and set the environment variable to, say, "C:\ETC\FL.LICENCE,myserver:"
 

Q. How do I find the Kusari licence server's version number?

A. To obtain this information, execute the licence server with the '-V' option, for example: ./naglmd -V.
 

Q. I have put my NAG Fortran key in the default place, but it's not found?

A. NAG Fortran allows you to put the licence key in a file called "nag.licence" in the compiler "lib" directory. If you do this you do not need to set the NAG_KUSARI_FILE environment variable. Please ensure that licence is spelt exactly as above (i.e. with two letters "c", and no "s"). NAG Fortran implementations licensed with Kusari 2.2 look for the file "nag.key" followed by the above names.
 

Q. My trial or node-locked key does not work. What can I do to check what is wrong?

A. Under Unix (including Linux)

At a command prompt or shell window issue the following commands.
 

    echo $NAG_KUSARI_FILE
    cat $NAG_KUSARI_FILE

  On Windows

    set NAG_KUSARI_FILE
    type "%NAG_KUSARI_FILE%"

Ensure that the file name reported by the first command is correct and that the second command prints out the file that you created with the key. If not, go back to Question 3 or 4 and review what you've done.

Under Microsoft Windows (licence installed in a file)

The first thing to check is that you set the environment variable NAG_KUSARI_FILE correctly. One way to find out is to start a DOS command prompt window. You can get a command prompt window from the Windows Start Menu by choosing Programs/Accessories/Command Prompt. Once the command prompt is open, type this:

  echo %NAG_KUSARI_FILE%
  type "%NAG_KUSARI_FILE%"

If the environment variable is set correctly you should see the licence key or keys that you put into the file, for example:

NLW6I29XE TRIAL 2023/07/21 "5VnUdiR+burfp+nxUlxvkPxiMW"

If it becomes clear that the file that you thought existed does not, it could be that the editor you used named the file something other than what you thought. For example, some editors will save your file as licence.lic.txt instead of licence.lic. If that is the case, you need to rename it.
You should also make sure that Sometimes it is easier to use a file name without spaces. If you have trouble with C:\Program Files\licence.lic, try using just C:\licence.lic instead.
 

• there is a newline character on the end of the last or only line in the file (some editors do not insert a newline by default)
• in the environment variable NAG_KUSARI_FILE, you do NOT put quotation marks around the name of the file. e.g. use C:\Program Files\... and not "C:\Program Files\..."