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

Clear

Ideas

    Discard tie-up tracking data for a CICS region that isn't running

    IIDR/VSAM encountered issues with tie-up tracking introduced in CICS TS 6.1 where the CICS region would not log/flush tie-up records when a file was either closed intra-day or at normal region shutdown. In order to address the missing file close r...
    3 months ago in Data Replication: IMS / VSAM  / Data Replication for VSAM for z/OS 0 Submitted

    Multi-tenancy support for Analytics Engine Spark

    Client has two CP4D installs that require multi-tenancy support. One install's use case is MLOps, while the other is pure Spark compute usage. They would like to separate/isolate workloads by tenants, while maintaining a uniform UI. As these two s...
    4 months ago in Analytics Engine 0 Submitted

    Full GRAPHIC/VARGRAPHIC support by Classic CDC

    In the current Classic CDC, there are cases where GRAPHIC / VARGRAPHIC data is replicated without being converted from the code page specified on the source side to the code page used on the target side. To eliminate this situation, please enhance...
    7 months ago in Data Replication: IMS / VSAM  / Classic Change Data Capture 0 Planned for future release

    Spark job to be able to access, read and write on external database without the credentials being exposed anywhere (instance, logs, job metadata, etc…)

    We want to create a job on a Spark instance of the Analytics Engine powered by Apache Spark that runs a Spark application reading from and writing to an Exasol database. To enable database access, we need to pass our user credentials into the job....
    10 months ago in Analytics Engine 0 Submitted

    Capture DB segment replace calls which actual data is not updated.

    Our client (Fukuoka Financial Group) is currently using Dprop(IMS DataPropagater for z/OS) for creating Data Warehouse. Dprop captures replace calls and writes to PRDS(Propagation Request Data Set) even when DB segment was not actually updated. Cl...
    almost 4 years ago in Data Replication: IMS / VSAM  / Classic Change Data Capture 1 Not under consideration

    Preserve Change Data Capture Bookmark When Journal Assignment Changes on IBM i (AS400)

    Problem Statement When IBM CDC captures changes from an IBM i (AS400) source database, the product relies on the associated journal to track transactional changes. If the source table's journal is changed (for example, the existing journal is remo...
    about 2 months ago in Data Replication: IMS / VSAM  / Classic Change Data Capture 0 Submitted

    Enable MAXTRANSSIZE parm for Classic CDC for VSAM

    When batch jobs perform a large number of updates to VSAM, it create 1 UOR that contains too many changes which made the capture cache may full. However, cache memory are shared by subscriptions. We cannot stop other subscriptions to free cache. F...
    5 months ago in Data Replication: IMS / VSAM  / Classic Change Data Capture 1 Future consideration

    CHCCLP - Return Code Handling in Mainframe and LUW platform

    Provide return codes for individual CHCCLP instructions and add features to CHCCLP script to evaluate return code (e.g., if...then...else...) before proceeding with subsequent instructions. Additionally, include an option to set return codes back ...
    about 1 year ago in Data Replication: IMS / VSAM  / Classic Change Data Capture 2 Future consideration

    Capture DB segment replace calls which actual data is not updated.

    Our client is currently using Dprop(IMS DataPropagater for z/OS) for creating Data Warehouse. Dprop captures replace calls and writes to PRDS(Propagation Request Data Set) even when DB segment was not actually updated. Client’s Dprop application p...
    almost 4 years ago in Data Replication: IMS / VSAM  / Classic Change Data Capture 0 Not under consideration

    Enhancement requests for handling bookmark retrieval (MQGET) failures

    If an MQGET for the CCDC bookmark fails due to insufficient CPU resources, multiple bookmarks may remain in the bookmark queue. As a result, the subscription may read the restart time from an older bookmark and reprocess data that has already been...
    3 months ago in Data Replication: IMS / VSAM  / Data Replication for IMS for z/OS 0 Submitted

    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.