Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at



Spectrum LSF

Showing 389

Have LSF Handle ZOMBI job searching using either BTREE or HASH ALGO's

Large number of ZOMBI jobs can impact very large clusters operations resulting in high backlogs and additional lost job status. Improving the ZOMBI search algorithm from Linear Search to BTREE or HASH would reduce this impact.
24 days ago in Spectrum LSF / Administration 0 Future consideration

Enhance the Support Tool to be able to remove ZOMBI jobs and create a log of exec hosts and pgids that need to be cleaned

We had an issue where LSF could not keep up with dispatch due to high numbers of ZOMBI jobs. We would like the ability to shut down LSF and clean up the ZOMBI jobs via a Database repair to accelerate the time-to-restore of the LSF clusters.
24 days ago in Spectrum LSF / Administration 0 Future consideration

Make Queue Open/Close/Act/Inact 'all' Requests a single event

We recently had a serious issue that required us to close/inact all of our queues, and then perform a database repair using the IBM support tool. However, when we started LSF, all but one of the queues was Open/Act again. This was due to the suppo...
24 days ago in Spectrum LSF / Administration 0 Future consideration

Make the TCP Backlog for the MBATCH and MBATCHD Query Port Configurable for Large Clusters

We have been monitoring the TCP backlogs for LIM, MBD, and the Query port for some time, and there are periods where the MBD query port becomes overloaded resulting in a higher than expected count of UNKNOWN and sometimes eventually ZOMBI jobs, an...
24 days ago in Spectrum LSF / Administration 0 Future consideration

Enable License (LS) Visibility on Spectrum Application Center

We would like users to have visibility of the availability of solver license on LSF Application Center. We are using version and were told by support that this feature is no longer supported. This is necessary as it enables users to have ...
2 months ago in Spectrum LSF / End User UI/Applicaton Center 0 Future consideration

bsub should accept a cpu_efficiency parameter to allow cpu over-commiting in the pool

It's rare for a job to achieve close to 100% cpu efficiency. Often, jobs have a peak cpu requirement during its execution lifetime but use less cpus in average. If bsub could be told that a job is expected to run with a given cpu efficiency, LSF c...
4 months ago in Spectrum LSF / Simulation & Prediction 2 Needs more information

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...
4 months ago in Spectrum LSF / Reporting/Explorer 4 Not under consideration

job select statement improvement

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...
6 months ago in Spectrum LSF / Scheduling 2 Future consideration

Add lsb.params setting to limit the number of times a job can be redispatched upon either a pre-exec failure of job initilization failure

We currently have jobs that will bounce from host to host either based upon a pre-exec failure, or a job initialization failure. This can impact > 500 hosts and cause an increase in MBD memory use. It would be nice to have a setting such as: MA...
about 1 month ago in Spectrum LSF / Administration 0 Future consideration

Add a JobID's column to the table grid_hosts_gpu and show in Job Details page

It would be very beneficial to reporting to see which jobid's are allocated to which jobs when it comes to the GPU assigned. This way, the user can look at the ELIM graphs and know that their job is actually using the GPU in question. Right now, y...
about 1 month ago in Spectrum LSF / Operations/RTM 0 Future consideration