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...
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...
We are facing the need to limit access to certain data columns/fields in LSF Explorer for certain roles. In our environment a few different teams will make use of the reporting capabilities of LSF Explorer in different scopes. Nevertheless, LSF Ex...
When a Benchmark job fails It would be nice to see the bsub used to submit the job
We can manually construct the actual bsub, but it would be nice to be able to cut and paste it when editing the Benchmark job so we can test that it actually will work. In one case we were getting "Queue Permission Errors" and it having that bsub ...
The Reporting tool in cacti gives the option of sending out periodical usage graphs to users. It would be great to also have the option of including raw CSV data in these reports. The workaround is to log into RTM and manually grab the CSV export,...
LSF Explorer support for multiple clusters with the same name
Customer has multiple clusters with the same cluster name. Changing LSF cluster names to be unique is not an option. Their environment is large. Other products in the LSF family support this. LSF_LIC_SCHED_CLUSTER_ALIAS addresses the concern for L...
Chargeback report in LSF explorer reports usage based on slots that are tied to CPU cores. Deep learning experiments use CPUs and GPUs, we need chargeback to include GPU usage so that the target users/departments can be charged appropriately.
Do not place IBM confidential, company confidential, or personal information into any field.