We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Allow bjobs command to show the pre and post exec exitStatus/exitCode information
Right now, we require bhist to get any detail on pre/post exec error codes, it would be nice if we could get this from the job record via bjobs vs. bhist. bhist in very large environments is a non-starter for obtaining this status information.
Allow Users to specify a ClearCase 'cleartool' command but require that it be white listed first
Allow the users to override the CLEARTOOL binary path, but only if it's included in a white list configuration file in the $LSF_ENVDIR location. I would suggest something like:
Set more job variables in parent SBATCHD prior to forking the job SBATCHD/RES
I've been working with the Daemons Wrap source code trying to make the logging more presentable, and I've come accross a hurdle to effectively enhancing that integration. I need both the Job Start and Submit Times, and normally, I would just be ab...
Track a local directory duing job execution and report utilization details in job rusage
We would like to be able to, at submission time, specify a local directory that we would like to have LSF monitor the total size and files in and report in the Jobs RUSAGE periodically. This directory will be separate from the execCwd or the cwd. ...
Add the following commands to the Query log, also add the total execution time to the query log output
Right now, many commands are logged to the query log, but a certain number of commands are not. Additionally, we would like to know the transaction time to process each command added to the log entry. The commands that are missing are:
Most recent Linux' OS' do not provide an easy way to create a dynamic support for libnsl.so.1 any longer and instead they link to libnsl.so.2* due to libnsl.so being symbolically linked to libnsl.so.2*. The library libnsl.so.2 de-contented several...
bhosts and lshosts should have an option to let them perform more like the scheduler
Currently, if I have a host with two exclusive resources in the lsf.cluster file <hostname> <model> <type> 1 () () () (!res1 !res2) If I run the following bhosts command, it acts like "grep" instead of like the scheduler, and rep...
Enable the Scheduler Debug to Run Continually and Provide JSON Output via 'badmin' Standard Output
Currently the Scheduler debug must be written to a file, and the scheduler debug information is not easily accessible through the management CLI. What would be better would be to have an MBD parameter to enable all the time as is done with 'badmin...
We have a high propensity to perform the following commands:
It would be good if LSF would keep track of the number of successful attempts to run those various commands as is more generally done within the 'badmi...
Add a bjobs -R option to seach combined Resource Requirements for jobs that match a select pattern
We have been working on performing analysis of buckets in RTM, and we have found some buckets that have difficulty getting access to resources. Though we have done this, searching for jobs that match a resource requirement is proving more difficul...
Do not place IBM confidential, company confidential, or personal information into any field.