Platform LSF Reference Version 6.2

Feature Section
Platform LSF Reference
586
FLEX_NAME allows the NAME parameter to be an alias of the FLEXnet feature
name. For feature names that start with a number or contain a dash (-), you must set both
NAME and FLEX_NAME, where FLEX_NAME is the actual FLEXnet Licensing
feature name, and NAME is an arbitrary license token name you choose.
For example
Begin Feature
FLEX_NAME=201-AppZ
NAME=AppZ201
DISTRIBUTION=LanServer1(Lp1 1 Lp2 1)
End Feature
DISTRIBUTION
Syntax
DISTRIBUTION=
[service_domain_name([project_name
number_shares[
/number_licenses_owned]] ... [default] )] ...
◆ service_domain_name
Specify a License Scheduler service domain (described in the “ServiceDomain
Section” on page 583) that distributes the licenses.
◆ project_name
Specify a License Scheduler project (described in the “Projects Section” on
page 596) that is allowed to use the licenses.
◆ number_shares
Specify a positive integer representing the number of shares assigned to the project.
The number of shares assigned to a project is only meaningful when you compare
it to the number assigned to other projects, or to the total number assigned by the
service domain. The total number of shares is the sum of the shares assigned to each
project.
◆ number_licenses_owned
Optional. Specify a slash (
/) and a positive integer representing the number of
licenses that the project owns.
◆ default
A reserved keyword that represents the default License Scheduler project if the job
submission does not specify a project (
bsub -Lp).
Description
Required if GROUP_DISTRIBUTION is not defined. Defines the distribution policies
for the license. The name of each service domain is followed by its distribution policy,
in parentheses. The distribution policy determines how the licenses available in each
service domain are distributed among the clients.
The distribution policy is a space-separated list with each project name followed by its
share assignment. The share assignment determines what fraction of available licenses
is assigned to each project, in the event of competition between projects. Optionally, the
share assignment is followed by a slash and the number of licenses owned by that
project. License ownership enables a preemption policy. (In the event of competition
between projects, projects that own licenses preempt jobs. Licenses are returned to the
owner immediately.)