LSF Version 7.3 - Platform LSF Configuration Reference

FeatureGroup section structure
The FeatureGroup section begins and ends with the lines Begin FeatureGroup and End
FeatureGroup. Feature group definition consists of a unique name and a list of features
contained in the feature group.
Example
Begin FeatureGroup
NAME = Synposys
FEATURE_LIST = ASTRO VCS_Runtime_Net Hsim Hspice
End FeatureGroup
Begin FeatureGroup
NAME = Cadence
FEATURE_LIST = Encounter NCSim NCVerilog
End FeatureGroup
Parameters
•
NAME
•
FEATURE_LIST
NAME
Required. Defines the name of the feature group. The name must be unique.
FEATURE_LIST
Required. Lists the license features contained in the feature group.The feature names in
FEATURE_LIST must already be defined in Feature sections. Feature names cannot be
repeated in the FEATURE_LIST of one feature group. The FEATURE_LIST cannot be empty.
Different feature groups can have the same features in their FEATURE_LIST.
ProjectGroup section
Description
Optional. Defines the hierarchical relationships of projects.
The hierarchical groups can have multiple levels of grouping. You can configure a tree-like
scheduling policy, with the leaves being the license projects that jobs can belong to. Each project
group in the tree has a set of values, including shares, limits, ownership and non-shared, or
exclusive, licenses.
Use blstat -G to view the hierarchical dynamic license information.
Use blinfo -G to view the hierarchical configuration.
ProjectGroup section structure
Define a section for each hierarchical group managed by License Scheduler.
The keywords GROUP, SHARES, OWNERSHIP, LIMIT, and NON_SHARED are required.
The keyword PRIORITY is optional. Empty brackets are allowed only for OWNERSHIP,
LIMIT, and PRIORITY. SHARES must be specified.
Begin ProjectGroupGROUP SHARES OWNERSHIP LIMITS NON_SHARED
PRIORITY
(root(A B C)) (1 1 1) () () () (3 2 -)
(A (P1 D)) (1 1) () () () (3 5)
(B (P4 P5)) (1 1) () () () ()
lsf.licensescheduler
Platform LSF Configuration Reference 523