LSF Version 7.3 - Platform LSF Configuration Reference

A dash (-) is equivalent to INFINIT_INT, which means there is no maximum limit and the
project group can use as many licenses as possible.
You can leave the parentheses empty () if desired.
NON_SHARED
Defines the number of licenses that the hierarchical group member projects use exclusively.
Specify the number of licenses for each group or project, separated by spaces, in the same order
as listed in the GROUP column.
A dash (-) is equivalent to a zero, which means there are no licenses that the hierarchical group
member projects use exclusively.
Normally, the total number of non-shared licenses should be less than the total number of
license tokens available. License tokens may not be available to project groups if the total non-
shared licenses for all groups is greater than the number of shared tokens available.
For example, feature p4_4 is configured as follows, with a total of 4 tokens:
Begin Feature NAME =p4_4 # total token value is 4 GROUP_DISTRIBUTION=final
SERVICE_DOMAINS=LanServer End Feature
The correct configuration is:
GROUP SHARES OWNERSHIP LIMITS NON_SHARED
(final (G2 G1)) (1 1) () () (2 0)
(G1 (AP2 AP1)) (1 1) () () (1 1)
Valid values
Any positive integer up to the LIMITS value defined for the specified hierarchical group.
If defined as greater than LIMITS, NON_SHARED is set to LIMITS.
PRIORITY
Optional. Defines the priority assigned to the hierarchical group member projects. Specify the
priority for each member, separated by spaces, in the same order as listed in the GROUP
column.
“0” is the lowest priority, and a higher number specifies a higher priority. This column
overrides the default behavior. Instead of preempting based on the accumulated inuse usage
of each project, the projects are preempted according to the specified priority from lowest to
highest.
By default, priorities are evaluated top down in the project group hierarchy. The priority of a
given node is first decided by the priority of the parent groups. When two nodes have the same
priority, priority is determined by the accumulated inuse usage of each project at the time the
priorities are evaluated. Specify LS_PREEMPT_PEER=Y in the Parametersr section to enable
bottom-up license token preemption in hierarchical project group configuration.
A dash (-) is equivalent to a zero, which means there is no priority for the project. You can
leave the parentheses empty () if desired.
Use blinfo -G to view hierarchical project group priority information.
Priority of default project
If not explicitly configured, the default project has the priority of 0. You can override this value
by explicitly configuring the default project in Projects section with the chosen priority value.
lsf.licensescheduler
Platform LSF Configuration Reference 525