Software fixes

The following table lists the known problems that were fixed for the DirectConnect version 12.6.1. The DirectConnect products affected are identified, and each issue contains a description, resolution, and the associated Quality Tracking System (QTS) number.

Table 5: Description of software fixes

Product

Description

Resolution

QTS #

DirectConnect for ODBC only

The odbct test utility did not work in the bourne shell.

Corrected DC_SYBASE.sh.

420665

The column names containing “$” were not correctly SQL transformed.

SQL transformation now supports “$” in column names.

417800

A template transfer using a stored procedure fails.

Sybase now supports stored procedures in a template transfer.

416251

DirectConnect for DB2 UDB only

Incorrect date formatting occurred with only 3 digit years.

Dates are correctly formatted with all 4 digits.

421328

The sp_who stored procedure caused a segmentation fault.

Result handling was corrected to allow zero row result set for DB2 targets.

420094

The sp_tables stored procedure with an owner name starting with “@” failed.

Sybase now supports owner names starting with “@” in sp_tables and other catalog stored procedures.

415687

SQL statements containing SUBSTRING should be changed or transformed to SUBSTR.

SUBSTR is now used for DB2 targets.

402619

ASE/CIS cursor date parameter was bound as datetime.

The date parameter is now bound as date.

402362

Revoked user ID caused the system to fail.

The ODBC driver now returns an error for a revoked user ID.

392025

Using the AlternateID property to connect to the mainframe caused errors.

This has been corrected.

385229

Varchar (2048) proxy table failed. Also bulk transfer had a problems with varchar (2048).

The driver problem with reporting long characters has been fixed.

383500377053

DB2 varchar datatype larger than 255 characters is incorrectly reported as a varchar datatype by the sp_columns property.

This has been corrected.

383494385500

A request was made for Sybase to support AS/400 SQL stored procedures.

AS/400 SQL stored procedures are now supported.

226468

DirectConnect for Informix only

Support for quoted identifiers to ASE/CIS was incorrectly reported.

Quoted identifiers are now identified as not supported.

424820 323126

Select statements and other results-generating queries did not produce results against Informix tables containing VARBINARY columns.

This has been corrected.

275721

Dynamic inserts into char columns on Informix failed because the UserDataType field of the CS_DATAFMT structure was not initialized.

The UserDataType field of the CS_DATAFMT structure is now initialized.

268278

Attempts to perform bulk transfers of rows containing a NULL value datetime column failed.

This has been corrected, and it is now possible to perform bulk transfers of NULL value datetime columns.

241483

When in sybase transformation mode, a failure occurred when inserting binary values preceded by 0x.

This problem has been corrected, and it is now possible to insert binary values preceded by 0x, with or without quotation marks.

234250

DirectConnect for Microsoft SQL Server only

WCHAR columns caused a failure in sp_columns.

WCHAR columns are now supported in sp_columns.

417657

ReturnNativeError = yes returned an error message instead of MSSQL error message.

ReturnNativeError = yes now returns a MSSQL error message.

404658

Null text column result failed when tracing was set to “on.”

The method of sending null result value was changed.

401899

The NTEXT datatype mapped incorrectly through ASE/CIS.

sp_columns was adjusted for NTEXT datatype and XNL settings.

392089

Conflicting datatype was returned in sp_columns when mapping unicode to text.

The problem in sp_columns was fixed for both cspcolumnODBCVersion = 2 and 3.

354091

The SQL_GUID datatype caused failures.

The SQL_GUID datatype is now supported.

224420

A null character data caused SQL statement truncation.

Null characters and binary zeros in SQL statement are now stripped when the StripBinaryZero property is set.

291774

DirectConnect Manager

A Java exception occurred when DCON/Oracle userid was not the DCON/Oracle admin.

This has been corrected.

393601

The security of using a fixed userid=sa and password=null was too weak

The user ID and password is now configurable.

390680 390830