|
Version
|
Date
|
Changes
|
4.0.0.0
|
10/22/07 |
- Added support for Microsoft Windows Vista and passed Windows Vista certification;
- Fixed a problem with catalog issues when using Visual Studio 2005 where the environment was suspended while designing a new data access project due to a lack of catalog information;
- 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.
|
3.0.0.3
Update Pack
Only |
04/25/06 |
- Fixed a problem with distributed transactions using two phase commit with DB2 V8.x;
- Added support for Microsoft Windows 64-bit environments.
|
| 3.0.0.2 |
03/06/06 |
- Fixed a problem with distributed transactions using two phase commit. Running
transactions in a SQL Server environment with DB2 zOS 7.x and above caused transaction failures;
- Fixed a problem in the Server Edition where re-using pooled connections caused the
re-connection attempt to hang when the Server Agent is active;
- Fixed a problem where running 4-level INSERT/UPDATE/DELETE queries with SQL Server linked
servers with DB2 UDB 8.x did not report the correct number of rows affected;
- Fixed a problem where the Toolbox was not displaying the correct Isolation Level for
Packages retrieved;
- Improved support for reported error details and description for DRDA level errors;
- Improved support for stored procedures by introducing support for 7.x and
8.x zOS/MVS systems and LOB arguments;
- Enhanced support for stored procedures with management of result sets;
- Improved connect-logon sequence process to meet XA specifications;
- Fixed a problem where the wrong return value was supplied for the “number of
rows affected” property in parametric queries;
- Introduced support for BIGINT SQL data type;
- Improved management of autocommit for DML SQL statements;
- Improved management for parametric queries on various DB2 platforms;
- Improved management for traditional SQL data types;
- Improved management for LOB data types on DB2 8.x systems;
- Fixed an issue with Convert Date Time when used in SQL Server with linked servers
and querying timestamp fields: sometimes the description of the fields and the data
retrieved was conflicting causing queries via linked servers to fail;
- Improved the global trace to make it more readable;
- Updated HiT Server Agent (in Server edition only).
|
| 2.1.0.9 |
09/12/05 |
- Fixed a problem with stored procedure call support. In some cases, a release
of the command object did not close the statement on the server causing the server
to hang. The server responded only after resetting the commands and closing
the session;
- Introduced support for IRowsetChange using the IGNORE_VALUE flag to avoid setting
default values for some fields like autonumbers;
- Fixed a problem when parsing a qualified stored procedure used by Query analyzer.
|
| 2.1.0.8 |
11/22/04 |
- Fixed a problem with multiple execution for parametric queries where
executing a SELECT statement, fetching results and rexecuting with different
parameters gave the same results;
- Fixed a problem with positional queries management, used when running queries
via SQL Server linked servers. NULL parameters were not treated correctly;
- Fixed a problem with locking in Two Phase Commit;
- Added support for BIGINT datatype;
- Fixed a problem where the toolbox was running a wrong statement in the SQL test
connecting to a VM system;
- Updated the SSL support with the latest cipher suites.
- Fixed a problem with TIME field: the correct value was not returned;
- Fixed a regression problem introduced in 2.1.0.7 with (SELECT) DECIMAL/NUMERIC SQL types;
- Updated OpenSSL to version 0.9.7d and recompiled the SSL libraries using Visual Studio .NET.
|
| 2.1.0.7 |
08/11/03 |
- Improved multi-threading management with OLEDB. Previously
caused multithreading .NET applications to fail (ex.: random
C++ Exceptions );
- Added HiT OLEDB/DB2 recognition in HiT Server Agent (HiT
Server Manager);
- Improved DRDA errors management in multi-threading enviroment;
- Fixed a problem in Stored Procedures Management under
.NET enviroment: The qualifier was skipped by the parser;
- Fixed a problem that occured when CREATE PROCEDURE statement
contained WITH keywords: The statement was interpreted as
a SELECT statement;
- Fixed a problem in tokens management that caused an Unhandled
C++ Exception when an invalid command text was entered;
- Fixed case-sensitive UserID and Password management in
Toolbox Test (UID/PWD will be converted to uppercase) and
UserID and Password persistence on UDL file. There was a
potential problem using case sensitive UID/PWD accounts
connecting to DB2 UDB 8.1. Now UserID and Password are always
stored in their case formats in the .udl file;
- Enhanced file properties details: The OLEDBDB2.DLL file
in the Server version is now described as HiT OLEDB
Server/DB2 in File Properties, while the Client version
remains HiT OLEDB/DB2;
- Fixed bug in IDBInfo::GetKeywords procedure that showed
up when using HiT WinAllora. An access violation occurred
when releasing the shared buffer containing the keywords
string. The bug caused the calling application to hang because
the shared buffer was on stack and not in system memory;
- Added a new tracing feature to high-level trace: You can
now see in the trace the actual value of each output parameter;
- Fixed a problem with the high-level trace related to GetNextRows
API. Now all the input/output values of this API are traced
correctly;
- Improved catalogs memory management;
- Added support for Stored Procedures with constant parameters;
- Fixed a problem with NUMERIC/DECIMAL data types under
Windows XP. Performing a SELECT statement on a NUMERIC/DECIMAL
column, the driver mistakenly returned only 0-values in
the NUMEIC/DECIMAL column;
- Improved DECIMAL and NUMERIC precision. DECIMAL and NUMERIC
fields can be respectively 38 and 25 digits long;
- Added Column Alias management;
- Fixed a problem in support for stored procedures with
single and multiple-result set;
- Fixed problems related to CREATE PROCEDURE statements
with DECLARE CURSOR;
- Introduced recovering for error with SQLCODE = -905 during
Fetch operations;
- Fixed problems in the memory management of Stored Procedures
parameters;
- Now possible to execute Catalog Queries using case-sensitive
restrictions;
- Improved positional update/insert/delete with BLOB fields
when not using ISequentialStream bindings;
- Fixed a problem in accessor management : Previously, when
the accessor was created after the prepare and not after
the execute, the getdata couldnt find valid binding
information;
- Removed memory leaks in accessor management;
- Fixed a Bug : querying empty tables with xLOB fields DRDA
returns SQLCODE 100 SQLSTATE 02000 as an error.
|
2.1.0.6
|
04/14/03 |
- Resolved concurrency issues in Two Phase Commit Management
;
- Added asyncronous management for ItransactionResourceAsync
Interface.
|
| 2.1.0.5 |
02/11/03 |
- Fixed a problem with the Max. rows in result set property:
it didn't work properly;
- Added management for Case Sensitive UserID & Password
( Only for DB2/NT version 8.1 );
- From now users can execute ADO Parametric Query with
adBSTR parameters;
- ColumnsRowset support for rowsets created by MultipleResults
object returned E_NOINTERFACE because it could not find
data source properties (using the m_sSite instance variable);
- The GetBindings method did not handle accessors properly
with the pObject pointer set to values other than null;
- Fixed a bug on method IRowsetChange:SetData: could not
change the setting of the auto-commit property after a command
was already created (this worked instead for InsertRow and
DeleteRows of the same interface).
|
2.1.0.4
|
11/22/02 |
- .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).
|
2.1.0.3
|
11/18/02 |
- Fixed a problem with Primary Key Catalog Query on DB2
OS/400;
- Stored Procedure support: on MVS systems we do not strip
the package collection name off the call statement;
- Stored procedure support: fixed a bug that incorrectly
set lob support for parameters that do not contain any blobs;
- 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);
- Modified PROCEDURE PARAMS catalog support for AS400 to
handle differences between ROUTINE_NAME and SPECIFIC_NAME
(now catalog query is a join between SYSPROCS and SYSPARMS);
- Fixed a bug that returned invalid ordinal positions for
PROCEDURE PARAMS for DB2/400 and DB2 UDB.
|
2.1.0.2
|
10/28/02 |
- Fixed a problem when calling SP on DB2/400 (library name
was missing);
- Fixed a sporadic problem in getting data while reading
data caused by a format conversion on the bookmark field;
- From the Data Link you can now enable or disable Two Phase
Commit Support;
- From the Data Link you can now enable or disable the use
of Local Settings;
- Fixed a sporadic problem with the Toolbox: The creation
or the editing of a data link file didnt create a
valid data link file under some specific conditions.
|
|
2.1.0.1
|
09/23/02 |
- From the Toolbox you can now insert the connection password
to save in the UDL file;
- Fixed a problem related to commit management: While using
2PC support, no RDBCMM have to be sent to DB2 after the
statement executions.
|
| 2.1.0.0 |
09/12/02 |
- Added Two Phase Commit Support with recovery functionality
for DB2 UDB for OS/390 v6.1;
- Introduced Stored Procedure Management for .NET Framework;
- 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;
- Fixed problem calling Stored procedures returning output
parameters on DB2 for Windows: Output parameters were not
returned;
- Fixed an error using parametric queries with an idle parameter
set;
- 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.
|
| 2.0.0.4 |
07/01/02 |
- This maintenance activity has added support for PRIMARY
KEY and FOREIGN KEY catalog queries (for DB2 OS/390, DB2
UDB and DB2 OS/400). Also the ColumnsRowset interface now
returns Base_Catalog, Base_Schema, Base_Table and Primary
Key information for a SQL Select query;
- .Net DataSet Update method is also supported and integration
with .Net OLEDBAdapter Wizard is provided.
|
|
2.0.0.3
|
06/11/02
|
- Added Convert Date Time checkbox in the Advanced
tab: This feature enables the client application to read
date/time fields as char fields. This can be useful whenever
the date/time field is set to non-date/time values (like
0, NULL, or a very old date) to a NULL data. This behavior
is allowed by the AS/400 server, but can sometimes create
problems if applications (like those using ADO, for instance)
try to read that field expecting a correct date/time value.
The ADO error is usually the following: "Multiple-step
OLE DB operation generated errors. Check each OLE DB status
value, if available. No work was done." By converting
the date/time field to char, this error is avoided;
- Fixed the correct functionality referring to "Max
Rows in Result Set";
- Introduced support for OUT OF PROCESS working mode;
- Fixed a problem occurring in first package creation connecting
to DB2 for AIX. The package creation fails without reporting
explicit messages, but subsequent operations fail with the
following message: Package <PACK_COLLECTION>.<PACK_NAME>
was not found SQLCODE = -805, SQLSTATE = 51002;
- Introduced early release of memory in update/insert/delete
operations;
- Fixed a memory leak using recordsets with IMultipleResults
interface;
- Introduced the DisableWindowLoop check in the registry;
- Fixed a DRDA problem when end-of-rowset is reached;
- Fixed the following problem: when using the toolbox and
changing the trace file name, in the past one could not
trace anything until the toolbox was restarted. Now that
can be done without restarting the toolbox;
- Fixed a problem related to trace file: Trace file is created
and eventually existing file overwritten only when the DLL
is loaded
|
|
2.0.0.2
|
10/30/01
|
- Added support for SQLDescribeParam function.
- Fixed some updating problems with LOB datatypes.
- Running a select count(*) .. from SQL Server
Query Analyzer, the parser converts the * symbol
into a 0, and the OS390 is unable to execute
a select count(0) .. statement. Our parser was
modified in order to fix the problem.
- Fixed a C++ exception running a DELETE statement from
SQL Server Query Analyzer on a OpenQuery function (syntax:
delete OpenQuery (lnkServer, select * from
).
- Changed the memory allocation function for the rowset
object: if the size of the row if consistent, we disable
the optimized delete in order to limit memory use.
- Fixed a problem (in debug mode): if the connection failed,
a second error message would occur, caused by the notification
to the agent of the end of the connect function.
|
|
2.0.0.1
|
08/30/01 |
- Modified online help and readme files.
|
|
2.0.0.0
|
08/21/01
|
- Introduced use of the decimal separator symbol, depending
on the users local settings;
- Modified error messages caused by invalid key, added expiration
date and maximum number of connections in the About dialog
in the Toolbox;
- Resolved a memory leak problem caused by non deallocated
property strings after calling IDBProperties::GetProperty;
- Added HiT Server Manager to HiT OLEDB/DB2 Server to provide
services for monitoring server activity and connection pooling;
- Added Change License Key menu item to the Toolbox for
updating product license keys;
- Added the ability to upgrade HiT OLEDB/DB2 Server version
1.1 to version 2.0;
- Updated installation to include Microsoft Data Access
Components (MDAC) version 2.6 SP1.
|
|
1.1.2.2
|
05/17/01
|
- Fixed a conversion problem in the IRowsetChange:InsertRow
and IRowsetChange:SetData methods. The conversion problem
showed up when converting binary data (DBTYPES_BYTES) into
Variant of type vt equal to VT_BSTR.
|
|
1.1.2.1
|
07/17/00 |
- Resolved a memory exception, which occured when a trace
was active, in CreateAccessor;
- Implemented the IRowsetUpdate interface (the provider
doesnt expose it automatically, but the consumer can
require it);
- Fixed an error for the Mode property: it was permanently
set to Write value;
- Introduced a provider-specific property named Init Timeout,
which can be saved statically. Its value is used as socket
timeout value;
- Fixed a memory allocation error that occurred upon selecting
Rowset Locate: some memory blocks were not reused;
- Resolved an update error with decimal types, with a precision
greater than 19: length of field was not always correctly
calculated;
- Modified DRDA DLL in order to manage ANSI Host Code Pages
in the 1250-1258 range. The tables are not listed in the
HCP combo;
- Added hstable 420, hstable 838 , hstable 954 and modified
hstable 875
|