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,
Post an idea
Upvote ideas that matter most to you
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
I support this request. ( Neale Armstrong, IBM Australia Technical Sales ).
The most common CDC use case these days is from mainframe data sources to Kafka. Kafka inherently misses the transactional paradigm that exists in transactional databases like Db2, IMS, VSAM, Oracle etc... However, the business processes that are being built on top of kafka event hubs still crave that transactional context.
CDC does a great job of supporting this demand for transactional context, with the inclusion of the &CCID JCF, and with the transactionally consistent consumer. But these capabilities are limited to the scope of one DBMS. IMS and CICS are often uses as global transaction managers, writing to two databases with the scope of a single business transaction.
The support for IMS-TM updating both IMS-DB and DB2 was implemented very efficiently, by simply providing a configuration parameter to substutute the local &CCID with the global &CCID. CDC_I_559. The elegance of this solution meant that no changes at all were necessary outside the capture agent. Management Console, Access Server, Apply Agent, Monitoring APIs etc... are oblivious to the fact that they are dealing with a global &CCID rather than a local DBMS &CCID
As a result of fulfilling CDC_I_559 Db2 already logs the global transaction ID for a synchpoint manager, whether it is an IMS SPM or a CICS SPM.
Does the replication log generated by Augmenting a VSAM cluster also include the CICS SPM global transaction commit data ? And if so, could it be used in exactly the same way to support global transaction ID identification ?