apogee-software apogee compilers c & c++ & fortran 77 & fortran 90 User Manual

Apogee User’s Manual  Page 203

The considerations that affect this decision are as follows:

1) The identity of the license-server machine (or machines) is specified at the time the

product is purchased, and remains fixed thereafter (since the hostid of the license-
server is part of the data that is secured by encryption).

2) Each executing copy of

 is tied to a specific license-file that is determined at the

time

 starts up.

3) License-files may be merged, i.e. each license-file may have features from more than

one vendor (by including more than one DAEMON line, plus all the relevant
FEATURE lines), or may have features from more than one purchase of Apogee
products (by including all the relevant FEATURE lines).

4) There may be multiple copies of

 executing on one license-server, each one

associated with a different license-file.  However, there may only be one copy of each
vendor daemon executing on any one license-server, therefore: a) if there are multiple
copies of

 executing, the license-files to which they are tied must have disjoint

sets of vendors, and b) each license-server may only support one license-file from any
one vendor.

5) There may be administrative reasons for wishing to have either separate license-files

or merged license-files, or to have either one or multiple copies of

.  The

overhead of multiple

 processes is small, so any increase in efficiency from

decreasing their number would be hard to measure.

Once a decision has been made to merge license-files, the following actions must be taken:

1) A decision must be made about the placement and visibility of the merged license-file.

In general, the identical file contents must be visible to all involved applications and to

.  This may be accomplished by making copies, by using symbolic links, by

using hard links, or by using the

 environment variable.  For

Apogee products, the file must either be named in

 or be linked as

 at the correct place in the installation directory.

2) The most recent version of

 used in all of the vendor shipments that are

involved must be located and used.  As described above, the version of each

can be seen in its logged output.  Old versions of

 will not be able to properly

initialize and communicate with new versions of vendor daemons.  If you see errors in
the logged output of the

 using the merged

 file indicating

initialization or communication problems with some of the vendor daemons
(particularly if you see that some work and some fail), it is most likely a version
mismatch.  The error message most often given in this situation is "invalid returned
data from license server".  (The version of

 used by the Apogee version 4.0

compilers is FLEXlm version 2.40.  The version that was used by the Apogee compilers
before version 2.0 was FLEXlm version 2.21.)