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 (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 Future consideration
Workspace Replication: Change Data Capture
Created by Guest
Created on Feb 23, 2023

RELATED IDEAS

Enhance CDC z/OS to support Db2 z/OS RBA/LRSN values in full length (New JCF: COMMITSEQ/INTENTSEQ)

We plan to migrate existing SQL Replication CCD tables to CDC Live Audit tables.

For that we need to identify the exact values for the source RBA/LRSN log-points to keep the original sequence of DML and to identify the COMMIT scope of the transaction.

The currently provided Journal Control Fields (JCFs) &SEQNO and &CCID in CDC are cut. They only provide a 6-byte extract of the 10-byte RBA/LRSN. In a high-volume system, these values are not unique from a certain point in time.

In SQL Replication these values are represented in full 10-byte format in the columns IBMSNAP_INTENTSEQ and IBMSNAP_COMMITSEQ as VARCHAR(16) FOR BIT DATA.

We like to have the identical values and behavior in CDC JCFs as in SQL Replication.

COMMITSEQ should be the RBA/LRSN of the captured COMMIT of the source transaction, not the begin-of-UR as currently provided by &CCID.

We would like to have two new JCFs &INTENTSEQ and &COMMITSEQ with a datatype of VARCHAR(16) FOR BIT DATA that provide the full 10-byte RBA/LRSNs of each DML operation and COMMIT.

Needed By Yesterday (Let's go already!)
  • Guest
    Reply
    |     Dec 4, 2024

    We are also interested in this idea as we also want to do the same migration and at the moment the &SEQNO field does not map the entire RBA/LRSN.

    And this issue for us is blocking.


    Regards

  • Admin
    Alex Klufas
    Reply
    |     May 5, 2023

    IBM Update: thank you for submitting this request. We have reviewed it an deem it valid. We are working through architecting a solution. At this time, we will not be committing resources to this enhancement. Thanks.

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.