In dependency conditions, job names specify only your own jobs, unless you are the LSF administrator. By default, if you use the job name to specify a dependency condition, and more than one of your jobs has the same name, all of your jobs that have that name must satisfy the test. If JOB_DEP_LAST_SUB in lsb.params is set to 1, the test is done on the job submitted most recently.
Use double quotes (") around job names that begin with a number. In the job name, specify the wildcard character asterisk (*) at the end of a string, to indicate all jobs whose name begins with the string. For example, if you use jobA* as the job name, it specifies jobs named jobA, jobA1, jobA_test, jobA.log, etc.
Use the * with dependency conditions to define
For example:
bsub
indicates that before element 1 of myArrayB can start, element 1 of myArrayA must be completed, and so on.
You can also use the * to establish
If you want to specify array dependency by array name, set JOB_DEP_LAST_SUB in lsb.params. If you do not have this parameter set, the job is rejected if one of your previous arrays has the same name but a different index.
In dependency conditions, the variable op represents one of the following relational operators:
>
>=
<
<=
==
!=
Use the following conditions to form the dependency expression.
done(job_ID "job_name" ...)
The job state is DONE.
LSF refers to the oldest job of job_name in memory.
ended(job_ID "job_name")
The job state is EXIT or DONE.
exit(job_ID "job_name" [,[operator] exit_code])
The job state is EXIT, and the job’s exit code satisfies the comparison test.
If you specify an exit code with no operator, the test is for equality (== is assumed).
If you specify only the job, any exit code satisfies the test.
external(job_ID "job_name", "status_text")
The job has the specified job status.
Platform LSF Command Reference 203