Platform LSF Administration Guide Version 6.2

Chapter 42
Non-Shared File Systems
Administering Platform LSF
589
><, <>
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.
bsub -i
If the input file specified with bsub -i is not found on the execution host, the file is
copied from the submission host using the LSF remote file access facility and is removed
from the execution host after the job finishes.
bsub -o and bsub -e
The output files specified with the -o and -e arguments to bsub are created on the
execution host, and are not copied back to the submission host by default. You can use
the remote file access facility to copy these files back to the submission host if they are
not on a shared file system.
For example, the following command stores the job output in the
job_out file and
copies the file back to the submission host:
% bsub -o job_out -f "job_out <" myjob
Example
To submit myjob to LSF, with input taken from the file /data/data3 and the output
copied back to
/data/out3, run the command:
% bsub -f "/data/data3 > data3" -f "/data/out3 < out3" myjob data3 out3
To run the job batch_update, which updates the batch_data file in place, you need
to copy the file to the execution host before the job runs and copy it back after the job
completes:
% bsub -f "batch_data <>" batch_update batch_data