LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 689
Non-Shared File Systems
If the directory is not available on the execution host, the job is run in /tmp. Any
files created by the batch job, including the standard output and error files created
by the
-o and -e options to bsub, are left on the execution host.
LSF provides support for moving user data from the submission host to the
execution host before executing a batch job, and from the execution host back to the
submitting host after the job completes. The file operations are specified with the
-f option to bsub.
LSF uses the
lsrcp command to transfer files. lsrcp contacts RES on the remote
host to perform file transfer. If RES is not available, the UNIX
rcp command is
used. See File Transfer Mechanism (lsrcp) on page 690 for more information.
bsub -f
The -f "[local_file operator [remote_file]]" option to the bsub command copies
a file between the submission host and the execution host. To specify multiple files,
repeat the
-f option.
local_file File name on the submission host
remote_file File name on the execution host
The files local_file and remote_file can be absolute or relative file path names. You
must specific at least one file name. When the file remote_file is not specified, it is
assumed to be the same as local_file. Including local_file without the operator
results in a syntax error.
operator Operation to perform on the file. The operator must be surrounded by white space.
Valid values for operator are:
> local_file on the submission host is copied to remote_file on the execution host
before job execution. remote_file is overwritten if it exists.
< remote_file on the execution host is copied to local_file on the submission host after
the job completes. local_file is overwritten if it exists.
<< remote_file is appended to local_file after the job completes. local_file is created if it
does not exist.
><, <> Equivalent to performing the > and then the < operation. The file local_file is copied
to remote_file before the job executes, and remote_file is copied back, overwriting
local_file, after the job completes. <> is the same as ><
If the submission and execution hosts have different directory structures, you must
ensure that the directory where remote_file and local_file will be placed exists. LSF
tries to change the directory to the same path name as the directory where the
bsub
command was run. If this directory does not exist, the job is run in your home
directory on the execution host.
You should specify remote_file as a file name with no path when running in
non-shared file systems; this places the file in the job’s current working directory on
the execution host. This way the job will work correctly even if the directory where
the
bsub command is run does not exist on the execution host. Be careful not to
overwrite an existing file in your home directory.