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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Components Q Replication for Z
Created by Guest
Created on Sep 30, 2017

No Expression Procession for CAST_TO_VARCHAR2

z/OS has 65536 code page for Chinese character. CAST_TO_VARCHAR2 does not make any change in character. But the expression with Chinese character causes performance problem.

For character in RAW to VARCHAR2, Qrep should ignore the expression CAST_TO_VARCHAR2 and make no procession.

  • Admin
    Rohit Agarwal
    Apr 6, 2020

    Latest discussion with Serge suggests there is a workaround and this idea could be rejected.

  • Admin
    Rohit Agarwal
    Apr 6, 2020

    Adding histroy from RFE-32425:

    4.Davendra PaltooDec 1, 2017 6:32 AMJennifer:

    --之前serge和陶谦应该是指出可以将源端设置65535改成在目标段设置1386,避免主键索引字段引用cast_to_varchar2的做法,功能我验过,计划下周搭环境验证性能。
    Serge and Tao Qian suggested that change 65535 in Source with 1386 in Target to prevent cast_to_varchar2 with primary fields. ICBC has tested with the suggestion. The fuction is OK. ICBC plans to set up environment to test performance in next week.

    3.Davendra PaltooDec 1, 2017 6:30 AMSerge:
    We still need to better understand this issue. We would like to fully understand why the customer needs expression on the replication key and unique indexes. Have they tried defining the subs without those expressions? Is the data coming from the mainframe already in the target Oracle codepage? Are they using codepage_override for both cases?

    Today, Q Apply must evaluate the expressions BEFORE it can do dependency analysis on the replication key and other unique indexes. We could consider not evaluating the expression only if and when the expression is a CAST_TO_VARCHAR2 and the source is for BIT DATA (and codepage_override to no conversion). Would that work? For this case, I wonder why there is the expression in the first place.
    Unfortunately, removing the expression evaluation before dependency analysis has several implications on Q Apply design and is not entirely trivial. We will need to further assess if it really needed, before we accept this requirement.

    2.Davendra PaltooOct 19, 2017 7:47 AMHe Fang to help with the clarification on what is being requested.

    1.Davendra PaltooOct 19, 2017 7:42 AMSerge to follow up with client.