IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Planned for future release
Components Q Replication for Z
Created by Guest
Created on Apr 12, 2017

QREP DDL replication, add UNICODE factor for column length

When replicating from non-unicode to unicode, the legth of char/varchar target columns needs to be extended. Example: create all CHAR/VARCHAR columns at the target with source_length*2 and implemented an additional life belt with OKSQLSTATES = 22001 (SQL Code -302) and some source checking to prevent unwanted chars which extend to more than factor 2 in unicode.
That works quite fine for DML, but not for DDL. When a new VARCHAR Column is added to the source, Apply with REPLADDCOL creates the column at the target but is not able to extend the source length, which leads to unwanted and difficult to handle exceptions and makes release processes more than complex.
We are asking for an optional feature to let Apply create char/varchar target columns with a length of source_length*x. x Could be stored as parameter in APPLYPARMS.