MAX
This option applies to concurrent licenses held in license files and trusted storage.
MAX num_lic feature[:keyword=value] type {name | group_name}
Limits usage for a group or user.
Term |
Description |
num_lic |
Usage limit for this user or group. |
feature |
Feature or package this limit applies to. |
keyword=value |
Feature name modifier to denote a group of licenses. See Specifying Features for details. |
type |
One of USER, HOST, DISPLAY, INTERNET, PROJECT, GROUP, or HOST_GROUP. See Specifying License Restrictions Using Type for details. |
name |
Name of an item of type type for which usage is limited. To avoid having to repeat the MAX line multiple times to restrict all users, you can use one MAX line that specifies ALL_USERS as the value for the type USER (for example, USER ALL_USERS). See for USER and GROUP Examples more information. |
group_name |
Name of the group to limit. Group names are case sensitive. (The options file must include a GROUP line that defines this group.) To avoid having to repeat the MAX line multiple times to restrict all groups defined in the options file, you can use one MAX line that specifies ALL_GROUPS as the value for the type GROUP (for example, GROUP ALL_GROUPS). See USER and GROUP Examples for more information. |
The following are examples of using the USER and GROUP types for the MAX option.
Note:Never position a MAX line that restricts USER user_name for a specific feature after a MAX line that restricts USER ALL_USERS for the same feature. Likewise, never position a MAX line that restricts GROUP group_name for a specific feature after a MAX line that restricts GROUP ALL_GROUPS for the same feature. The positioning invalidates the restriction in the later line.
• | To limit the user jan to five licenses for feature f1, include the following line in the options file: |
MAX 5 f1 USER jan
• | To limit all users to to five licenses for feature f1, include the following line: |
MAX 5 f1 USER ALL_USERS
• | To limit the user jan to five licenses for feature f1 and all other users to four licenses for the same feature, include the following lines: |
MAX 5 f1 USER jan
MAX 4 f1 USER ALL_USERS
• | To limit group DEV to three license for feature f2 and all other groups to one license for the same feature, include these lines: |
MAX 3 f2 GROUP DEV
MAX 1 f2 GROUP ALL_GROUPS
• | If you attempt to position a MAX line that specifies ALL_USERS (or ALL_GROUPS) before a MAX line that specifies a single user (or single group), FlexNet Publisher cannot enforce the restriction in the second line because the user or group in the second line (in this case, the DEV group) is a part of ALL_USERS or ALL_GROUPS in the first line. |
For example, the following line positioning is invalid:
MAX 1 f2 GROUP ALL_GROUPS
MAX 3 f2 GROUP DEV
Queueing Behavior When Requested Licenses Exceed MAX Limit
For current version vendor daemons, if queueing is allowed by the application, requests for licenses that exceed the limit set by the MAX keyword will be denied. From the above example, if the user jan requests six licenses for feature f1, the request will be denied. Requests from users or groups within the MAX limit that exceed the number of available licenses will be queued. For example, if the license file includes ten licenses for feature f1 and nine of those licenses are already checked out, a request from the user jan for two licenses will be queued.