Platform LSF Reference Version 6.2

bsub
Platform LSF Reference
164
If you use -oo without -e or -eo, the standard error of the job is stored in the output
file.
If you use
-oo without -N, the job report is stored in the output file as the file header.
If you use both
-oo and -N, the output is stored in the output file and the job report is
sent by mail. The job report itself does not contain the output, but the report will advise
you where to find your output.
If you use the special character
%J in the name of the output file, then %J is replaced by
the job ID of the job. If you use the special character
%I in the name of the output file,
then
%I is replaced by the index of the job in the array, if the job is a member of an array.
Otherwise,
%I is replaced by 0 (zero).
-P project_name
Assigns the job to the specified project.
On IRIX 6, you must be a member of the project as listed in
/etc/project(4). If you
are a member of the project, then
/etc/projid(4) maps the project name to a
numeric project ID. Before the submitted job executes, a new array session
(
newarraysess(2)) is created and the project ID is assigned to it using setprid(2).
-p process_limit
Sets the limit of the number of processes to process_limit for the whole job. The default
is no limit. Exceeding the limit causes the job to terminate.
-q "queue_name ..."
Submits the job to one of the specified queues. Quotes are optional for a single queue.
The specified queues must be defined for the local cluster. For a list of available queues
in your local cluster, use
bqueues.
When a list of queue names is specified, LSF selects the most appropriate queue in the
list for your job based on the job’s resource limits, and other restrictions, such as the
requested hosts, your accessibility to a queue, queue status (closed or open), etc. The
order in which the queues are considered is the same order in which these queues are
listed. The queue listed first is considered first.
-R "res_req"
Runs the job on a host that meets the specified resource requirements. A resource
requirement string describes the resources a job needs. LSF uses resource requirements
to select hosts for remote execution and job execution.
The size of the resource requirement string is limited to 512 characters.
Any run-queue-length-specific resource, such as
r15s, r1m or r15m, specified in the
resource requirements refers to the normalized run queue length.
A resource requirement string is divided into the following sections:
◆ A selection section (select). The selection section specifies the criteria for
selecting hosts from the system.
◆ An ordering section (order). The ordering section indicates how the hosts that
meet the selection criteria should be sorted.
◆ A resource usage section (rusage). The resource usage section specifies the
expected resource consumption of the task.