2.3 Product permits

2.3.1 Policies

Each product permit has a number of settings that determine how the product can be used. Generally the policy setting can be adjusted by your systems administrator using the administration tool hqn_lsa. See Chapter 3, The License Server Administration Tool, for details of how to change policies. However, if required, Harlequin can lock one or more policy flags into the permit.

The policy value in a permit is a set of bit flags which, if set, turn on the policies shown in Table 2.1. Note that hqn_lsa never changes the permit files themselves; it only configures an active hqn_lsd daemon. Current policies are as follows for the 'on' setting.

Bit Policy Description
0 GRAB Licenses not updated within 'crashout' time period are freed on next request (the default setting). Thus licenses held by applications that have crashed will be made available. This policy is on by default.
1 ONPN Only 1 floating license is allowed per machine. For locked nodes only one license is allowed per listed machine -- the same machine may be listed more than once to allow up to a maximum number of products instances to run on a single specified machine.
2 TIML Licenses may only be held continuously for some maximum time period (timeout) after which the license may be given up to another user if no free licenses are available.
3 LKNL As for TIML but the time limit does not apply to locked nodes.
4 LKNF Node-locked machines are not allowed to also hold floating licenses.
5 LKPR Users on node-locked machines have priority over users on other machines. That is, if no licenses are available the oldest floating license not running on a locked-node will be reallocated.
6 UVIS The application is allowed to request a list of current users of that product so that users can see where licenses are allocated.
7 USRL The system administrator can allocate guaranteed licenses for particular users. If no licenses are available the oldest current license is reallocated to the privileged user.
8 ACCL Your system administrator can assign an access level to groups and/or particular users. Generally full access is assigned unless the current user or their current group has a lower access level assigned. Access levels are in the range 0 to 8, where 8 is full access, 1 is minimum access, and 0 denies all access to the software, that is, no license is issued.

Bit	Policy	Description
0	GRAB	Licenses not updated within 'crashout' time period are freed on next request (the default setting). Thus licenses held by applications that have crashed will be made available. This policy is on by default.
1	ONPN	Only 1 floating license is allowed per machine. For locked nodes only one license is allowed per listed machine -- the same machine may be listed more than once to allow up to a maximum number of products instances to run on a single specified machine.
2	TIML	Licenses may only be held continuously for some maximum time period (timeout) after which the license may be given up to another user if no free licenses are available.
3	LKNL	As for TIML but the time limit does not apply to locked nodes.
4	LKNF	Node-locked machines are not allowed to also hold floating licenses.
5	LKPR	Users on node-locked machines have priority over users on other machines. That is, if no licenses are available the oldest floating license not running on a locked-node will be reallocated.
6	UVIS	The application is allowed to request a list of current users of that product so that users can see where licenses are allocated.
7	USRL	The system administrator can allocate guaranteed licenses for particular users. If no licenses are available the oldest current license is reallocated to the privileged user.
8	ACCL	Your system administrator can assign an access level to groups and/or particular users. Generally full access is assigned unless the current user or their current group has a lower access level assigned. Access levels are in the range 0 to 8, where 8 is full access, 1 is minimum access, and 0 denies all access to the software, that is, no license is issued.

In addition to tailoring the licensing policy of a product to your site, hqn_lsa can also be used to convert floating licenses to node-locked licenses (and vice versa but only if the license has been previously converted), add to the list of node-locked hosts, and exclude certain hosts from running the product at all.

MLWorks Guide to the License Server - 17 JAN 1997

Generated with Harlequin WebMaker