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 Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on Feb 17, 2020

License Scheduler fix INUSE license token detection on same-server Jobs

The License Scheduler is unable to correctly identify the INUSE and RESERVE values of requested tokens (e.g. rusage[MYTOKEN=4], when more than one jobs run on the same server by the same user.

Possible solution:
This could be solved, if the License Scheduler used the provided PIDs of the GRID jobs to filter out the correct job which is using the licenses.
These PIDs are also shown by the output of LMSTAT.
More information can be found in the attached support case ID.

  • Guest
    Sep 10, 2020

    There has been no response from the submitter for the requested information, as such, this RFE will be rejected.

  • Guest
    Feb 20, 2020

    In your PMR you include an output from lmstat that contains pid information of the form:

    user host: license [pid = 12345] (version) ...

    Can you confirm the specific flags/versions and whether this is a custom build of lmstat?
    None of the documentation for lmstat indicates pid information being available, and it is not shown in the versions of lmstat we have tested in the lab.