Command Reference Guide

Options
188 Platform LSF Command Reference
If you use the -o out_file,-e err_file, -oo out_file, or the -eo err_file option, and you
want the specified file to be copied back to the submission host when the job
completes, then you must use the
-f option.
If the submission and execution hosts have different directory structures, you must
make sure that the directory where the remote file and local file are placed exists.
If the local and remote hosts have different file name spaces, you must always
specify relative path names. If the local and remote hosts do not share the same file
system, you must make sure that the directory containing the remote file exists. It
is recommended that only the file name be given for the remote file when running
in heterogeneous file systems. This places the file in the job’s current working
directory. If the file is shared between the submission and execution hosts, then no
file copy is performed.
LSF uses
lsrcp to transfer files (see lsrcp(1) command). lsrcp contacts RES on
the remote host to perform the file transfer. If RES is not available,
rcp is used (see
rcp(1)). The user must make sure that the rcp binary is in the user’s $PATH on the
execution host.
Jobs that are submitted from LSF client hosts should specify the
-f option only if
rcp is allowed. Similarly, rcp must be allowed if account mapping is used.
-G user_group Only useful with fairshare scheduling.
Associates the job with the specified group. Specify any group that you belong to
that does not contain any subgroups. You must be a direct member of the specified
user group.
-g job_group_name Submits jobs in the job group specified by job_group_name The job group does not
have to exist before submitting the job. For example:
bsub -g /risk_group/portfolio1/current myjob
Job <105> is submitted to default queue.
Submits myjob to the job group /risk_group/portfolio1/current.
If group
/risk_group/portfolio1/current exists, job 105 is attached to the job
group.
Job group names can be up to 512 characters long.
If group
/risk_group/portfolio1/current does not exist, LSF checks its parent
recursively, and if no groups in the hierarchy exist, all three job groups are created
with the specified hierarchy and the job is attached to group.
You can us e
-g with -sla. All jobs in a job group attached to a service class are
scheduled as SLA jobs. It is not possible to have some jobs in a job group not part
of the service class. Multiple job groups can be created under the same SLA. You can
submit additional jobs to the job group without specifying the service class name
again.
For example, the following attaches the job to the service class named opera, and
the group
/risk_group/portfolio1/current:
bsub -sla opera -g /risk_group/portfolio1/current myjob
To submit another job to the same job group, you can omit the SLA name:
bsub -g /risk_group/portfolio1/current myjob2
-i input_file | -is input_file