Skip to Main Content
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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Workspace Spectrum LSF
Created by Guest
Created on Dec 6, 2021

Deprecate License Scheduler DYNAMIC setting and support RUSAGE DURATION natively

Currently License Scheduler does not support jobs that use a DURATION on a license reservation in either Fast Dispatch or Cluster Mode. We would prefer that License Scheduler follow LSF properly in all three modes, and deprecate/remove the DYNAMIC setting entirely from License Scheduler. The new behavior would be: 1) If a user places a reservation on a token, mark as RESERVED when not in use. 2) If a user places a reservation on a token with an DURATION, mark as RESERVED until the either the token is checked out, or the reservation expires 3) If a users reservation has expired and the user subsequently checks out a token, mark the license use as OTHERS in license scheduler. 4) If a user does not place a reservation on a token and subsequently checks out a token, mark as OTHERS in license scheduler.
Needed By Yesterday (Let's go already!)