Table of Contents * Previous Chapter * Next Chapter

Q4. License File Locations

Q4.1 My application can't seem to find the license file. What do I do?

Applications find the license file in one of 3 places:

1. A location specified in the application by the vendor. See the application manual for this location.
2. $LM_LICENSE_FILE (including VMS and Windows/NT). In UNIX, this can also be a colon-separated list (like $PATH) of license files, so that this environment variable can be set once for all applications. In Windows, you use a semicolon-seperated list.

Q4.2 lmstat doesn't report all the features in my license file. Why?

Here's the possibilities:

1. $LM_LICENSE_FILE is set to the wrong file.
2. lmstat doesn't report on 'uncounted' features. These are features with a 'number of licenses' field set to '0' or uncounted (v6+). 'Number of licenses' is the 6th item on a FEATURE line (after the expiration date). There's nothing to report on uncounted features. NOTE: v5.+ of FLEXlm provides the option of having servers service 'uncounted' features, in which case lmstat will report these also.

Q4.3 I've received FLEXlm license files from 2 different companies. Do I have to combine them?

You don't have to combine license files. Each license file that has any 'counted' lines (the 'number of licenses' field is >0) requires a server. It's perfectly OK to have any number of separate license files, with different lmgrd server processes supporting each file. Moreover, since lmgrd is a lightweight process, for sites without system administrators, this is often the simplest (and therefore recommended) way to proceed.

Q4.4 I want to combine license files. How do I do it?

Pre v6:
Only license files with identical hostids on the SERVER line can be combined. Note that license files may refer to the same host using different hostids, particularly on hp700, where one file may use ethernet hostid, and another uname -i. In this case these license files CANNOT be combined because the hostids are not identical.

If the hostids are identical, concatenate the 2 files, and then remove identical SERVER lines, so there's only one (or three for redundant servers) SERVER line(s). It's then strongly recommended that symbolic links be made from the new, merged file to the old file locations. That way, the applications will be able to find the newly merged file without having to change anything.

Finally, make sure you use the latest version of lmgrd on the merged file. The FLEXlm version of lmgrd MUST be >= the FLEXlm version of the vendor daemon (noted on the DAEMON line). Use lmver to determine the FLEXlm version of the vendor daemon or lmgrd. (The patch letters at the end of the version are not significant when comparing versions for this purpose.)

v6+:
If all FLEXlm computers are v6+, you can set the $LM_LICENSE_FILE to a directory (or the application may have already specified this). Then all files named *.lic in that directory are automatically read as if they were combined.

Q4.5 When is it recommended to combine license files?

Many system administrators, especially for larger sites, prefer to combine license files to ease administration of FLEXlm licenses. It's purely a matter of preference.

Q4.6 How do I set the location of the license file with an Environment Variable?

You can set either LM_LICENSE_FILE or VENDOR_LICENSE_FILE(v6+).
Where VENDOR is the vendor daemon name in all uppercase(e.g., GSI_LICENSE_FILE).

In UNIX:

% setenv LM_LICENSE_FILE license_file_path

In Windows 3.1 and 95/98:

edit autoexec.bat

type SET LM_LICENSE_FILE=license_file_path

In Windows NT:

In the Control Panel "System icon" change global environment by adding LM_LICENSE_FILE with license_file_path