Summary

Will Setting LM_A_LICENSE_DEFAULT Override End-User Settings?

Synopsis

Is it possible to override registry settings and environment variables when setting LM_A_LICENSE_DEFAULT in the application?

Discussion

No this setting will not overide the VENDOR_LICENSE_FILE or LM_LICENSE_FILE

1. Environment Variable for VENDOR_LICENSE_FILE
2. Registry/.flexlmrc for VENDOR_LICENSE_FILE
3. Environment Variable for LM_LICENSE_FILE
4. Registry/.flexlmrc for LM_LICENSE_FILE
5. Application defined location (LM_A_LICENSE_DEFAULT)
6. Any ".lic" file located in the same directory as application (*.lic).
   Extract from documentation

If LM_A_LICENSE_DEFAULT is set, FLEXlm still honors the
VENDOR_LICENSE_FILE and LM_LICENSE_FILE environment variables
and/or the license finder first.

The following will still be followed by the application:

1. Choosing a License File
   Client applications use the following rules for choosing a license file to use:
   1. If a license-file list is set with either the VENDOR_LICENSE_FILE or
   LM_LICENSE_FILE (where VENDOR is the vendor?s daemon name)
   environment variable, it is used. VENDOR_LICENSE_FILE is used first.
   VENDOR_LICENSE_FILE is used only by products from VENDOR and by
   lmutil and LMTOOLS.
2. The environment variables VENDOR_LICENSE_FILE and/or
   LM_LICENSE_FILE can also be set in the Windows registry or, on UNIX,
   in $HOME/.flexlmrc. The Windows registry is in
   \HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager.
   VENDOR_LICENSE_FILE is also automatically set upon successful
   checkout.
3. The default license-file list can be set by the CHECKOUT() or
   lp_checkout() calls. This is searched after VENDOR_LICENSE_FILE
   and/or LM_LICENSE_FILE.
4. Licensing utilities accept -c license_file_list argument, which specifies the license paths.
   If this is set, the environment variables are ignored.
5. If none of the other locations are specified, then a backup/default location is used.

Relying on this default location is not recommended.