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: The ADO.NET Provider for DB2 can't read data stored in DB2 for z/OS V11 TIMESTAMP(6) WITH TIME ZONE columns


View products that this article applies to.

Symptoms

Consider the following scenario:

  • You try to use a query to read data by using the Microsoft ADO.NET Provider for DB2.
  • The data is stored in DB2 for z/OS V11 as TIMESTAMP(6) WITH TIME ZONE.

When you run the query in this scenario, you experience the following exception:

↑ Back to the top


More information

After this update is installed, the Microsoft DRDA Application Requester Client for DB2 data conversion functionality is updated to correctly process DB2 for z/OS V11 TIMESTAMP(6) WITH TIME ZONE columns.

↑ Back to the top


Resolution

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

↑ 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 : 4023749
Revision : 8
Created on : 1/10/2018
Published on : 1/10/2018
Exists online : False
Views : 225