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

res_req parsing functions in LSF API

It would be useful to have functions for parsing the res_req strings. These strings are included in job info structure, but there is no way to extract particular components from them other than using standard C string processing functions, ie. strstr, strtok etc. I guess there are functions for doing so in LSF code, but nothing in the public API.

  • Guest
    Oct 3, 2016

    We have no current plans to expose the internals of the parser API.
    In LSF 10.1.0.1 the esub will automatically expose variables containing memory and swap requests.

  • Guest
    Jan 19, 2015

    Exposing the internals of the parser is something we may do in the future.

  • Guest
    Jan 15, 2015

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