Options

-Pproject_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).

-pprocess_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 "[exit_code …] [EXCLUDE(exit_code …)]"

-q "queue_name ..."

-R "res_req" [-R "res_req" …]

Specify automatic job requeue exit values. Use spaces to separate multiple exit codes. The reserved keyword all specifies all exit codes. Exit codes are typically between 0 and 255. Use a tilde (~) to exclude specified number or numbers from the list.

exit_code has the following form:

"[all] [~number ...] [number ...]"

Job level exit values override application-level and queue-level values.

Jobs running with the specified exit code share the same application and queue with other jobs.

Define an exit code as EXCLUDE(exit_code) to enable exclusive job requeue. Exclusive job requeue does not work for parallel jobs.

If mbatchd is restarted, it does not remember the previous hosts from which the job exited with an exclusive requeue exit code. In this situation, it is possible for a job to be dispatched to hosts on which the job has previously exited with an exclusive exit code.

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.

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 job execution.

The size of the resource requirement string cannot exceed 512 characters. If you need to include a hyphen (-) or other non-alphabet characters within the string, enclose the text in single quotation marks, for example, bsub -R "select[hname!='host06-x12']".

A resource requirement string is divided into the following sections. Each section has a different syntax.

◆A selection section (select). The selection section specifies the criteria for selecting execution hosts from the system.

◆An ordering section (order). The ordering section indicates how the hosts that meet the selection criteria should be sorted.

196Platform LSF Command Reference