Symptoms
Consider the following scenario:
-
You use the Microsoft Service for Distributed Relational Database Architecture (DRDA) to send SQL statements from IBM DB2 to SQL Server.
-
A parameterized SQL statement is included in a static SQL package.
-
The parameter data values that are passed in the SQL statement are invalid values for the data types that are used.
In this scenario, the name of the static SQL package that is run when an error occurs is not written to the Microsoft Service for DRDA log file. The missing static SQL package name makes it difficult to identify which package failed when there are multiple SQL packages being run by the Microsoft Service for DRDA.
Resolution
Cumulative update information
The fix that resolves this problem is included in Cumulative Update 1 for Host Integration Server 2013.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
After Cumulative Update 1 is applied, the Microsoft Service for DRDA writes additional details to the log file when errors occur during the processing of invalid SQL parameter data values. The additional details include the SQL package name and the consistency token.
