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
Created by Guest
Created on Mar 7, 2019

SQL Engine enhancement to support "Db2 mode" SQL syntax rules

(This IDEA item was written based on my own experience in DVM POC test at customer site.)

In DVM, SQL syntax rules are based on ANSI-92 standard, not on Db2 for z/OS rules, even in the case where DVM virtual table is defined on Db2 for z/OS table.

For existing Db2 for z/OS customers, this means they would experience a lot of SQL syntax errors after they move their applications to DVM environment, because they often have a lot of SQL statements whose syntax would not be allowed by ANSI-based SQL engine.

To help such situation, DVM has a kind of event handling engine called 'SEF'(Server Event Facility) inside, and customer can make and activate their own SQL Rule(s), REXX program each, to modify or override such "bad" SQL syntax.

However, making and testing SQL Rule(s) require not a few skill and workload of customer. So, if customer has a large number of, and/or a wide variety of such SQL syntax, this approach looks not realistic at all.

Instead, I'd like to request DVM to have another set of SQL engine, which supports SQL syntax rules specific to Db2 for z/OS.

For example, how about the following scenario ?
1) When defining a virtual table, customer selects "Db2 for z/OS" data source and checks "Use Db2 for z/OS SQL Engine" checkbox or something like that.
2) When application issues SQL statement toward this virtual table, DVM checks its SQL syntax using Db2-specific syntax rules.

Another idea is to add a new AVZSIN00 parameter  to select which SQL engine to use.