Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

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.