|
-a
|
Specifies the day the license expires (1 - 31).
|
|
-A
|
Specifies either network or standalone licensing:
> 0 = Network licensing
> 1 = Standalone licensing
>2 = Repository licensing
|
|
-B
|
Specifies the number of subnets used for site licensing. Long codes only.
|
|
-b
|
Specifies short numeric or long license code:
>1 = Long
>2 = Short, numeric
If you request a short, numeric code (value 2), you must follow that value with a colon and the number of the license model you want to use (example, -b 2:7).
>1 = 1-1461 day standalone (relative demo license)
>2 = 1-1461 day network (relative demo license)
>3 = Absolute standalone demo license
>4 = Absolute network demo license
>5 = Locked standalone demo license
>6 = Buy standalone product license
>7 = Buy network product license
>8 = Locked Network Demo
|
| -b_hr |
Specifies the license start hour (0 - 23) |
| -b_min
|
Specifies the license start minutes (0-59)
|
|
-c
|
Used to specify the type of locking desired:
> 0 = Server Locked
>1 = Client & Server Locked
>2 = Unlocked
>3 =Client Locked
|
|
-C
|
Used for client-locked applications to specify the locking code. Do not include spaces. The format is: -Cn<lock-selector>:<locking-code>.
For example, -C10x2:0x3455.
|
|
-cap
|
Specifies capacity.·
>0 - Capacity shall be From 1 through 1022, (Multiple of 1)
> 1 - Capacity shall be From 10 through 10220, (Multiple of 10)
> 2 - Capacity shall be From 100 through 102200, (Multiple of 100)
> 3 - Capacity shall be From 1000 through 1022000, (Multiple of 1000)
> 4 - Capacity shall be From 10000 through 10220000, (Multiple of 10000)
|
|
-cap_flag
|
Defines whether the license is a non-capacity or capacity
pooled or capacity non-pooled license.
Valid values are 0 or 1 or 2.
> 0 = Non-capacity
> 1 = Non-pooled capacity
>2 = Pooled capacity
|
|
-cap_units
|
Defines the capacity units. Valid values are 0, 1, 2, 3, and 4.
> If capacity_units is 0, capacity shall be From 1 through 1022, (Multiple of 1)
> If capacity_units is 1, capacity shall be From 10 through 10220, (Multiples of 10)
> If capacity_units is 2, capacity shall be From 100 through 102200, (Multiples of 100)
> If capacity_units is 3, capacity shall be From 1000 through 1022000, (Multiples of 1000)
> If capacity_units is 4, capacity shall be From 10000 through 10220000, (Multiples of 10000).
|
| -com_max_days |
Specify a value between 1 to 1827 days. |
|
-D
|
Specifies additive or aggregate or exclusive licenses.
> 0 = Additive license
>1 = Exclusive license
>2 = Aggregate license
|
| -d_hr
|
Specifies the license expiration hours (0 - 23).
|
| -d_min
|
Specifies the license expiration minutes (0-59)
|
|
-e
|
Name of the license configuration file.
|
|
-E
|
Specifies the feature name.
|
|
-enc
|
Specifies the log files encryption level for network licenses:
>0 = End-user defined. This level leaves the encryption choice up to your customer. The customer can then specify the encryption level using the -lfe License Manager startup option. (If you specify end-user defined encryption, and your customer chooses not to select an encryption level, Sentinel RMS uses no encryption; tag each record as the default encryption.) Note that the customer only defines the encryption level for license codes set to end-user defined encryption; end-user encryption is ignored for license codes set to other encryption levels by the developer.
>1 = No encryption. Transaction data will be logged for this license code with no encryption.
>2 = No encryption, tag each record. Transaction data will be readable by the customer, but tampering with or deleting an entry will be prevented.
>3 = Encrypt usage only. Transaction data will be readable by the customer except for license usage data (which will be encrypted), but tampering with or deleting an entry will be prevented.
>4 - Encrypt entire record. All transaction data for the license code will be encrypted. Tampering with or deleting an entry will not be prevented, but can be detected if the appropriate usage utility (lsusage or vusage) is run on the log file.
|
|
-F
|
Specifies the soft limit or no limit. NOLIMIT is a valid value.
|
|
-g
|
Specifies the location of an optional file containing global licensing options.
|
|
-G
|
Specifies the type of shared licenses.
> 0 = No sharing of license
> 1 = Username-based sharing
> 2 = Hostname-based sharing
>3 = x - display-based sharing
> 4 = Application-defined sharing
|
| -gp |
For specifying the grace period when an application is run in a disconnected network. Specify
>0 = For no grace period
>1 = For allowing grace period
|
| -gp_days |
Grace period in the number of days. A value between 1 to 180 days. |
| -gp_hours |
Grace period in the number of hours. A value between 1 to 1440 hours. |
|
-h
|
Specifies the type of held licenses.
>0 = Not allowed
>1 = Client application specifies hold time
> 2 = The licensing code specifies hold time
|
|
-H
|
Specifies the system attribute used for primary License Manager locking information. Applicable to non-redundant License Managers. The format is: H<lock-selector>:<locking code>.
|
|
-i
|
Lists any proprietary private vendor information. Long codes only.
|
|
-j
|
Specifies the license hold time, in units specified by -j.
|
|
-J
|
Specifies license holdtime units (1, 10, 30, or 60 minutes) used with -J < hold minutes> option.
>0 = Multiple of 1 minute(s), maximum 15 minutes
>1 = Multiple of 10 minute(s), maximum of 150 minutes
> 2 = Multiple of 30 minute(s), maximum of 450 minutes
> 3 = Multiple of 60 minute(s), maximum of 900 minutes
|
|
-k
|
Specifies license lifetime units (1, 10, 30, or 60 minutes)
used with -K <lifetime minutes> option.
>0 = Multiple of 1 minute(s), maximum 15 minutes
>1 = Multiple of 10 minute(s), maximum of 150 minutes
> 2 = Multiple of 30 minute(s), maximum of 450 minutes
>3 = Multiple of 60 minute(s), maximum of 900 minutes
|
|
-K
|
Specifies the license lifetime in units specified by -k. NOLIMIT is a valid value.
|
|
-ktype
|
Format is: -ktype <0> or -ktype <1>. 0 prompts for single-feature and 1 prompts for multi-feature. This option is normally used with the number of features switch.
|
|
-l
|
Used for server-locked applications, specifies the attribute used for locking. Secondary License Manager locking information. Applicable to non-redundant License Managers. The following format is used: -I<lock-selector>:<locking-code>.
|
|
-L
|
Specifies whether clients are locked to the same License Manager for client and server locked licenses (y, n).
|
| -lcl_req_lockcrit |
The lock criteria of the local system. The format is required:float:minimum.
For example, when 0x6:0x98:3 is set, it means that the IP address and disk ID locking criteria must be met. Out of host name, Ethernet address, and CID- any one must be met.
|
| -lic_vendor_info |
Specifies proprietary license vendor information. This information will remain encrypted in the license string. |
|
-m
|
Specifies the month the license expires (1 - 12 or Jan. - Dec).
|
|
-M
|
Repeats prompting. If set to Y then after generating the first license it prompts if you wish to generate more license but if set to N then it exits after generating the first license.
|
|
-maj
|
Majority rule. (Only for redundant License Managers.)If majority rule flag is set and majority of License Managers are not running, client request will not be served.
|
|
-n
|
Used to restrict the number of concurrent users. Specifies the number of licenses. NOLIMIT is a valid value.
|
|
-N
|
Used with client locking, this option provides the number of client nodes.
|
|
-n1:-n2:
|
Number of users for multi-features (-n1:5 = 5 users for feature 1, -n2:3 =3 users for feature 2 and so on).
|
|
-nfeat
|
Specifies the number of features for a multi feature license.
|
|
-nserv
|
Number of redundant License Managers. Maximum set of License Managers is 11.
|
|
-o
|
Name of the output file. By default, the code generator appends new license codes to the file. If the output file does not exist, it will be created. The location of the output file can also be specified by the environment variable, NEWCODES.
|
|
-O
|
Commuter License. Used to generate keys for the traveling clients. Commuter licensing allows end users to check out an authorization from a network served license pool and check it in when they are done. The value of the switch has to be given as either Y for commuter license or N for non-commuter license.
|
| -ovd
|
Not supported.
|
| -ovd_hours
|
Not supported.
|
| -ovd_users
|
Not supported.
|
|
-p
|
Specifies the number of licenses per node. NOLIMIT is a valid value.
|
|
-P
|
Specifies whether or not an application should run if time tampering is detected. 'Y' or 'N' has to be given as the value of the switch.
|
| -pub_vendor_info |
The proprietary public vendor information. This information will remain readable in the readable output license string. |
|
-Q
|
Specifies the sharing limit (1-254). NOLIMIT is a valid value.
|
|
-r
|
Specifies the number of challenge-response secrets. An additive security mechanism for the License Manager (challenge) and client (response). Maximum number of secrets is 7.
|
|
-Rn
|
Text of the secret(s). For example, -R2text.
|
|
-s
|
Name of the software license file.
|
|
-S
|
Specifies subnet information for the subnet(s) used for site licensing. Long codes only. Format is specified as following:-S<n> <subnet-info>.
For example, -S1 204.*.1.* -S2 205.*.1.*
|
|
-serv1: -serv2:
|
Locking information for redundant License Managers. Format is as specified in the following: -serv<n>:server<n>-lock-selector:server<n>-lock-code
|
|
-T
|
Specifies the day the license begins (1 - 31).
|
|
-U
|
Redundant Licenses.
|
|
-v
|
Specifies the feature version number. Long codes only.
|
|
-V
|
Specifies the month the license begins (1 - 12 or Jan. - Dec).
|
|
-ver
|
Selects the version of Sentinel RMS to create a license code. For example, -ver 5 causes a license code compatible with Sentinel RMS version 6.0 to be created. Valid arguments are:
>21 = Sentinel RMS Kit version 9.7.0
>20 = Sentinel RMS Kit version 9.5.0
>19 = Sentinel RMS Kit version 9.4.1
>18 = Sentinel RMS Kit version 9.2.x and 9.4.0
>17 = Sentinel RMS Kit version 9.1.x
>16 = Sentinel RMS Kit version 9.0.x
>15 = Sentinel RMS Kit version 8.6.0
>14 = Sentinel RMS Kit version 8.5.0
>13 = Sentinel RMS Kit version 8.4.0
>12 = Sentinel RMS Kit version 8.2.3
> 11 = Sentinel RMS Kit version 8.1.0
> 10 = Sentinel RMS version 8.0.0
> 9 = Sentinel RMS version 7.3.0.x
> 8 = Sentinel RMS version 7.3.0
>7 = Sentinel RMS version 6.3 - 7.2
> 6 = Sentinel RMS versions 6.1 and 6.2
>5 = Sentinel RMS versions 6.0.x
If omitted, a license code with current code generator version will be created.
|
| -vm |
Specifies the VM detection flag in the license generated.
|
|
-w
|
Specifies the license model:
> 0 = Encrypted
>1 = Expanded readable
> 2 = Concise readable
|
|
-W
|
Specifies life in days of license relative to date of license installation. The format is <Days:Hours>
|
|
-y
|
Specifies the year the license expires (2006 - 2133). NEVER is a valid value.
If you use the -b <license code> option and the -y<expiration> option, you must also specify a quarter in which the license will expire. For example:· 1 = March 31· 2 = June 30· 3 = September 30· 4 = December 31
|
|
-Y
|
Specifies the year the license begins (2006 - 2133).
|
