LSF Version 7.3 - Administering Platform LSF

File Transfer Mechanism (lsrcp)
690 Administering Platform LSF
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
File Transfer Mechanism (lsrcp)
The LSF remote file access mechanism (bsub -f) uses lsrcp to process the file
transfer. The
lsrcp command tries to connect to RES on the submission host to
handle the file transfer.
See Remote File Access on page 688 for more information about using
bsub -f.
Limitations to lsrcp
Because LSF client hosts do not run RES, jobs that are submitted from client hosts
should only specify
bsub -f if rcp is allowed. You must set up the permissions for
rcp if account mapping is used.
File transfer using
lscrp is not supported in the following contexts:
◆ If LSF account mapping is used; lsrcp fails when running under a different
user account
◆ LSF client hosts do not run RES, so lsrcp cannot contact RES on the
submission host
See Authorization options on page 675 for more information.
Workarounds
In these situations, use the following workarounds: