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.
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 P2PNORECAPTURE insert speed faster than Q Capture house keeper cleanning speed, IBMQREP_SIGNAL table may growing very big.
Although we know reduce the parameter of prune_interval could help to solve the issue， customer think it will be helpful to get a message if this situation appears with a hint to reduce the pruning interval, like print a warning message to prompt customer that they may take a consideration to reduce the prune interval, otherwise data may accumlated and signal table will grow big
Do not place IBM confidential, company confidential, or personal information into any field.