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.
Automate restart of IIDR tasks when RRS terminates
We had issues with RRS recently which were solved via a maintenance cycle. During those issues, our IIDR Capture and Apply tasks failed and required manual restart. We have the option TERM=N enabled yet the Capture/Apply tasks were not restarted w...
In a busy Q Rep env with many bi-di Q subs, there may lots of P2PNORECAPTURE signal insert into IBMQREP_SIGNAL control table by Q Apply program. As per design, Q Capture delete up to 10000 rows at a time for one prune interval. When the average P2...
We'd like to request Replication to have re-try / reconnect mechanism even without MQ multiple instances. Because currently it doesn’t support MQ multiple instances, we can use SLB, but if it has no re-connect, we can do nothing.
When a table fails due to structure or availability changes, the replication set should instead set the failed table to inactive instead of crashing capture. It should also send an email notification to alert of the issue.
Do not place IBM confidential, company confidential, or personal information into any field.