Feedback
Did this article resolve your question/issue?

   

Article

Connect for JDBC DB2 driver's AlternateID option is setting CURRENT SQLID instead of CURRENT SCHEMA

Information

 
TitleConnect for JDBC DB2 driver's AlternateID option is setting CURRENT SQLID instead of CURRENT SCHEMA
URL Nameconnect-for-jdbc-db2-driver-s-alternateid-option-is-setting-current-sqlid-instead-of-current-schema
Article Number000178439
EnvironmentProduct: Connect for JDBC DB2 driver
Version: 5.1
O/S: Java
Database: DB2 on Z/OS
Application: N/A
Question/Problem Description

Connect for JDBC DB2 driver's AlternateID option is setting CURRENT SQLID instead of CURRENT SCHEMA.  Behavior found when connected to DB2 Z/OS

Steps to Reproduce
Clarifying Information
Error Message
Defect Number30654
Enhancement Number
Cause
Due to a broken implementation of the portion of the driver that checks for the DB2 type, DB2 on Z/OS (MVS) was not being detected properly by the driver.
Resolution
Fixed in hotfix 5.1.4.000183

Refer to "Connect for JDBC hot fix download and install instructions" for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date5/31/2017 3:10 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.