Skip to Main Content
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 Mar 10, 2017

Q Apply issue a warning after exception due to OKSQLSTATES

Using OKSQLSTATES certain error conditions can be specified which will let Q Apply document a failing operation in IBMQREP_EXCEPTIONS.
Today, Q Apply does not write out a warning into the log file if an exception based on OKSQLSTATES happened.
Monitoring (often done be monitoring the APPLY log file) of such errors is very difficult / impossible if these exceptions are not logged.
This RFE addresses to (optionally) log warnings in the Q APPLY log when exceptions related to OKSQLSTATES happen.

A parameter like WARNOKSQLSTATES could control this behavious. WARNOKSQLSTATES=N would let Q Apply log as of today. WARNOKSQLSTATES=Y would let Q Apply write out an additional warning messages if a record was not applied but saved to IBMQREP_EXCEPTIONS due to OKSQLSTATES.

  • Admin
    Rohit Agarwal
    Apr 6, 2020

    Adding histroy from RFE-30188:

    2.Davendra PaltooJun 27, 2017 12:47 PM From Serge's May 9 update

    We finished our investigation, proposing a simple parameter WARNOKSQLSTATES=Y.

    This is trivial to implement - total sizing is 1PW (both test, and code).