IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Spectrum LSF
Components Administration
Created by Guest
Created on Feb 6, 2020


Because "Preemption scheduling" is actually for the jobs in different queues.

LSF today has no such feature or concept of in-queue preemption.

the new feature maybe work like this:

define a INQUEUE_PREEMPT=[[userA,80%] [userB,20%]] ...

For example, the queue has total 1000 slots, so userA can use 800, userB can use 200.


If there is no userB jobs, userA can use all of 1000 slots.

If userB submit 100 jobs, userA should suspend 100 jobs, let userB run.

If userB submit 300 jobs, userA should suspend 200 at max(20%), let userB run 200 jobs totally.

  • Guest
    Mar 30, 2020

    This will be considered in a future release