LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 449
C HAPTER
26
Job Dependencies
Contents
◆ Job Dependency Scheduling on page 449
◆ Dependency Conditions on page 450
Job Dependency Scheduling
About job dependency scheduling
Sometimes, whether a job should start depends on the result of another job. For
example, a series of jobs could process input data, run a simulation, generate images
based on the simulation output, and finally, record the images on a high-resolution
film output device. Each step can only be performed after the previous step finishes
successfully, and all subsequent steps must be aborted if any step fails.
Some jobs may not be considered complete until some post-job processing is
performed. For example, a job may need to exit from a post-execution job script,
clean up job files, or transfer job output after the job completes.
In LSF, any job can be dependent on other LSF jobs. When you submit a job, you
use
bsub -w to specify a dependency expression, usually based on the job states of
preceding jobs.
LSF will not place your job unless this dependency expression evaluates to TRUE.
If you specify a dependency on a job that LSF cannot find (such as a job that has not
yet been submitted), your job submission fails.
Specify a job dependency
1 To specify job dependencies, use bsub -w to specify a dependency expression
for the job.
Syntax bsub -w 'dependency_expression'