SYMPTOM:
NOTE: Strategy ODBC Driver for DB2 Wire Protocol is manufactured by Progress (formerly Data Direct) DB2 UDB for z/OS database is also known as DB2 UDB for OS/390 or sometimes simply as DB2/390 or DB2 MVS.
User attempts to run a query against DB2 UDB for z/OS database using the Strategy ODBC Driver for DB2 Wire Protocol and the following error occurs:
Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Unhandled CodePoint: 2F
CAUSE:
This error occurs because a DB2 gateway was used to connect to the DB2 UDB for z/OS database. Strategy ODBC Driver for DB2 Wire Protocol does not support connections to DB2 UDB for z/OS database through a gateway.
This is outlined in article 000003942 from Progress (formerly DataDirect) Knowledge Base. To find this article, go to the Progress Knowledge Base (URL below) and type "4404" in the 'Search' box:
http://knowledgebase.progress.com/
ACTION:
The use of a DB2 gateway for connectivity to DB2 UDB for z/OS database is not necessary for usage with Strategy products. To resolve this error, it is recommended to directly connect to the DB2 UDB for z/OS database.
WORKAROUND:
If the use of DB2 gateway is desired, users may use the IBM DB2 Connect ODBC driver for connectivity. This driver is certified for connectivity to DB2 UDB for z/OS database from Strategy Intelligence Server running on Microsoft Windows. Consult the 'Certified and Supported Configurations' section of the Strategy General Information Readme file for the precise version of the driver that is certified.
Third Party Software Installation:
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
