Informix
Informix Online Documentation

RELEASE NOTES FOR

INFORMIX-Client SDK 2.40

Date: 10/15/99

Version: 2.40


Table of Contents

I. Overview of Release Notes
II. Client-Server Testing
III. New Features
IV. Configuration Requirements
V. Example Files
VI. Known Problems
A. Message filename change in the Client SDK 2.01 and later
B. Using ESQL/C Libraries
C. Client SDK File Size Increase
VII. Fixed Problems
A. Error Message Change for chkenv Utility
VIII. Client-Server Testing


I. Overview of Release Notes

The purpose of these release notes is to make you aware of any special actions required to configure and use the Client SDK products on your computer. This file also describes new features and feature differences from earlier versions of this product and other Informix products, and how these differences affect current products. In addition, this file contains information about known bugs and their workarounds.

This release notes document is not intended to be all-inclusive; it should be used as an addendum to the product manuals which provide thorough information about product features and behavior.

These release notes are written for the following audience:

You will find release notes for products available as part of the Client SDK 2.4 release in the following files::

Filenames Product
CPPREL.HMT[L], CPPREL.TXT INFORMIX-Object Interface for C++
ESQLCREL.HTM[L], ESQLCREL.TXT INFORMIX-ESQL/C
GLSAPIREL.HTM[L], GLSAPIREL.TXT INFORMIX-GLS
INFODBCREL.HTM[L], INFODBCREL.TXT INFORMIX ODBC Driver


II. Client-Server Testing

The Client SDK 2.40 products have been tested with the following database servers:


III. New Features

For information about the content of this release, refer to the release notes and documentation notes for each of the SDK products.


IV. Configuration Requirements

You must not install the 32-bit version and the 64-bit version of the Client SDK in the same INFORMIXDIR directory.


V. Example Files

Some of the Client SDK files, such as ESQL/C and ODBC, include example files. See the release notes for each Client SDK product to find the location of example files for that product.


VI. Known Problems

This section describes the known problems with this release of the Client SDK and shows how to work around these problems. See individual product release notes for problems that are specific to each product.

A. Message filename change in the Client SDK 2.01 and later

For the US English locale, the following problem has been fixed for Version 2.30 of the Client SDK and Connect on both Win32 and UNIX platforms.

The term "old client APIs" in the text below means pre-2.01 versions of Client SDK and Connect and all versions of the separate ESQL/C, ESQL/COBOL and CLI products; the term "new client APIs" means 2.01 and later versions of Client SDK and Connect.

After the installation of versions 2.01 or later of Client SDK or Connect on either Win32 or UNIX platforms, a category of already compiled applications may exhibit an error.

The shared and static libraries in both the old and new client APIs refer to message files in the directory $INFORMIXDIR/msg on UNIX and %INFORMIXDIR%\msg on Win32. The names of several message files were changed in the new client APIs to avoid conflict with the server versions of those files. For example, old client APIs distributed the message file sqli.iem and the libraries in the old client APIs referred to sqli.iem. Now the new client APIs distribute that same message file under the name of csqli.iem and the libraries in the new client APIs refer to csqli.iem.

All of the following circumstances must occur in order for this error to manifest itself:

If all of these conditions apply, then the application will continue to look for message files by their old name, for example, sqli.iem. However, the directory containing just the new client API will have those files by their new name, for example, csqli.iem. Therefore, an error message will be given.

You can use any one of the following workarounds to avoid the error:

This problem has been fixed for Version 2.3. In Version 2.3, the install process of these products will first look to see if the message files already exist by their "old" name in the target installation directory. If they already exist, nothing special will be done. If they do not already exist, a link (on UNIX) or a copy (on Win32) of each message file whose name changed will be made so that both files, like sqli.iem and csqli.iem, will always be guaranteed to exist. This fix will remain in the installation of Client SDK and Connect in all future releases of those products.

B. Using ESQL/C Libraries

In the following notes, I-CONNECT 2.30 refers to the conn.tar file in the Client SDK 2.30 bundle, and ClientSDK 2.30 refers to the clientsdk.tar file in the Client SDK 2.30 bundle.

  1. If I-CONNECT 2.30 is NOT installed on top of an existing 7.2x ESQL/C installation:

  1. If I-CONNECT 2.30 is installed on top of an existing 7.2x ESQL/C installation:

  1. Installing ClientSDK 2.30 with ESQL/C Libraries

  1. In order to recompile 7.2x applications with 9.2 ESQL/C, customers need to install ClientSDK 2.30. The command "installclientsdk" is used to install clientsdk product that contain 9.2 ESQL/C (and other client products). Like the current "installesql", "installclientsdk" will overwrite all files in an existing 7.2x ESQL/C installation. There is no -u option for installclientsdk.

C. Client SDK File Size Increase

Due to the addition of several new Locale files, the size of the 2.30 Client SDK and I-Connect unix products have increased. For instructions on removing unwanted locale files from the GLS Library, please reference the Informix Guide to GLS Functionality, Version 9.1, Appendix A, Managing GLS Files. This guide is available in the Answers On Line CD-ROM, and at:

http://www.informix.com/answers/.


VII. Fixed Problems

A. Error Message Change for chkenv Utility

The chkenv utility returns an error message if it finds a bad environment-variable entry in the shared-environment configuration file. Informix products ignore all lines in the environment configuration file, starting at the point of the error. When this error occured in previous releases, you received the following error message:

When this error occurs in this release, you receive the following error message:

Note: The chkenv utility only checks for the validity of the environment-variable name (not the values set) from the shared-environment configuration file that comes with the same release. If the environment variable is then passed to a server that is running a previous release, that server will consider the environment variable invalid and will ignore it.

For example, the 7.2 release includes a new variable: DB_LOCALE. The 7.2 chkenv utility will recognize this environment variable when it finds it in the shared-environment configuration file. However, if the environment variable is then sent to a 7.1 server, that server will ignore the variable, as the variable is not included in the shared-environment configuration file for Version 7.1.

See individual product release notes for problems that are specific to each product.


VIII. Client-Server Testing

The Client SDK 2.40 products have been tested with the following database servers:


INFORMIX-Client SDK 2.40
Version 2.40 , 10/15/99
Copyright © 1999, Informix Software, Inc. All rights reserved