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:

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 Scheduling
Created by Guest
Created on May 25, 2022

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 run on either hosts with res1 (resource) OR ( res2 and the loaner_host dynamic resource).

The scheduler is letting the job run on this host as if someone used (note no parens):

'select[defined(res1) || defined(res2) || dynamic_pool==loaner_host]'

$ grep specific_host lsf.cluster.<site>

specific_host model type 1 () () () (blah !res1 docker !res2)

$ lsload -o dynamic_pool specific_host



I should not have to use:

-R 'select[(defined(res1) && !defined(res2)) || (defined(res1) && dynamic_pool==loaner_host)]'

Needed By Month
  • Guest
    Jun 22, 2022

    We had some scenarios where this combination of resources was needed. The set of hosts was owned by one team, but they shared them with another using the dynamic_pool value. It became an obvious case showing the issues with the select statement logic.

    I'm pretty sure that there were other cases, but this was the easiest to replicate and describe.

  • Guest
    Jun 22, 2022

    why we need two exclusive resources ?