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 Mar 27, 2015

Roll back job submission when bsub cannot receive the jobid from mbatchd

Due to a network hiccup caused by an overloaded server, job submission using bsub returned this message which of course does not include the new jobid:

Failed in an LSF library call: Communication time out. Job not submitted

However the job was really submitted causing an inconsistent status between the application launcher (PAC or others) and the LSF scheduler.

  • Guest
    May 5, 2015

    The root cause is an incorrect error message. If the client cannot determine that the submission was successful, then the error message should not be "Job not submitted" which is clearly wrong. Changing this message can be handled as a defect.

    The timeout the client will wait for a response can also be increased.

    However, having the mbd wait to receive an acknowledgement from bsub would significantly reduce the throughput of the cluster. And if we were to provide rollback, the client would then also need to wait for an acklowdgement that a rollback had occured etc

  • Guest
    Mar 28, 2015

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