Platform LSF Reference Version 6.2

bsub
Platform LSF Reference
166
You are running an application version 1.5 as a resource called app_lic_v15 and the
same application version 2.0.1 as a resource called
app_lic_v201. The license key for
version 2.0.1 is backward compatible with version 1.5, but the license key for version 1.5
will not work with 2.0.1.
Job-level resource requirement specifications that use the
|| operator take precedence
over any queue-level resource requirement specifications.
◆ If you can only run your job using one version of the application, submit the job
without specifying an alternative resource. To submit a job that will only use
app_lic_v201:
% bsub -R "rusage[app_lic_v201=1]" myjob
◆ If you can run your job using either version of the application, try to reserve version
2.0.1 of the application. If it is not available, you can use version 1.5. To submit a
job that will try
app_lic_v201 before trying app_lic_v15:
% bsub -R "rusage[app_lic_v201=1||app_lic_v15=1]" myjob
◆ If different versions of an application require different system resources, you can
specify other resources in your
rusage strings. To submit a job that will use 20 MB
of memory for
app_lic_v201 or 20 MB of memory and 50 MB of swap space
for
app_lic_v15:
% bsub -R "rusage[mem=20:app_lic_v15=1||mem=20:swp=50:app_lic_v201=1]" myjob
-s signal
Send the specified signal when a queue-level run window closes.
By default, when the window closes, LSF suspends jobs running in the queue (job state
becomes SSUSP) and stops dispatching jobs from the queue.
Use
-s to specify a signal number; when the run window closes, the job is signalled by
this signal instead of being suspended.
-S stack_limit
Sets a per-process (soft) stack segment size limit for each of the processes that belong
to the batch job (see
getrlimit(2)). The limit is specified in KB.
-sla service_class_name
Specifies the service class where the job is to run.
If the SLA does not exist or the user is not a member of the service class, the job is
rejected.
You cannot use
-sla with -g. A job can either be attached to a job group or a service
class, but not both.
You should submit your jobs with a run time limit (-W option) or the queue should
specify a run time limit (RUNLIMIT in the queue definition in
lsb.queues). If you do
not specify a run time limit, LSF automatically adjusts the optimum number of running
jobs according to the observed run time of finished jobs.
Use bsla to display the properties of service classes configured in
LSB_CONFDIR/cluster_name/configdir/lsb.serviceclasses (see
lsb.serviceclasses(5)) and dynamic information about the state of each service
class.