Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: DRDA Service doesn't establish connections with in-bound IBM Java clients for DB2


View products that this article applies to.

Symptoms

The Microsoft Service for DRDA (DRDA Service) does not establish connections with in-bound IBM Java clients for DB2.

↑ Back to the top


Cause

The DRDA Service returns an incorrect DRDA PRDID (Product Identifier) that is outside the range of supported values that is unrecognized by IBM Java clients for DB2.

↑ Back to the top


Resolution

This issue is fixed in Cumulative Update 2 for Host Integration Server 2016.

After Cumulative Update 2 is installed, the DRDA Service returns a correct DRDA PRIDID "SQL11000" that is compatible with IBM Java Clients for DB2.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

Learn about the terminology Microsoft uses to describe software updates.

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top


Keywords: kbQFE, kbfix, kbBug, kbExpertiseInter, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 4019807
Revision : 10
Created on : 1/9/2018
Published on : 1/10/2018
Exists online : False
Views : 257