The VMS version of FLEXlm does not use lmgrd, so clients connect directly with the vendor daemons. This implies that each vendor daemon is started independently in the system startup command file. The command line for starting a daemon is:

daemon_name [-c license_file_path] [-l log_file_path]

The default license file on VMS is SYS$COMMON:[SYSMGR]flexlm.dat. You can set a new default in the vendor daemon by editing ls_vendor.c and changing the value of the (char *) variable default_license_file to be the pathname you wish for the default license file for your daemon. The end-user's license administrator can still override this setting with either the “-c” command-line option, and the end-user can set their LM_LICENSE_FILE environment variable.

---

Note: On VMS, the SYSNAM and SYSLCK privileges are required to run the daemons.

---

lmgrd can be started as an application from the Windows NT console with the –app option. For example:

D:\flexlm> lmgrd -app -c my_lic.dat

Alternatively, lmgrd can be installed as a service on a Windows NT system so that it can be managed from the control panel on NT. To install lmgrd as a service, use the INSTALL.EXE command provided by FLEXlm. For example:

D:\flexlm> install d:\flexlm\lmgrd.exe

Note that the full pathname to lmgrd.exe must follow the install command. You must also make sure that the full path name including drive letter for your vendor daemon is specified correctly in your license file, c:\flexlm\license.dat. FLEXlm Windows NT DLL, lmgr32.dll, must also be in the system's DLL search path.

After INSTALL.EXE is run successfully, lmgrd is installed as a Windows NT service and will be started automatically each time your system is booted. To start lmgrd right after running INSTALL.EXE without rebooting your system, you may use the Service Icon from the Windows NT control panel. Look for FLEXlm Licensing Service from the dialogue box after you double click on the Service icon.

To remove lmgrd from the registered service list, simple type install remove. If you wish to customize the INSTALL program, the source code and makefile for INSTALL.EXE is included in the UTILS directory.

When lmgrd.exe is installed as a service on your system, you may use the following procedure to set the license file path for lmgrd by updating the system registry:

The startup arguments for vendor daemons changed between FLEXlm v1.x and v2.0. If you are running a configuration with a mixture of v1.x and v2.x vendor daemons, then you will need to use the –b option (Note: this is the default in FLEXlm v3.0).

If the “-2 -p” startup argument is used to lmgrd, then the user who issues an lmdown, lmreread, or lmremove command must be a “license administrator”. A license administrator is:

To start the license finder, execute the following command on the node flexlm_license_finder (and optionally flexlm_license_finder2 and flexlm_license_finder3):

lmgrd -f finder_file

lmgrd, when it is operating as a license finder (“-f finder_file” option), will ONLY processes the finder-specific messages, and sends the license file path back to the client. This lmgrd will NOT start any vendor daemons or process any other client request. This functionality is delivered in lmgrd so that you do not have to ship a separate executable.

The “finder file” format is:

DATA lfpath license_file_path1[:license_file_path2]

for example:

DATA lfpath /usr/local/flexlm/licenses/license.dat:1234@host2

---

Note: This format will be extended in a later release of FLEXlm to allow specification of paths that are specific to particular users, hosts, displays, and vendors.

---

---

Note: The license finder is not available on VMS systems.

---

To insert your vendor daemon name, the lmrandom program takes the built-in vendor_name variable from lm_code.h and creates 10 single char variables with each character of your vendor name. Your daemon name no longer appears in the vendor daemon as a character string (from FLEXlm v2.4 on) until the daemon is running.

---

Note: In place of the lockfile used on UNIX systems, VMS daemons set the process name to: <daemon name>_FLEXlm” (truncated to 15 characters). This means that the daemon name must not contain any characters that are illegal in a VMS process name. This restriction will be removed in a future version of FLEXlm, as FLEXlm is migrated to use the VMS lock manager in place of the process name.

---

This variable is set to the pathname of the (new) default license file, if the software vendor desires to override the FLEXlm default of:

SYS$COMMON:[SYSMGR]FLEXLM.DAT.

int ls_compare_vendor_on_increment = 0; /* Compare vendor-defined */

INCREMENT lines are combined if the following is true:

ls_compare_vendor_on_increment gives you control whether an INCREMENT line will require the vendor string to match in order to pool its licenses. If set to a non-zero value, then the vendor string must match; if 0, then no comparison is done on the vendor string.

int ls_compare_vendor_on_upgrade = 0; /* Compare vendor-def fields */

Prior to FLEXlm v3.0, UPGRADE lines were assigned to a FEATURE/INCREMENT line if the following was true:

ls_compare_vendor_on_upgrade gives you control whether an UPGRADE line will require the vendor string to match in order to upgrade another license. If set to a non-zero value, then the vendor string must match; if 0, then no comparison is done on the vendor string.

int ls_conn_timeout = MASTER_WAIT; /* How long to wait for a connection */

ls_conn_timeout is the amount of time (in seconds) that vendor daemons will wait for connections from vendor daemons on other nodes when using redundant servers. It should normally not be changed. This parameter has no effect on VMS versions of FLEXlm.

int ls_crypt_case_sensitive = 0; /* Is license key case-sensitive? */

If you have written your own encryption routine, and the output code from it is case-sensitive, set ls_crypt_case_sensitive to a non-zero value.

void (*ls_daemon_periodic)() = 0; /* Vendor-defined periodic call in daemon */

If you set the function pointer “ls_daemon_periodic” in ls_vendor.c to one of your functions, this function will be called approximately once per minute in the vendor daemon's main processing loop. You must insure that the .o file for this routine specified in ls_vendor.c is linked into your vendor daemon.

int ls_do_checkroot = 0; /* Perform check that we are running on the real root */

To require that your vendor daemon be running on a filesystem which has its root directory as the “real” root directory of the disk, set this option. This prevents an end-user from cloning part of the UNIX file hierarchy and executing the daemon with a chroot command. If this were done, the vendor daemon locking would be bypassed and the user could run as many copies of your vendor daemon as he desired.

Theft by using chroot is considered to be an obscure, difficult kind of theft. The user has to have root permission, and setting up a phony / directory is a non-trivial task. It requires that the necessary parts of the OS from /etc, /dev, /bin, etc. be copied into this phony / directory, and is an ongoing administrative hassle.

---

Note: The check performed by ls_do_checkroot will FAIL on a diskless node. This prevents diskless nodes from acting as license servers. Globetrotter Software does NOT recommend running license daemons on diskless nodes, but if you choose to support this, you will need to set ls_do_checkroot to 0. For complete security, set ls_do_checkroot to 1. For minimization of confusion and support calls when your customers are running on diskless nodes, set ls_do_checkroot to 0.

---

int ls_dump_send_data = 0; /* Set to non-zero value for debug output */

This variable controls the debug output of transmitted daemon data. It should normally be left set to 0.

int ls_enforce_startdate = 1; /* Enforce start date in features */

To use the start date present in the feature line, set ls_enforce_startdate to a non-zero value.

int (*ls_infilter)() = 0;

To install a vendor-defined checkin filtering routine, initialize ls_infilter with a pointer to your routine. The checkin filter is called with no parameters. If it returns 0, the current checkin is aborted; a return of 1 allows the current checkin to continue. If the filter aborts the operation (returns 0), then it should set the error code, lc_get_errno(), appropriately.

To obtain the parameters of the current checkin call, use the ls_get_attr() call described in “Vendor daemon Support Routines”.

int (*ls_incallback)() = 0;

To install a vendor-defined checkin callback routine, initialize ls_incallback with a pointer to your routine. The checkin callback is called with no parameters, and the return value is unused. The checkin callback routine is called after the checkin is performed.

To obtain the parameters of the current checkin call, use the ls_get_attr() call described in “Vendor daemon Support Routines”.

int ls_min_lmremove = 120; /* Minimum amount of time (seconds) that a...

The lmremove utility could be used to bypass the license count for a feature if an end-user were to run lmremove on each user as soon as he had checked out a license. ls_min_lmremove makes the lmremove utility ineffective for a certain period of time after a user connects to the daemon (120 seconds by default).

int ls_minimum_user_timeout = 900; /* Minimum user inactivity timeout (seconds)

This is the minimum value (in seconds) that an end-user can set the feature's TIMEOUT value. An attempt to set a timeout less than ls_minimum_timeout will result in the minimum value being set. If ls_minimum_user_timeout is set to 0, then the user TIMEOUT option is disabled.

int ls_read_wait = 10; /* How long to wait for solicited reads */

This variable controls how long the vendor daemon will wait for a connection to be completed with another vendor daemon. The default is 10 seconds. If your daemon supports a large number of features, you may need to increase this value, since the remote daemon's feature initialization can happen during this timeout interval.

int (*ls_outfilter)() = 0;

To install a vendor-defined checkout filtering routine, initialize ls_outfilter with a pointer to your routine. The checkout filter is called with no parameters. If it returns 0, the current checkout is aborted; a return of 1 allows the current checkout to continue.

If the filter aborts the operation (returns 0), then it should set the error code appropriately with lc_set_errno(). The general-purpose error code LM_CHECKOUTFILTERED is used for checkout requests that are filtered, if no other FLEXlm error is appropriate.

To obtain the parameters of the current checkout call, use the ls_get_attr() call described in “Vendor daemon Support Routines”.

int ls_show_vendor_def = 0; /* If non-zero, the vendor daemon will send...

FLEXlm v2.4 allows your client to send a vendor-defined checkout string to the daemon on each checkout request. If ls_show_vendor_def is non-zero, this data will appear in lc_userlist() calls, and hence, in lmstat output. If you use this vendor-defined checkout data and wish for your users to be able to view it with lmstat, then set ls_show_vendor_def to 1.

int ls_tell_startdate = 1; /* Tell the user if it is earlier than start date */

To inform the user that a feature's start date is later than the system date, set ls_tell_startdate to a non-zero value. If ls_tell_startdate is 0, then the feature will not be enabled in the daemon, and no warning message will appear in the log file.

int ls_use_featset = 0; /* Use the FEATURESET line from the license file */

To require the FEATURESET line in the license file, set ls_use_featset to a non-zero value.

int ls_use_all_feature_lines = 0; /* Use ALL copies of feature lines that are...

Globetrotter Software discourages your use of this option, which has been made unnecessary and obsolete by the new INCREMENT and UPGRADE features. The ls_use_all_feature_lines option will cause your vendor daemon to process every FEATURE line in the license file as INCREMENT lines.

With ls_use_all_feature_lines set to a non-zero value, any old feature lines which you may have shipped will now be “legal”, so, for example, if you had shipped a customer a feature line with a count of 5, then upgraded them with a new line with a count of 7, they would now be able to use 12 licenses.

Some restriction on INCREMENT lines existed for FLEXlm v2.61. These restrictions are removed in FLEXlm v3.0.

void (*ls_user_init1)() = 0;

To install an initialization routine that runs before normal vendor daemon initialization, initialize ls_user_init1 with a pointer to your routine.

void (*ls_user_init2)() = 0;

To install an initialization routine that runs after normal vendor daemon initialization, initialize ls_user_init2 with a pointer to your routine and make sure an object file with this function is linked with your vendor daemon.

char *(*ls_vendor_msg)() = 0;

To add support for sending messages from your client code to the daemon (with lc_vsend()), initialize ls_vendor_msg with a pointer to your routine which will process the message and create the reply for the client. ls_vendor_msg() is called with a single parameter—the character string sent by the client. It should create a reply message and return a pointer to it. The message string will be unused the next time that ls_vendor_msg() is called, so the use of a single static char array in ls_vendor_msg() is appropriate. Make sure this an object file with this routine is linked with your vendor daemon.

char *(*ls_user_crypt)() = 0;

To use your own encryption routine, initialize ls_user_crypt with a pointer to your routine, and make sure an object file with this routine is linked with your vendor daemon.

char *user_lockfile = (char *)NULL;

The vendor daemons use a lock file to prevent multiple copies from running on a server host. By default, this lock file is named /usr/tmp/lockDAEMON, where DAEMON is the name from the DAEMON line. On some new systems, the default is /usr/tmp/.flexlm/.lockDAEMON. If user_lockfile is NULL, or points to a null string, the default lock file will be used.

In FLEXlm v3.0, the date on the lock file is updated every 6 hours to make it less likely for cron jobs to remove it.

If you wish to change the location of the lock file, set user_lockfile to the new location. Be sure to use a full pathname for this file (i.e. the pathname should start with “/”) otherwise, multiple vendor daemons could be run from different directories.

VENDORCODE vendorkeys[] =.....

Example from lm_code.h:

/*
* VENDOR's private encryption seed — must be changed by user
* vendor should make up unique 32-bit hex numbers.
*/ 
#define ENCRYPTION_CODE_1 0x87654321
#define ENCRYPTION_CODE_2 0x12345678
/*
 *      FLEXlm vendor keys
 */ 
#define VENDOR_KEY1 0xe7503c03
#define VENDOR_KEY2 0x75811bed
#define VENDOR_KEY3 0xb8ea89c8
#define VENDOR_KEY4 0xc9a1b6d3
#define VENDOR_KEY5 0xc5dda903

The ENCRYPTION_CODEs are to be made up by the FLEXlm developer; the VENDOR_KEYS are supplied by Globetrotter Software when you purchase or upgrade FLEXlm.

CONFIG_DAEMON edits lm_code.h (or you can edit it manually) with the encryption seeds and vendor keys that you specified for your daemon. When your vendor daemon comes up, it checks all feature lines that specify its daemon name. If the license key in the license file is valid for any feature lines that the daemon checks, and the hostid is correct, then the vendor daemon sets the number of licenses to the value in the license file. All components of FLEXlm must share the same lm_code.h, where the VENDORCODE is specified. This encryption seed is the unique part of your daemon, so it is wise to

Each entry in the VENDORCODE array consist of a pair of 32-bit vendor-defined encryption seed values and a set of five 32-bit Globetrotter Software supplied FLEXlm Vendor Keys. The two 32-bit vendor-defined encryption seeds should be set to any values that do not contain long strings of either 0 or 1 bits (e.g. do not use 0x5 or 0xffffff3f). The FLEXlm Vendor Keys supplied by Globetrotter Software enable various portions of the FLEXlm software to run. Both the first set of vendor-defined encryption seeds and the FLEXlm Vendor Keys will be defined in the include file lm_code.h by CONFIG_DAEMON.

---

Note: The encryption seeds that you use in your lc_init() call must be the same as the first set of encryption seeds in the vendorkeys array. Otherwise, a “Bad encryption handshake with daemon” error will result from a checkout request.

---

---

Note: Only the two encryption seeds, which you the vendor define, affect the licenses you create. The FLEXlm vendor keys have no effect on the license files you create.

---

% cd /usr/license/lmgr

(run CONFIG_DAEMON to edit ls_vendor.c and lm_code.h as above).

% make

Create a binary kit as described in Chapter 2, “Installing the Distribution Kit” then follow the directions for the binary kit.

If you have added initialization or callback routines, you can add the XTRAOBJS macro to your make, e.g.:

make XTRAOBJS="xxx.o yyy.o zzz.o"

where xxx.o, yyy.o, and zzz.o are the object files for your additional routines. Alternately, you could modify the makefile to specify these objects.