 
 
Informix Online Documentation <http://www.informix.com/documentation/>

------------------------------------------------------------------------

Licensed Materials - Property of IBM
"Restricted Materials of IBM"

IBM Informix Client SDK 2.80
© Copyright IBM Corporation 2002 All rights reserved.

------------------------------------------------------------------------

RELEASE NOTES FOR
IBM Informix Client SDK
Date: 6/06/2002
Version: 2.80

------------------------------------------------------------------------


      Table of Contents

   1. Overview
   2. Configuration Requirements
   3. Client Server Testing
   4. Client API Component & Versions
   5. Example Files
   6. Known Problems
   7. CSDK Install on Windows with ISWI2.0
   8. New Features

 

 
------------------------------------------------------------------------


     I.  Overview

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:

    *   System administrators who install IBM Informix database servers
    *   Database administrators who control access to IBM Informix databases
    *   Developers who write applications using Client SDK, Version 2.8


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



 

Filenames

Product

CPPREL.HTML, CPPREL.TXT 

IBM Informix-Object Interface for C++

ESQLCREL.HTML, ESQLCREL.TXT 

IBM Informix ESQL/C

GLSAPIREL.HTML, GLSAPIREL.TXT 

IBM Informix GLS

INFODBCREL.HTML, INFODBCREL.TXT

IBM Informix ODBC Driver

DEFECTS.HTML, DEFECTS.TXT

Fixed and Known Defects for all CSDK components


------------------------------------------------------------------------


    II.  Configuration Requirements

    * Client SDK and IConnect which are bundled with ISWI 2.0, will
      successfully install in a directory of upto 215 characters. 
    * You must not install the 32-bit version and the 64-bit version of
      the Client SDK in the same INFORMIXDIR .

------------------------------------------------------------------------


     III.  Client-Server Testing

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

    *   Informix Dynamic Server, Version 5.10
    *   Informix Dynamic Server, Versions 7.3x
    *   Informix Dynamic Server with Advanced Decision Support and
      Extended Parallel Options, Version 8.21 and Informix Extended
      Parallel Server, Version 8.3x
    *   Informix Dynamic Server 2000, Versions 9.2x and 9.3x
    *   INFORMIX -SE Version 7.25

------------------------------------------------------------------------


     IIV.  Client API Component & Versions

Component

Version

ESQL/C

9.52

ODBC driver  (formerly CLI)

3.81

OLE-DB (Only On Windows)

2.80

Object Interface for C++ (LIBC++)

2.83

Client LIBMI  (LIBDMI)

2.42

Setnet32 (Only On Windows)

9.52

GLS

3.13


------------------------------------------------------------------------


     V.  Example Files

Some of the Client  SDK files, such as  ESQL/C ,  ODBC and OLEDB ,
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. Bug #123969

PRODUCTS ON WINDOWS PLATFORMS WILL USE ENVIRONMENT VARIABLE SETTINGS AT
A HIGHER PRECEDENCE THAN THE CURRENT USER'S REGISTRY OR THE INETLOGIN STRUCT

Workaround : 

For Win32 client, do not set Informix specific environment variables in
the Windows OS environment. If these variables are set in the OS
environment, your applications will not be able to override them. In
other words, your applications will not be able to use the values you
specified using the setnet32 utility or set via calls to ifx_putenv();
these values will be picked up from the OS environment instead. 

 


      B. Using ESQL/C Libraries

In the following notes, I-CONNECT 2.80 refers to the conn.tar file in
the Client  SDK Version 2.8 bundle, and ClientSDK 2.80 refers to the
csdk.tar file in the Client  SDK 2.80 bundle.

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

    *   Both "installconn" and "installconn -u" will install 2.80
      I-CONNECT exactly the same as the current I-CONNECT "installconn".
      The -u option is only available on  UNIX. Windows  NT  ESQL/C does
      not need this option.
    *   Any existing Version 7.2x  UNIX  ESQL/C (and Version 7.23
      Windows  NT  ESQL/C) applications can use this installed I-CONNECT
      without relinking or recompilation. If recompilation is not
      performed, only Version 7.2x level functionality and some bug
      fixes will be available.

To recompile and get new functionality, you need the development version
of the product (CSDK 2.80 tar file).

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


    *   "installconn" will install 9.52  ESQL/C shared libraries, and
      either KEEP the 7.2x shared libraries or REPLACE them with the
      9.52 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:
          *   Existing 7.2x applications will continue to use the
            existing 7.2x shared libraries.
          *   Existing 9.1x applications can use the 9.52 shared
            libraries. If the existing shared libraries are overwritten,
            then the effect is the same as the effect caused by
            replacing 7.2x shared libraries with 9.52 shared libraries
            (see next bullet).
    *   "installconn -u" will install Version 9.52  UNIX  ESQL/C shared
      libraries and REPLACE 7.2x shared libraries with the 9.52 shared
      libraries. (Actually, only the links are updated.)

Both existing 7.2x (and 9.1x) applications will then use the Version
9.52 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 a 7.2x application
is not recompiled.

   1.   Installing ClientSDK Version 2.8 with  ESQL/C Libraries


    *   If ClientSDK Version 2.8 is installed on top of an existing
      Version 7.2x  ESQL/C installation, it will always REPLACE Version
      7.2x shared libraries with the Version 9.52 shared libraries. If
      you intend to continue using the Version 7.2x  ESQL/C preprocessor
      or shared libraries, ClientSDK Version 2.8 should be installed in
      a separate directory.
    *   Regardless of whether ClientSDK Version 2.8 is installed on top
      of an existing Version 7.2x  ESQL/C or not, an existing Version
      7.2x application CAN use the Version 9.52  ESQL/C shared libraries
      in this installation without relinking or recompilation.

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


    ------------------------------------------------------------------------


     VII.  CSDK Installation on windows with ISWI2.0


      MsiExec and Installation Properties

Windows Installer Installation,repair,and uninstallation can be
activated from the Command line using the utility MsiExec with
appropriate command-line options.MsiExec is a part of Windows 2000, and
InstMsi Installs


MsiExec into <SystemFolder> on other Systems.

For example, here are some common installer actions and ther
corresponding command-
line options.

Install:                                     Msiexec.exe  /i    
D:\Example.msi
Uninstall:                                 MsiExec.exe  /x   D:\Example.msi
Install to Network:                  MsiExec.exe  /a   D:\Example.msi
Repair:                                    MsiExec.exe  /f   
D:\Example.msi
Advertise (to machine):          MsiExec.exe  /jm  D:\Example.msi
Advertise ( to current user):   MsiExec.exe  /ju   D:\Example.msi

MsiExec also accepts a product code instead of a path to an MSI Package.

public properties (those with upper-case names) of an installation
program can be set at the command line. For example, the default user
and company names displayed in the Identification panel of an
installation are taken from the target system's registry and stored in
the public installer properties USERNAME and COMPANYNAME. To set the
user and company names at the command line, we enter a command similar
to the following. (Note that property names are case-sensitive, and that
we enclose a property value in quotation marks if the value contains any
spaces.)

MsiExec.exe  /i   ?<.msi file path name>?   USERNAME=Default   
COMPANYNAME="<company name"

Similarly user can specify an alternative value for INSTALLDIR on the
command line

MsiExec.exe  /i  ?<.msi file path name>?  INSTALLDIR="<NewLocation path>"

An administration can prevent a product from being uninstalled by
setting the ARPNOREMOVE property  to 1 at the command line.Similarly,
setting ARPNOMODIFY to 1 prevents users from modifying installed files,
and setting ARPNOREPAIR  to  1 disables the Repair button in the Windows
2000 Add/Remove Programs Control panel applet.


      Silent Installation

Refer Informix Client Products Installation Guide for Unix,Linux And
Windows from the url


 

http://www.informix.com/answers/english/docs/25sdk/6638.pdf
<http://www.informix.com/answers/english/docs/25sdk/6638.pdf> on page 2-9.

Logging :-
=======

We can create a log file at setup runtime using the /L argument to
MsiExec. For example to store all error and warning messages in a text
log file, we can use the following command line, which passes the e and
w arguments to /L

MsiExec.exe  /i  "<.Msi file path name"   /Lew  D:\install.log

To log every action performed by the setup program,the command is

MsiExec.exe  /i  ".Msi file path name"  /L*v  D:\install.log

Note:- By default, MsiExec creates a log file in a users' Temp folder
only if an error occurs.


      Advertise Installation

Refer Informix Client Products Installation Guide for Unix,Linux And
Windows from the url


 

http://www.informix.com/answers/english/docs/25sdk/6638.pdf on page no 2-10


      Uninstallation of Client SDK

Refer Informix Client Products Installation Guide for Unix,Linux And
Windows from the url

http://www.informix.com/answers/english/docs/25sdk/6638.pdf on page 2-11


      Uninstallation of Client SDK from Command line

Refer Informix Client Products Installation Guide for Unix,Linux And
Windows from the url


 

http://www.informix.com/answers/english/docs/25sdk/6638.pdf
<http://www.informix.com/answers/english/docs/25sdk/6638.pdf> on page 2-12


      Modify the Installation

Refer Informix Client Products Installation Guide for Unix,Linux And
Windows from the url 
http://www.informix.com/answers/english/docs/25sdk/6638.pdf on page 2-12


      Repair the Installation

Refer Informix Client Products Installation Guide for Unix,Linux And
Windows from the url


 

http://www.informix.com/answers/english/docs/25sdk/6638.pdf
<http://www.informix.com/answers/english/docs/25sdk/6638.pdf> on page 2-13
 

------------------------------------------------------------------------


     VIII.  New Features

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

ODBC 3.81
     Support SQL QUERY TIME OUT
Performance Enhancement of OLE DB provider
Upgrade to GLS 3.13



 

------------------------------------------------------------------------

© Copyright IBM Corporation 2002 All rights reserved

