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.
Change job submit time to include milliseconds for precision.
Job submit time to include milliseconds for precision. Instead of HH:MM:SS, make it like 12:29:05.1234. This will enable this column to be used as a unique identifier when generating data in an incremental fashion. We are extracting the RTM data a...
Enable more dynamic tags in LSF resource connector
Currently in Resource connector only one dynamic tag called "RC_ACCOUNT" is enabled but we would like to have more such dynamic tags which can be used along with bsub command.Example;Current tag takes only " -P project_name" as a dynamic tag . But...
Add Regular Expressions for Project Limits and SLA Auto-Attach and Permissions
We utilize hierarchical projects and at times we would like to allow certain projects and certain functions, both that are a part of the hierarchy to utilize an SLA, for example, assume that the project has three levels project_code:finance_code:f...
Ability to limit user's views in RTM to select clusters
Reduces support because users can't flip to other clusters via Cluster drop-down menu to then ask questions about resources and usage or see other information that should only be for users of a particular cluster or why can't they find their infor...
allow update for span string after a job is started
currently, it's not possible to update the span string after a job is started.
for ex: a user start a multinodes jobs using bsub .... -n x -R ".. span[ptile=y]" ...
unfortunately, he forgot to specify to the tool to start in mutlinodes an...
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...
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:
Do not place IBM confidential, company confidential, or personal information into any field.