Q100031: RLM and FLEXlm license syntax



RLM and FLEXlm licenses contain readable text that describes many useful details about the license.  Understanding RLM and FLEXlm license syntax can help avoid confusion and catch problems early.


The remainder of this article will provide a brief explanation of licenses to help you better understand the license syntax. Note collectives not addressed in this article.

First, two example NODE LOCKED licenses (FLOATING discussed at the end):

LICENSE foundry hiero_i 2014.0122 22-jan-2014 uncounted
hostid=0090f5df5600 share=h min_timeout=30 start=3-jun-2013
issuer=sf issued=3-jun-2013 _ck=5ecf71bc90 sig="60PG4580HDBXRTE22HJ

INCREMENT furnace_fxplug_i foundry 4.1 permanent uncounted \
HOSTID=406c8fb8bb2d ISSUER=sf ISSUED=30-may-2013 \
START=30-may-2013 TS_OK SIGN="038D AE7B 8F5F B511 DA50 77C1 \
B985 3504 57E0 9638 2403 7D11 8F9C CE42 B551 482F CD38 D7E2 \
8AC7 994B 441A"

1. Two license types (separate 3rd party vendors), very similar in construct and function: RLM and FLEXlm; different Foundry products on each, none on both; see
"What are RLM and FLEXIm licenses?"

2. first word in license block:
FLEXlm licenses have "INCREMENT"

3. both have 'hostid' or 'HOSTID' literally shown and also encrypted into the key string which is the same as system ID which is one of the hardware ethernet addresses on the machine to which the license is locked; a 12-character hex string always, supposedly unique - and it has to be, among all machines appearing on the same network (else ethernet doesn't work)

4. second & third words in license block (in RLM & FLEXLM order is swapped):

'foundry' refers to a specific piece of software in our apps and also license managers, that holds the means to unlock/validate the keys; All our licenses need to refer to this 'foundry' thing

the feature name, a.k.a the product; e.g.
nuke_i is a Nuke Interactive (GUI) license
hiero_i is a Hiero Interactive (GUI) license

5. fourth word in a license block:
version limiter - you can't run the app if the version is later than this; syntax is
but you'll notice that we can use
and instead of the app looking for a version major.minor ref, it looks at a build date.
In other words, in the date form, you cannot run a version of the app if it was built after the version-limiting-date that you see in the license.

6. fifth word in a license block:
expiration date;
or the word 'permanent'

7. sixth word in a license block:
number of licenses provided on that system ID;
'uncounted' appears when the license is locked to one machine, AND the license is not a floating license (i.e. node-locked);
Note: when the string
appears in the block, it is always a node-locked license, never floating.

8. Floating licenses have some slight differences.
(a) 2 extra lines at the top of the file;
(b) no "HOSTID" or "hostid" appears within the individual license block - but rather it appears ONCE only and in the first line of the floating license.

Here are examples of RLM and FLEXlm floating licenses, respectively:

HOST 000c29322964 4101
ISV foundry
LICENSE foundry rlm_server_enable_vm 1.0 31-jan-2014 1 share=h
min_timeout=30 start=22-jan-2013 issuer=support issued=22-jan-2013
replace _ck=9dd6f49f70 sig="60Q04580N5XWFEV87KWHG3869F86RXNV31NE0J9

SERVER 109addb68dc8
VENDOR foundry
INCREMENT nuke_i foundry 2014.0409 permanent 1 SUPERSEDE ISSUER=sf \
ISSUED=27-mar-2013 START=27-mar-2013 TS_OK SIGN="0349 D352 \
D5B4 EDAA 7D24 1D58 E4D2 7A33 9816 00B7 A302 E492 F200 21D3 \
3F35 4411 963E 6BF6 392E D5F9 BE61

Was this article helpful?
0 out of 0 found this helpful