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 Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on Jan 22, 2015

Need to change the status of hosts from closed_Excl to ok

In the cluster we have hosts with large number of cores - 16,32,48,.. Users would request exclusive access to a host and land on these large hosts. The users forget that they have requested the jobs or keeping the host for future use and the entire host stays idle.

In these cases we would like to make the host status "ok" so that other users can use the resources. Currently the only way to release the host is to kill the job.

  • Guest
    Oct 3, 2016

    Stripping a job of exclusive use of a host could be problematic - the job may have requested just one slot, but have spawned threads using the whole machine. Thus if excl were removed, and another cpu intensive job dispatched to the same host, they would be competing for resources. We have no plans to implement the functionality as requested.

  • Guest
    Feb 10, 2015

    One way to implement this is to add a duration to the job. The job can be exclusive for a given time and after that it becomes a non-exclusive job.

  • Guest
    Jan 23, 2015

    Creating a new RFE based on Community RFE #64813 in product Platform LSF.