Administering Platform LSF - SAS

Static Shared Resource Reservation
Chapter 9
Adding Resources
You must use resource reservation to prevent over-committing static shared
resources when scheduling.
The usual situation is that you configure single-user application licenses as
static shared resources, and make that resource one of the job requirements.
You should also reserve the resource for the duration of the job. Otherwise,
LSF updates resource information, assumes that all the static shared resources
can be used, and places another job that requires that license. The additional
job cannot actually run if the license is already taken by a running job.
If every job that requests a license and also reserves it, LSF updates the number
of licenses at the start of each new dispatch turn, subtracts the number of
licenses that are reserved, and only dispatches additional jobs if there are
licenses available that are not already in use.
Reserving a static shared resource
Example
To indicate that a shared resource is to be reserved while a job is running,
specify the resource name in the rusage section of the resource requirement
string.
You configured licenses for the Verilog application as a resource called
verilog_lic. To submit a job that will run on a host when there is a license
available:
% bsub -R "select[defined(verilog_lic)] rusage[verilog_lic=1]"
myjob
If the job can be placed, the license it uses will be reserved until the job
completes.
Administering Platform LSF 157