Publisher-Defined Required Keywords

The six fields after the feature definition line keyword are required and have a fixed order. They are defined by the software publisher and cannot be changed. The following table presents these fields in the order they must appear.

Feature Definition Line Required Fields

Field

Description

feature

Name given to the feature by the software publisher.

vendor

Name of the vendor daemon; also found in the VENDOR line. The specified daemon serves this feature.

feat_version

Version of this feature that is supported by this license.

When this field contains a date with the format yyyy.mmdd, this defines a date-based version that you can set as an Alert in the license server manager, lmadmin. In this case, mmdd must be in the range 101 to 1231 and valid (for example, 2020.1131 is not a valid date). For dd, both digits must be specified (for example, 2020.111 means January 11, 2020).

exp_date

Expiration date of license in the format dd-mmm-yyyy, for example, 31-dec-2020.

Note:If exp_date is the string “permanent” or the year is 0 (or 00, 000, 0000) then the license never expires.

num_lic

Number of concurrent licenses for this feature. If the num_lic is set to the string “uncounted” or 0, the licenses for this feature are uncounted and no license server is required but a hostid on the FEATURE line is required. See Counted vs. Uncounted Licenses.

SIGN=sign or

AUTH=...

SIGN= signature to authenticate this FEATURE line.

If your publisher has deployed his vendor daemon using the common vendor daemon technology, signatures are embedded within the AUTH= keyword. Contact your publisher for further details.