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.