-outdir

Categories

io

Description

The -outdir option supports the following dynamic patterns for the output directory:

• %J - job ID
• %JG - job group (if not specified, it will be ignored)
• %I - index (default value is 0)
• %EJ - execution job ID
• %EI - execution index
• %P - project name
• %U - user name
• %G - User group new forthe job output directory

For example, the system creates the submission_dir/user1/jobid_0/ output directory for the job with the following command:

bsub -outdir "%U/%J_%I" myprog

If the cluster wide output directory was defined but the outdir option was not set, for example, DEFAULT_JOB_OUTDIR=/scratch/joboutdir/%U/%J_%I in lsb.params, the system creates the /scratch/joboutdir/user1/jobid_0/ output directory for the job with the following command:

bsub myprog

If the submission directory is /scratch/joboutdir/ on the shared file system and you want the system to create /scratch/joboutdir/user1/jobid_0/ for the job output directory, then run the following command:

bsub -outdir "%U/%J_%I" myjob

Since the command path can contain up to 4094 characters for UNIX and Linux, or up to 255 characters for Windows, including the directory and file name, the outdir option does not have its own length limitation. The outdir option supports mixed UNIX and Windows paths when LSB_MIXED_PATH_ENABLE=Y/y. LSB_MIXED_PATH_DELIMITER controls the delimiter.

The following assumptions and dependencies apply to the -outdir command option:

• The execution host has access to the submission host.
• The submission host should be running RES or it will use EGO_RSH to run a directory creation command. If this parameter is not defined, rsh will be used. RES should be running on the Windows submission host in order to create the output directory.