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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
hi,As you know Classic CDC for IMS providing basic support. Nowadays it's important to monitor subscriptions' latencies, status or states for IMS side. It is posibble to monitor cdc for DB2 via API but we need same development for IMS. Before thi...
Limit maximum number of writer tasks that can be assigned per subscription
We had an incident where one subscription had monopolized most of the writer tasks which caused replication latency for the RMs of all the other subscriptions in that source/target server pair. Therefore, there should be a parm to set a limit for...
Provide attributes in conflict for message CECD1029E
Message CECD1029E only tells you that the attributes for the VSAM data set are different on the source and target servers. It doesn't tell you WHICH attribute it finds to be mis-matched. It would be more helpful in troubleshooting issues to kno...
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 ...
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 of b...
Diff function for produce log records after VSAM files are REPROed
Many customers are using IDCAM REPRO to update/replace the whole VSAM file during a nightly batch job. The repro operation does not create records in the logstream. As a result, user has to perform REFRESH to resynchronize the target database. S...
CHCCLP returns events from the oldest to the newest, with a limit of 10000 events returned. When using CHCCLP to monitor subscription activity, the intent should be to get the most recent events and current status of subscriptions, not the oldes...
Ref TS003663019 - When using CDA there is no option to log-in with read-only access so the assumption is that any CDA user could add, delete, or update a subscription. This is inapproriate for a Production Environment hence why we are experiencin...
Do not place IBM confidential, company confidential, or personal information into any field.