Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Planned for future release
Workspace Spectrum LSF
Components Data Management
Created by Guest
Created on Oct 6, 2026

Synchronous bstage out to guarantee data readiness for downstream jobs

Currently, bstage out returns successfully after the transfer jobs have been submitted in DMD. However, in reality, the transfer jobs may take a significant amount of time to complete. The downstream job flow, meanwhile, assumes that the data is ready as soon as bstage out returns.

A feature enhancement to add an option to make bstage out block and not return until DMD detects that the transfer jobs have completed? This would guarantee that the data has been successfully transferred to the staging area before bstage out returns, allowing downstream jobs to safely consume the data.

Needed By Yesterday (Let's go already!)
  • Admin
    Bill McMillan
    Nov 3, 2026

    Thanks for the clarification.
    Tentative delivery will be the end of the year, we'll have a better idea once development resource becomes available to work on.

  • Guest
    Oct 15, 2026

    Because the network architecture of the remote execution servers is isolated, direct scp between the remote execution servers and the local cluster is not available in our environment. Please help to implement this. Thank you.

  • Admin
    Bill McMillan
    Oct 13, 2026

    The default data movement in LSF is synchronous - e.g. bsub -f "a.txt < a.txt " a.out > a.txt the transfer of "a.txt" back to the submission host will be performed synchronously - ie the job will not complete until the transfer is complete.

    Data Manager is designed to address cases where you do not want the transfer to be synchronous - such as moving data to/from a cloud cluster - you want the data to be in place before jobs are scheduled, and move the results back after the job is complete - avoiding paying for cloud instances sitting idle while data is being moved.

    For jobs where you want synchronous returns, then you could add bsub -f as above, or create a wrapper around bstage to give an additional option, say outsync - which will use scp instead to synchronously move the data.



    #!/bin/bash
    
    set -euo pipefail

    mode="${1:?missing mode}"
    shift

    if [[ "$mode" == "in" || "$mode" == "out" ]]; then
    exec bstage "$mode" "$@"
    fi

    if [[ "$mode" == "outsync" ]]; then
    src=""
    dst=""

    args=("$@")
    for ((i=0; i<${#args[@]}; i++)); do
    case "${args[$i]}" in
    -src)
    src="${args[$((i+1))]}"
    ;;
    -dst)
    dst="${args[$((i+1))]}"
    ;;
    esac
    done

    [[ -n "$src" ]] || { echo "Missing -src"; exit 1; }
    [[ -n "$dst" ]] || { echo "Missing -dst"; exit 1; }

    exec scp -r "$src" "$dst"
    fi

    echo "Invalid command: $mode" >&2
    exit 1