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 12, 2018

To enable increase in the memory for a job when overall memory resource limit is in place in lsb.resources

Case#Case number TS001621460 can be referred for this RFE.

Explanation was: I have discussed with development team again, currently, LSF can not satisfy the increase memory request by bmod command for a running job when there is a general limit defined in lsb.resources. This should be a limitation. Because the general limit defined in lsb.resources which is handled by scheduler, but bmod is handled by mbatchd. When bmod a job, mbatchd cannot know whether the operation will break general limit, so it rejects the request directly. This behavior is introduced together with lsb.resources and hasn't changed ever since. I totally agree with you that it should be re-considered from user point of view especially when the user just have one job running and want to enlarger the memory usage.