================================= RELEASE NOTES FOR INFORMIX-Client SDK 2.02.UC4 PRODUCT RELEASE DATE: 12 Oct 1998 ================================= Release notes for client products available as part of the INFORMIX- Client SDK 2.0 are in the following files: CLIREL_2.8 INFORMIX-CLI Release Notes CPPREL_2.5 C++ Object Interface Release Notes ESQLCREL_9.1 INFORMIX-ESQL/C Release Notes GLSAPIREL_3.0 INFORMIX-GLS Release Notes JAVAREL_1.1 Java API Release Notes ODBCREL_3.0 INTERSOLV DataDirect ODBC Driver Release Notes The following is a quick summary of the Client SDK installation process including new changes in this release. For a complete description of all command line options of all installation scripts, please refer to your Installation Guide. In the following, I-CONNECT 2.02 refers to the conn tar file in the Client SDK 2.02 bundle, and ClientSDK 2.02 refers to the clientsdk tar file in the Client SDK 2.02 bundle. (1) If I-CONNECT 2.02 is NOT installed on top of an existing 7.2x ESQL/C installation, (a) both "installconn" and "installconn -u" will install 2.02 I-CONNECT exactly the same as the current 2.01 I-CONNECT "installconn"; (Note, the -u option is only available in UNIX. NT ESQL/C does not need this option.) (b) any existing 7.2x UNIX ESQL/C (and 7.23 NT ESQL/C) applications can use this installed I-CONNECT without relinking or recompilation. If recompilation is not performed, only 7.2x level functionality and some bug fixes will be available. To recompile and get new functionality, they would need the development version of the product (ClientSDK 2.02 tar file). (2) If I-CONNECT 2.02 is installed on top of an existing 7.2x ESQL/C installation, (a) "installconn" will install 9.14 ESQL/C shared libraries, and either KEEP the 7.2x shared libraries or REPLACE them with the 9.14 ones. The script "installconn" will ask you whether you want to overwrite the existing shared libraries or not. If the existing shared libraries are chosen NOT to be overwritten, then (a.1) existing 7.2x applications will continue to use the existing 7.2x shared libraries, (a.2) existing 9.1x applications can use the 9.14 shared libraries. If the existing shared libraries are overwritten, then the effect is the same as (b)(a.1) below. (b) "installconn -u" will install 9.14 UNIX ESQL/C shared libraries, and REPLACE 7.2x shared libraries with the 9.14 ones. (Actually, only the links are updated.) (a.1) Both existing 7.2x (and 9.1x) applications will then use the 9.14 shared libraries, and they should all work correctly. (The 7.2x shared libraries will not be accessible by the ESQL/C preprocessor.) No relinking or recompilation is required. However, only 7.2x level functionality and some bug fixes will be available if an 7.2x application is not recompiled. (3) Installing ClientSDK 2.02 (a) If ClientSDK 2.02 is installed on top of an existing 7.2x ESQL/C installation, it will always REPLACE 7.2x shared libraries with the 9.14 ones. If you intend to continue using the 7.2x ESQL/C preprocessor or shared libraries, ClientSDK 2.02 should be installed in a separate directory. (b) Regardless whether ClientSDK 2.02 is installed on top of an existing 7.2x ESQL/C or not, an existing 7.2x application CAN use the 9.14 ESQL/C shared libraries in this installation without relinking or recompilation. (4) In order to recompile 7.2x applications with 9.14 ESQL/C, customers need to install ClientSDK 2.02. The command "installclientsdk" is used to install clientsdk product that contains 9.14 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. (5) Version Checking As of version 2.02, installclientsdk and installconn scripts contains version checking. These installation scripts check for previously installed versions of the ClientSDK before the script proceeds. The installation script proceeds with installation only if any previous version is older. The installconn script checks both the version number for ClientSDK and Informix-Connect so that an older version of Informix-Connect is not installed over a newer ClientSDK. However, installclientsdk only checks the version of the ClientSDK. To run the installation scripts: (a) Copy the clientsdk.tar or conn.tar file to your current /vobs/tristarm/sqldist (b) Tar the tar file: tar xvf [clientsdk.tar | conn.tarr] (c) Run the installclientsdk or installconn script with either the -i or -o option. If you want to override version-checking, you can invoke the installclientsdk or installconn scripts with an option, -f, to force installation. (d) If you are installing 2.02 over a version older than 2.02, you can use a utility, check_version, to determine the current installed version number. For example: check_version [csdk | conn] Note: As of version 2.02, installation can be done by user root or informix. (6) ODBC Products Client SDK provides the following ODBC products: INFORMIX-CLI, Version 2.8 -------------------------- This product provides a seamless upgrade for INFORMIX-CLI 2.7 customers. It provides the following advantages: * ODBC 2.5 feature compliance. * Support for INFORMIX-Dynamic Server with the Universal Data Option extended data types. Available Platforms: * Windows NT 3.51 or higher * Windows 95 * Sun SPARC Solaris 2.4 or higher INTERSOLV DataDirect ODBC Driver, Version 3.02 ---------------------------------------------- This product provides a seamless upgrade for INFORMIX-CLI 2.5 customers. It provides the following advantages: * ODBC 3.0 feature compliance. * Many known issues with the INFORMIX-CLI 2.5 product have been resolved in this version of the INTERSOLV DataDirect ODBC Driver. Available Platforms: * Windows NT 3.51 or higher * Windows 95 * Sun SPARC Solaris 2.5 or higher * AIX 4.1 or 4.2 * HP-UX 10.10 or 10.20 IMPORTANT: If you are upgrading to the Client SDK 2.02 from an earlier version of the Client SDK, and you already use INTERSOLV DataDirect ODBC Driver, Version 3.01, then the new version of the INTERSOLV DataDirect ODBC Driver will be installed in addition to, not as a replacement for, the 3.01 version. Therefore, you do not need to use the new version; it is an option. If you choose to use the new version, refer to the release notes for the INTERSOLV DataDirect ODBC Driver for instructions on upgrading DSNs to use the new version.