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



Add a new idea Subscribe
Status Under review
Workspace Cloud Pak for Data
Components DataStage
Created by Guest
Created on Apr 15, 2026

RELATED IDEAS

Enable ORCHESTRATE Support in Redshift Connector

Currently, ORCHESTRATE-based job design logic works correctly with the Teradata connector, but fails with the Redshift connector. This creates a functional gap during Teradata → Redshift migrations and forces redesign of existing, production-stable DataStage jobs.

When using ORCHESTRATE inside SQL statements with the Redshift connector, DataStage does not interpret ORCHESTRATE correctly.

Instead, the Redshift connector passes ORCHESTRATE.<variable> directly to Redshift SQL, which results in runtime SQL errors.

Use Case:
Dynamic delete logic based on runtime ORCHESTRATE values (Year/Month derived during job execution)

DELETE FROM #$RS_RPTDM_DBNAME#.INTV_MDCTN_ORDR_FCT

WHERE CAST((#$RS_RPTDM_DBNAME#.INTV_MDCTN_ORDR_FCT.CRT_DT_DK/100) AS INTEGER)

      = ORCHESTRATE.Create_Year_Month

  • Many enterprise DataStage jobs depend heavily on ORCHESTRATE logic
  • Lack of support breaks existing Teradata job designs when migrating to Redshift
  • Increases migration effort, risk, and validation cycles
  • Teradata connector already supports this behavior
  • Redshift connector should also work similar to Teradata
Needed By Week

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.