The Support team at IAR Systems can occasionally refer to these environment variables (that exists in the licensing library) when sorting out problems in a Client-PC-to-License-Server-situation.
These environment variables can cause rather tricky issues with conflicting settings. In the vast majority of cases there are other ways to provide information that are better.
These environment variables are set at the Client PC with the effects that follows.
(Set the License Key File) This variable can be used to specify the file that is used to store the stand-alone keys used by IAR Embedded Workbench.
LSFORCEHOST (1 of 2)
(Point out a Network License)
IAR Embedded Workbench will try to obtain a network license by communicating with a license server located somewhere on the same subnet. You can point out the license server by setting LSFORCEHOST to the name (or the IP number) of the license server.
(Disable a Network License)
IAR Embedded Workbench will try to obtain a network license by communicating with a license server located somewhere on the same subnet. You can disable the network broadcast by setting LSFORCEHOST to NO-NET. With this setting, IAR Embedded Workbench only looks for a stand-alone license key.
(Set the Default Location of License Management Files) This variable can be used to set the default location of the license key and log files.
(Set Application License Management Options) This variable can be set to configure the application license management options in a way that is similar to its use on a server computer to configure a license server. (These options are often better set using a specific environment variable.)
(Set the IAR Embedded Workbench License Management Configuration File) This variable can be used to specify the configuration file that is used with the stand-alone IAR Embedded Workbench. (It is often enough to use the LSERVRC environment variable.)
All product names are trademarks or registered trademarks of their respective owners.