Adding one more field [JobID] to "badmin diagnose -c query" output

If users execute query commands in LSF batch job, it can overload the LSF master server and degrade its performance. To address this, we need a new field for job IDs to expedite the identification of problematic jobs.

And the requirement is to add one more field [JobID] to "badmin diagnose -c query" output, like below:

As-Is

[Timestampe] [query command],[UserID],[which host the request came from],[ data size],[query command options]

To-Be

[Timestampe] [query command],[UserID],[which host the request came from],[data size],[query command options],[JobID] # if the query command does not come from batch job, then show [-].

Needed By

Month

Post comment

Admin

Bill McMillan

Jul 14, 2025

From a query perspective, the mbatchd doesn’t know which job any given query came from - it only knows host/user. It would be a major rewrite of the query logic to implement this enhancement, and could only be done as part of a major release as it would fundamentally change the query protocol.
However, after identifying a problem host from the output of the badmin diagnose, you could then do “bjobs -u $user -m $host -r” to see what is running on the host.

Reply
Hide replies

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Adding one more field [JobID] to "badmin diagnose -c query" output