Known Issues for ECDA Option for ODBC

If you add ECDA service information to a local sql.ini file, you see this message during start-up:

CT-LIBRARY error:
ct_connect(): directory service layer: internal
directory control layer error: Requested server name not found.

You must add ECDA service information to the global sql.ini file instead of the local sql.ini file. The global sql.ini file is located in <install_dir>\ini\sql.ini. The local sql.ini file is located in <install_dir>\DC-15_0\connectivity}\ini\sql.ini.

Workaround:None.

The default server.cfg file does not use snrf.tbl as the default value.

Workaround: If you are using the default snrf.tbl, enter the following in the server.cfg file under the section called Client Interaction: ServiceRedirectionFile=snrf.tbl

Express transfer does not support the transfer of char datatypes to and from decimal datatypes.

Workaround: Convert query datatypes from char to decimal datatypes in the transfer query statement using the SQL CAST function.

Express transfer does not support the transfer of text datatypes to and from char datatypes.

Workaround: Convert query datatypes from text to char datatypes in the transfer query statement using the SQL CAST function.

(DB2 UDB) Setting WorkArounds2 value for space padding

(For DataDirect drivers only) For space padding, you must verify that a special string key, the WorkArounds2=131072 string value, is defined in the Windows Registry. This allows the driver to pad DB2 char for bit data fields with spaces instead of binary zeros. Repeat the process for each DB2 UDB Data Source Name (DSN) that you are going to use with ECDA Option for ODBC. See Add the WorkArounds2 string key to pad DB2 character data in the ECDA Installation Guide for Windows.

Workaround: None.

CLOB data is limited to 32K. BLOB datatype is not supported.

Workaround: Use DirectConnect for z/OS Option.

(Microsoft SQL Server) NCHAR and NVARCHAR datatype support

Microsoft NCHAR and NVARCHAR datatypes are not supported but are translated to the single-byte character set of the operating system. Unicode characters that cannot be mapped are translated to a default character for the operating system.

Workaround: None.

If your Microsoft SQL Server 2000 is not at Service Pack 3 or later, set QuotedIdentifiers=yes for the DSN entry for accessing Microsoft SQL Server.

Workaround: None.

An update of read-only cursors fails to return errors against Microsoft SQL Server 2005.

Workaround: None.