Manually Editing the Reservation File

You can also edit the reservation file manually, as shown below:

featurename,[version],capacity of license:flag:team group name:tokens reserved for teamgroup:capacity reserved:teams included
featurename,[version],capacity of license:flag:user groupname:team:sharing tokens reserved:capacity reserved:users included

A group specification consists of:

>The name of the feature for which the reservation applies.

>The name of the group.

>The number of license tokens reserved for that group.

>The user names, host IDs, IP addresses (IPv4 and IPv6) of computers that belong to that group that will included or excluded from using the feature.

>The characters $ and ! have special meaning: $ indicates the computer name, and ! indicates a logical NOT. Also, to include a single special percent (%) character in the group member in the group reservation file, specify it twice and so on. See examples in the table below:

Username Set	Resultant Username
user%%ABC	user%ABC
user%%%%1	user%%1
user%ABC	userABC

Group reservations should be entered according to the following format, with one group per line:

NOTE   The first expression (either include or exclude) used in the line always has the highest priority.

feature_name[ ,ver ]:group_name:num_of_licenses:{ user_name | computer }

One or more of user_name and/or computer may be specified, but at least one value must be specified in the last field. Version number is optional. If no version number is specified, only the feature name is used.

For example, two users, one computer in group 1:

	stars:group1:2:tom bryant $athena

 

One user, one computer in group 2:

	stars:group2:1:doug $0x4f3c5801

 

One computer to be excluded from dots, two licenses to be reserved for jill:

	dots:group1:2:!$0x592ae8b0 jill

NOTE   In these examples, the two groups denoted as group1 are distinct because they specify different feature names.

NOTE   If an entity is excluded from the reservation file, then it cannot access that feature at all.

Example 1: Let us assume that there is a license F1V1 having 10 tokens. If User 1 is excluded from being allocated 2 out of 10 tokens, then all other users can get maximum of 8 tokens. User 1 will not be eligible to receive any token.

Example 2:Let us assume that there is a license F1V1 having 10 tokens. If 3 out of 10 tokens are reserved for User 1, then maximum 7 tokens can be allocated to all other users. However, User 1 will still be eligible to receive 10 tokens.

The flag value can be:

>0 - Specifies capacity reservations for teams

>1 - Specifies capacity reservations for users/hosts

>2 - Specifies capacity reservations for non-shared capacity licenses

Taking into example a Pooled capacity license with capacity 3000, hard limit 4 and sharing limit 5 then the following file

f1,v1,3000:0:TG1:2:1000:team1 team2 team3

f1,v2,3000:1:UG1:team1:3:500:user1 user2

will reserve 2 tokens(out of 4) and 1000 capacity for team group TG1 consisting of team1,team2,team3. Among the users of team1, 3 sharing tokens (out of 5) and 500 capacity are reserved for user1 and user2 .