Specifications

Setting User Alerts
110
Chapter 6 - Setting User Options
• License returned
• License denied (occurs on the next request after the hard limit has been
reached)
• License time-out
• License expiration date reached
The alert reporting mechanisms are:
• E-mail
• Script
Alert Specification
To enable alerts, you need a configuration file with information on the license
codes in the license code file.
Configuration information can be readable license remap statements, alert action
statements, etc. The license server is the only entity that deals with alerts. The
configuration file is read by the license server and lsdecode, which ignore state-
ments in the configuration file that they are not interested in. If the configuration
file does not exist, no alerts will be reported. The file can contain the information
on what to do with the alerts. If the configuration file is changed while the
license server is running, the license server will need to be restarted in order for
the changes to take effect.
The configuration file, lservrc.cnf, is a general-purpose configuration file associ-
ated with a particular license file. The environment variable LSERVRCCNF can
specify the path to the configuration file. The path for <LicenseFile>.cnf is con-
structed from the license file path the user is using. LicenseFile can be specified
using existing methods such as the license server startup -s option, or the
LSERVRC environment variable. It is not an error for the configuration file to be
missing.