Platform LSF Administration Guide Version 6.2

Chapter 22
Job Dependencies
Administering Platform LSF
379
external
Syntax
external(
job_ID | "job_name", "status_text")
Specify the first word of the job status or message description (no spaces). Only the first
word is evaluated.
Description
The job has the specified job status, or the text of the job’s status begins with the
specified word.
Job ID or job name
Syntax
job_ID | "job_name"
Description
If you specify a job without a dependency condition, the test is for the DONE state (LSF
assumes the “done” dependency condition by default).
post_done
Syntax
post_done(
job_ID | "job_name")
Description
The job state is POST_DONE (the post-processing of specified job has completed
without errors).
post_err
Syntax
post_err(
job_ID | "job_name")
Description
The job state is POST_ERR (the post-processing of specified job has completed with
errors).
started
Syntax
started(
job_ID | "job_name")
Description
The job state is:
◆ RUN, DONE, or EXIT
◆ PEND or PSUSP, and the job has a pre-execution command (bsub -E) that is
running
Advanced dependency conditions
Job arrays
If you use job arrays, you can specify additional dependency conditions that only work
with job arrays.
To use other dependency conditions with array jobs, specify elements of a job array in
the usual way.
Job dependency examples
◆ The simplest kind of dependency expression consists of only one dependency
condition. For example, if
JobA depends on the successful completion of JobB,
submit the job as shown:
bsub -J "JobA" -w 'done(JobB)' command
◆ -w 'done(312) && (started(Job2)||exit("99Job"))'