HiT ODBC/DB2 and HiT ODBC Server/DB2 Release Notes
 

Version	Date	Changes
6.0.0.0	10/22/07	Added support for Microsoft Windows Vista and passed Windows Vista certification; Fixed a problem with output parameters when using stored procedures called by SQL Server where the position of every parameter was shifted by 1; Fixed a problem with distributed transactions using two phase commit with DB2 v8.x . A unique SYNCLOG file name is now used instead of a different file for every session; Introduced HTML help to replace WinHelp.
5.1.0.3 Update Pack Only	06/08/06	Fixed a problem reading LOB data using Gupta/Centura where, after reading affected LOB columns using SQLGetData, non-LOB columns of the record were read using SQLBindCol+SQLFetch.
5.1.0.2 Update Pack Only	04/25/06	Fixed a problem with distributed transactions using two phase commit with DB2 V8.x; Fixed a problem when using CHAR FOR BIT DATA with VB.NET. String truncation was occurring for when reading CHAR FOR BIT DATA values.
5.1.0.1	03/06/06	Introduced optional SQLDescribeParam (in data source configuration Advanced Tab) to allow/disallow applications using server descriptions for parameters. This is particularly useful when running parametric stored procedures; Fixed a problem where a connection error occurred using file DSNs run by services. Using a file DSN and getting a connection error caused the service to hang without getting back control from the driver; Fixed a problem where DSN-less connection strings were not working and failed to connect; Improved support for commitment management for CALL statements (stored procedures); Modified the behavior of SQLGetInfo for SQL_SERVER_NAME. Now returns the name of the DB2 DBMS to which the driver is connected; Introduced support for BIGINT data type for parameters; Fixed a "memory allocation failure" problem with parametric queries using DOUBLE parameter = 0; Fixed a CHAR to TIMESTAMP conversion problem for text literals to be sent as timestamp values: some separator characters were not recognized, causing the conversion to fail; Introduced 4-byte length for CONCISE TYPE data descriptions, required by .NET environments which require data length always as a 4-byte integer. The problem appeared using "IsDBNull" methods on some data types such as LONG VARCHAR; Updated HiT Server Agent included (in Server edition only).
5.0.0.3	02/03/05	Added XA/2PC (distributed transactions) support for DB2 8.1. Current 2PC support level does not include recovery.
5.0.0.2	12/15/04	Enhanced performance in situations when “Hold Cursors on Commit” is set, Isolation Level is non-zero and DML commands are issued; Fixed a problem in the global trace when tracing timestamp literals; Added support for a new low level trace (DRDA) feature, append trace. To activate, in the HSDB2.INI DRDA TRACE SECTION, manually set MPTNTrace=1.
5.0.0.0	10/06/04	Added support for DB2 UDB 8.1 (including support for 64-bit DB2 platforms); Added support for scrollable cursors; Added support for Stored Procedures with LOBs; Updated the SSL support with the latest cipher suites.
4.1.1.2 Update Pack Only	02/27/04	Added feature to change password on OS/390. It is possible to change the password by passing the connection password in this format: CurrentPassword/NewPassword.
4.1.1.1	01/28/04	Fixed a problem with opening the help file in DSN configuration dialog and HiT Toolbox.
4.1.1.0	01/12/04	Updated SSL support with the latest cipher suites; Fixed a catalog query problem encountered when using SQL Explorer of Borland Delphi 7: some tables not related; Fixed a SBCS conversion problem: a specific conversion of a field on a Chinese system was not performed correctly.
4.1.0.5	10/10/03	Fix for allowing Stored Procedures call on DB2 MVS v5, regression introduced in version 4.1.0.2. Synopsis: the SP output params that was simply not returned.A DRDA warning SQLCODE = +464, SQLSTATE = 01609 described the return of a Result Set for a SP that doesn't have any; Fix for SQLDescribeParam: Parameter description is not available in DB2 MVS v5.That caused some applications Based on Gupta technology to fail when running parametric queries, since the client requries a parameter description to the server. Now the driver allows parameter description based on DB2 server version; Added a new option in the advanced tab of the DSN configuration dialog to enable/disable the SQLExtendedFetch API. Disable this option fixes a compatibly problem with Power Builder 9.0 and Crystal Report 9.0; After reached the last record in the result set Crystal Report 9.0 try to close the cursor and this generates an exception; now this special situation is managed; SQLGetTypeInfo for Sql_Decimal returned "length,scale" instead of "precision,scale" in the CREATE_PARAMS column.
4.1.0.4	08/11/03	Improved DRDA errors management in multithreading environments; Improved High-level trace: API exit time added to the trace. Output parameters are now correctly traced after the execution of a statement; Fixed case-sensitive UserID and Password management in Toolbox Test (UID/PWD will be converted to uppercase); Fixed a problem in support for stored procedures with single and multiple-result sets; Introduced recovery for error with SQLCODE = -905 during Fetch operations; Fixed a regression that causes an Unhandled Exception while executing a Stored Procedure Call and improved error management; Fixed a bug : Querying empty tables with xLOB fields DRDA returns SQLCODE 100 SQLSTATE 02000 as an error; Fixed Parser: Introduced support for expressions and qualified identifiers in GROUP BY clause.
4.1.0.2	02/11/03	Added management for Case Sensitive UserID & Password ( Only for DB2/NT version 8.1 ); Fixed a sporadic problem occurs when exiting from a NT service that involves HiT ODBC driver ( Unhandled exception : Access Violation ); An error message is now returned for the PRMNSPRM codepoint (only when errors are encountered executing a Stored Procedure); The RDBCMTOK codepoint is now traced properly; When ENDUOWRM is returned by the Host, all open cursors (for dispositions 1 and 2, i.e., commit and rollback) are closed and marked to be opened on next execute; Current resultset Fetch position and last Fetch position offsets are saved for each result set in a multiple result set situation (when generated by calling a stored procedure); Only-output parameters now are properly handled even if no value is specified prior to calling the execution of a stored procedure; Support for stored procedures with multiple result sets is now available for most platforms both in SNA and TCP/IP. Major hurdles were found for large result sets (both for vC0 and D0 modes of returning results); .Net support added:stream buffers are now created using CoTaskMemAlloc for managed-to-unmanaged code support; Fixed a regression introduced to support SPs with multiple result sets (especially SNA environments).
4.1.0.1	10/25/02	Fixed a problem related to commit management: While using 2PC support, RDBCMM doesn't have to be sent to DB2 after the statement's execution
4.1.0.0	09/10/02	Global trace timing introduced; Low level trace improvement and fix: Process ID, Thread ID and timing are now traced. Fixed a concurrency problem using traces and multiple processes causing exceptions and protocol errors; Updated toolbox in Static SQL Package function: the local package file was incorrectly found empty; Fixed an error on OS390 calling parametric queries using VARCHAR and VARBINARY types; Created a new VS 6.0 configuration to support integration of the DRDA.DLL with the .Net environment. Replaced some ‘new’ and ‘delete’ calls with CoTaskMemAlloc and CoTaskMemFree; Introduced Two-Phase Commit – 2PC support for distributed transactions; Introduced support for DB2 8.1
4.0.0.6	06/21/02	Removed check for limiting user id and password to less than 10 characters; Fixed a problem with SQL Statements produced with Microsoft Access 97 running on WINNT (Changed SQL Statement Pre-Parsing management); Solved a C++ exception using the Remote Client with Crystal Reports during connection; Fixed a problem with nested queries and ADO 2.6 recordsets: When the first opened recordset ended, VB application would crash; Introduced UTF-8 support for code page 1208; Fixed an error using SQLExtendedFetch from Visual Basic and ADO: the cursor was not correctly positioned.
4.0.0.5	01/04/02	Fixed a problem with SQL statements length; Fixed a problem with thick client and Access97 to link a table: the configuration parameters in some cases weren’t counted correctly; Fixed a problem with CALL STATEMENT using Query Analyzer (SQL Server) and MS ODBC bridge: Now possible to run this statement; Fixed a problem with extended fetch using Query Analyzer (SQL Server) and MS ODBC bridge: Before, only one row was returned from a query; Solved a problem with Delphi 5 using Database Explorer with SqlGetData.
4.0.0.4	10/30/01	Fixed an error with SQLFetch function, with the agent enabled: When a table had several records, the send() to the database server required by the new fetch block caused a conflict with the send() used to notify the agent service of the new operation: after the first fetch block, the SQLFetch had a DRDA Fetch Error (TCP/IP Error 10053-4). Fixed a problem (in debug mode): if the connection failed, another error occurred, caused by the notification to the agent of the connect function’s ending. Added support for the SQLDescribeParam function. Fixed some updating problems with LOB data types. Fixed an error running a stored procedure to OS390: When using the brackets ‘{’ and the catalog name between double quotes, the parser wasn’t able to correctly analyze the statement. Added Arabic/Hebrew support for Windows 2000.
4.0.0.3	07/05/01	Added HiT Server Manager to HiT ODBC Server/DB2 to provide services for monitoring server activity and connection pooling; Added Change License Key menu item to Toolbox for updating product license keys; Modified uninstall program to allow users to choose whether to keep or delete data sources when removing the product; Updated installation to include Microsoft Data Access Components (MDAC) version 2.6
4.0.0.1	05/25/01	Fixed a problem with BIGINT column types: now supported - converted to a DECIMAL (19,0).
4.0.0.0	05/04/01	LOB support released; Arabic support with one-to-two and two-to-one mapping introduced; Fixed problem with Toolbox Test and data sources configured in SNA; Fixed memory problem with Win 98 on systems using Norton AntiVirus 2000 with Attachmate SNA Gateway. This caused a system crash with the following message A Fatal Exception 0E Has Occurred at 0177:BFF9DBA7; Modified DRDA DLL in order to manage character conversions based on the CCSID field, not on HCP configuration: this is performed by loading the right conversion table “on demand” whenever it’s needed and maintaining the table loaded in a Table Array; Added EUC support for AIX Japanese system RS/6000 (Table 954); Modified DRDA DLL in order to manage ANSI Host Code Pages in the range 1250-1258.The tables are not enlisted in the HCP combo; Modified Native Error return message getting return code by the message text; Introduced maximum connection number check by module and no longer by environment. Basing the maximum number by environment caused an increased connection number available for applications using more environments; Modified error messages due to invalid key and added expiration date and max number of connections in the About dialog in the Workshop; Corrected an error caused by opening conversion tables in a non-shared mode.
3.1.2.0	05/03/00	Modified global trace in order to provide more details about running machine, HiT product installed and MDAC version; Support for VM: updated catalog functions (SQLTables and SQLColumns); Support SSL Strong released for all versions.
3.1.1.1	04/13/00	Running a parametric query, SQLFreeStatement with SQL_CLOSE option called after SQLPrepare and SQLBindParameter and before SQLExecute caused the loss of information about the bound parameters. This caused errors or “no data found” depending on the parametric query Package support for DB2 accessing AS/400 has been added to HiT ODBC Toolbox. Improved DBCS support, in particular for UDB and Japanese tables. Setup: new MDAC version (2.50.4403.12);
3.1.1.0	02/15/00	HSALIAS32.DLL (32bit driver) has been removed from the installation process. The loading test of this DLLs has also been removed from the Toolbox; Introduced dbXpress feature; FileDSN test, view and dbXpress options now available in the Toolbox If the host does not support the isolation level, an error is returned (this error was not managed in the old version); Fixed a problem in the Toolbox: router unknown running the test on a dsn configured with “Attachmate SNA Gateway”; Fixed an error using a Symbolic Destination Name smaller than 8 characters with “Attachmate SNA Gateway”; Updated conversion tables 280 and 37; License key now visible from “About” in Toolbox Setup: The runtime version can be installed only on machines running Microsoft Windows 95/98, Windows NT 3.51 or NT 4.0 Workstation and Windows 2000 Professional (Windows 3.11 if you are using the 16-bit version of ODBC/400); Setup: Changed installation options in the installation options dialog; Setup: Dcom 98 replaced from Dcom95 latest version (1.3); Added support for Linux DB2 UDB to DRDA.
3.1.0.1	10/14/99	Introduced SSL security with two levels ( DES40 = Weak Encryption and 3DES = Strong Encryption) only with native TCP/IP as the communication protocol; New MDAC version (2.1.2.4202.3); New version with Strong Encryption for USA; DB2: Problem retrieving 0-length VARCHAR or BINARY fields previously bound with SQLBindCol; New setup versions: Weak and Strong.
3.0.0.0 (beta)	09/14/99	New features: ODBC 3.x; DB2/400 is now supported (sharing the same DRDA code as the DB2 versions); Support for MTS; Silent setup: to install HiT ODBC/DB2 without user intervention, the “silent.exe” file was added to the installation. Silent.exe is called from the command line. This file is not needed for the LITE version; Inserted MDAC (2.1.2.4202.3) and DCOM98 to replace Microsoft ODBC installation. When this component is checked, the Administrator icon is created; the setup procedure disables the MDAC component on Windows 2000; Running a query on DB2 systems could generate a lock on the application that executed it. This problem will very rarely happen, and was due to an unusual data format used by DB2 in some particular cases.