To specify multiple files, repeat the -f option.
local_file is the file on the submission host, remote_file is the file on the execution host.
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.
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 ><
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.
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.
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