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 Employees should enter Ideas at

Status Not under consideration
Created by Guest
Created on Apr 19, 2022

Splitting Software Update package upload and pre-check steps

When doing Software Upgrade, ie. when pressing the "transfer" button in Datastudio, idaa server runs a list of 5 steps.

The first step is the transfer of upgrade package of 20+GB. This could take long if the package does not locate on USS (some customers do not have a USS drive of big enough size), so it could take them a few hours to upload the package.

Step number 5 is db2diag preliminary check to make sure the appliance is on a good shape for upgrade. When the preliminary check fails, it fails the complete package transfer as well, ie. all the 4 steps before will be rolled back, the uploaded package is removed, etc.

On one production appliance, one customer experienced at least 4-5 times of a pre-check failure, and each time the package has to be re-transferred. Due to their small USS size and slow upload speed, it took them 3 attempts (on three individual planned weekends) to upgrade the ONE appliance.

The idea is to

  • separate the 5 steps, so that if the preliminary check fails, the package transfer won't be repeated.

Knut suggested:

  • keep the transferred (unverified) packages in some sort of staging area

  • introduce some validation of the transferred packages and in case they are good, skip re-transferring the packages again?

Needed By Yesterday (Let's go already!)