Options

If you specify the first word of the message description (no spaces), the text of the job’s status begins with the specified word. Only the first word is evaluated.

job_ID "job_name"

If you specify a job without a dependency condition, the test is for the DONE state (LSF assumes the “done” dependency condition by default).

numdone(job_ID, operator number *)

For a job array, the number of jobs in the DONE state satisfies the test. Use * (with no operator) to specify all the jobs in the array.

numended(job_ID, operator number *)

For a job array, the number of jobs in the DONE or EXIT states satisfies the test. Use * (with no operator) to specify all the jobs in the array.

numexit(job_ID, operator number *)

For a job array, the number of jobs in the EXIT state satisfies the test. Use * (with no operator) to specify all the jobs in the array.

numhold(job_ID, operator number *)

For a job array, the number of jobs in the PSUSP state satisfies the test. Use * (with no operator) to specify all the jobs in the array.

numpend(job_ID, operator number *)

For a job array, the number of jobs in the PEND state satisfies the test. Use * (with no operator) to specify all the jobs in the array.

numrun(job_ID, operator number *)

For a job array, the number of jobs in the RUN state satisfies the test. Use * (with no operator) to specify all the jobs in the array.

numstart(job_ID, operator number *)

For a job array, the number of jobs in the RUN, USUSP, or SSUSP states satisfies the test. Use * (with no operator) to specify all the jobs in the array.

post_done(job_ID "job_name")

The job state is POST_DONE (post-execution processing of the specified job has completed without errors).

post_err(job_ID "job_name")

The job state is POST_ERR (post-execution processing of the specified job has completed with errors).

started(job_ID "job_name")

The job state is:

◆RUN, DONE, or EXIT

◆PEND or PSUSP, and the job has a pre-execution command (bsub -E) that is running.

204Platform LSF Command Reference