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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Future consideration
Workspace Spectrum LSF
Components Other
Created by Guest
Created on Mar 25, 2023

Provide ability to dump sequence of jobs ids considered by LSF scheduler for dispatch during a dispatch cycle

An old job which is pending in LSF may continue to remain pending with the reason "Individual host based reasons" while newer jobs continue to get scheduled. This may happen due to queue priority and fairshare settings.

When running 'badmin diagnose' on such a job, it details the reason for the job pending with various per host reasons. However, there is no mention of whether the job was bumped down in priority while considered for scheduling.

Currently there is no way to debug fairshare as the cause for job pending as the job eventually get considered for dispatch and there will not be sufficient resources left to dispatching it.


Pending jobs is one of the biggest pain points for user running their jobs and inability to determine accurate pending reason cripples us to determine what action to take. Often it comes down to experience & guess work when solving jobs pending due to fairshare.


To help with above scenario, having an ability to list the sequence in which jobs (along with the queue & fairshare related details) were considered during dispatch cycle(s) would help determine if the job is pending for long time due to queue priority & fairshare settings.

Needed By Quarter