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.
Being able to see the currently available and reserved memory values for a host[group] requires a 'bhosts -l' report. It would be very nice to report something like: $ bhosts -o 'HOST_NAME mem mem_reserved' [host_name ... | host_group ... | comput...
I have hosts with exclusive resources and some with a dynamic resource. A few hosts have two exclusive resources. The job submit: $ bsub -R 'select[ defined(res1) || (defined(res2) && dynamic_pool==loaner_host)]' I would expect this job to...
We would like that preemption will be supported also for MIG jobs(A100 dgx mig devices). Currently the preemption is not working for this type of jobs. Example scenatiois: kill two or more jobs and reconfigure mig to have the new job run. We need ...
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...
Adjust login messages in LSF Explorer for better troubleshooting
We are facing a strange behaviour with the messages for a failed login at LSF Explorer Server. There are three scenarios: The user is not able to the system on the server where LSF Explorer is installed - hence the user is not able to login to LSF...
In our environment, a few different teams will make use of different reporting capabilities in LSF Explorer in different scopes. Therefore they will be creating different reports and dashboards. So there is the need to introduce something like a p...
This is the current bbot/btop functionality:- Group administrators can change the position of all jobs submitted by users who are members of the user group within a queue (move the selected job before/after the first/last job with the same priorit...
Do not place IBM confidential, company confidential, or personal information into any field.