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 updateson 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
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...
Documentation of raw data format in Classic CDC MQ publishing.
This is not functional requirement, but documentation requirement.
it seems that Classic CDC MQ publishing have a capability to publish data format by using PUBBINASIS=TRUE. I've found this function in developerWorks.
High availability for IMS CDC in a SYSPLEX environment
We are currently implementing CDC for IMS in our Production environment.
This consists of 2 IMS v15.2 systems running on 2 different LPAR's, in a SYSPLEX.
The OS on both are currently z/OS 2.3.
CDC for IMS runs on 1 LPAR, replicating the LOGS o...
Journal Field for to identify transaction which updated the record
We are looking for following fields in management console journal fields which can help us identify who updated the record information :- First Priority - &JOB (This is must have field for all update/delete/insert operation on the record - It ...
Do not place IBM confidential, company confidential, or personal information into any field.