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.
A more efficient way for CDC to process subscriptions which are behind in the Db2 logs
This is related to the CDC Db2 z/OS engine. The situation is multiple subscriptions that are behind, for example due to the subscriptions being stopped for several hours for technical reasons. We recently had 3 subscriptions that went down for more than 24 hours and one subscription that remained active and processing and advancing the CDC log cache. When the 3 subscriptions were restarted, the log cache no longer contained the needed log data as the active subscription had continued to advance the log cache. This was in a large 10 way Db2 data sharing group that is high volume. Upon restart of the 3 down subscriptions, each of the 3 subscriptions opened individual connections to Db2 requesting log data, which at that point was on archive logs that numbered over 2,000. We moved the archive logs from virtual tape to DASD to help speed the process, however, there was still the MAXRTU limit in play in Db2 on the number of archives that could be actively read. We have seen in the past in our testing environment when this happens, we can encounter what I will call an archive read deadlock from the subscriptions. For example, sub A needs to mount a member archive to continue to move forward; however sub B now has some of the drives as well so the archive needed by sub A can’t be mounted. At the same time sub B is needing an archive mounted but can’t because no drives are available because sub A has some of them but as mentioned can’t be moved forward. Plus, the process was requiring Db2 to read through the same 2,000+ archives 3 times, once for each subscription. There needs to be a more efficient way for CDC to process subscriptions which are behind where multiple subscriptions can leverage the same scraping process of the Db2 log data.
Do not place IBM confidential, company confidential, or personal information into any field.