bwait command logging

Addressed in Service Pack 13

Thanks for the feedback. It is too late to include this in the next service pack, but we will consider it for the subsequent one.

Please go ahead.
A way to identify who is using bwait from where is the main ask of this RFE but the changes you proposed sounds very much needed too and would be helpful in ensuring proper usage of the tool.

"bwait" uses the same framework as job dependencies, so it should not introduce any additional overheads.

That said, we acknowledge that there is no obvious way to see where bwait is being used.

The original use case for bwait was for it being in a user script which is submitting jobs - so it is clear to the user when the script is waiting. However, we are seeing people use it within a running job - in that scenario it is not easy to see if the job has hung, or is it waiting on something else. Clearly, using a lot of bwait's within running job scripts will lower utilization as you could have many slots blocked with jobs waiting on something.

We are considering three enhancements in this area, and would appreciate your input:

1) A administrative option to prevent bwait from being used within a job. This will prevent running jobs blocking slots with bwait (if desired).

2) If bwait is allowed within a job, using bwait within the job, a message will be posted to the job so that it is clear from querying the job that it is waiting.

3) Expose additional counters in badmin perfmon for the number of waits.