Dynamic Cluster jobs will distinguish between provisioning time (when the jobs are in the PROV job state) and running time (when the jobs are in the RUN job state) to show a more accurate job status and be able to determine how much time jobs are spent actually running.
To enable this feature, specify LSB_DC_DISP_PROVISION_TIME=Y in lsf.conf. When enabled, the following commands distinguish provisioning time from running time:
The bacct, bhist, and bjobs commands show the PROV job state when Dynamic Cluster jobs are provisioning. In addition, the job query API also uses the PROV job state, allowing other applications to distinguish between provisioning time and running time.
Certain LSF commands report job details, while others only report counters (for example, 10 RUN jobs, 15 PEND jobs). The commands that only report counters, which includes bqueues and bapp, treat PROV jobs as identical to RUN jobs, so the counter for RUN jobs also includes PROV jobs. This is because PROV is a special type of RUN job: it is basically a job in a RUN state with an active provision action.
For example, if there are 10 RUN jobs and 10 PROV jobs, commands that report job details (such as bjobs, bhist, and bacct) report 10 RUN jobs and 10 PROV jobs, while commands that report job counters (such as bqueues and bapp) report 20 RUN jobs.