Platform LSF Reference Version 6.2

ProjectGroup Section
Platform LSF Reference
594
SHARES
Required. Defines the shares assigned to the hierarchical group member projects.
Specify the share for each member, separated by spaces, in the same order as listed in
the GROUP column.
OWNERSHIP
Defines the level of ownership of the hierarchical group member projects. Specify the
ownership for each member, separated by spaces, in the same order as listed in the
GROUP column.
You can only define OWNERSHIP for hierarchical group member projects, not
hierarchical groups. Do not define a number for the top level project group.
A dash (
-) is equivalent to a zero, which means there are no owners of the projects. You
can leave the parentheses empty
() if desired.
Valid values
A positive integer between the NON_SHARED and LIMITS values defined for the
specified hierarchical group.
If defined as less than NON_SHARED, OWNERSHIP is set to NON_SHARED.
If defined as greater than LIMITS, OWNERSHIP is set to LIMITS.
LIMITS
Defines the maximum number of licenses that can be used at any one time by the
hierarchical group member projects. Specify the maximum number of licenses for each
member, separated by spaces, in the same order as listed in the GROUP column.
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
To correct configuration is: