Client Install Guide

Informix Product Family Informix Client Software Development Kit
Version 3.70
IBM Informix Client Products Installation Guide
GC27-3560-02
Informix Product Family Informix Client Software Development Kit

Version 3.70
IBM Informix Client Products Installation Guide
GC27-3560-02
Note Before using this information and the product it supports, read the information in Notices on page D-1.
Edition This edition replaces GC27-3560-01. This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this publication should not be interpreted as such. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright IBM Corporation 1996, 2011. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
About this Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v What's new in installation for IBM Informix client products, Version 3.70 . . . . . . . . . . . . . . . v Client SDK Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi IBM Data Server Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Differences between .NET Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Additional documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Compliance with industry standards . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Syntax diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv How to read a command-line syntax diagram . . . . . . . . . . . . . . . . . . . . . . xvi Keywords and punctuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Identifiers and names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii How to provide documentation feedback. . . . . . . . . . . . . . . . . . . . . . . . . xviii
Part 1. Installing Client Products on UNIX, Linux, and Mac OS X

Chapter 1. Preparing to Install Client SDK and IBM Informix Connect on UNIX, Linux, and Mac OS X Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Overview of Client SDK and Informix Connect Installation . . . Determine Location . . . . . . . . . . . . . . . . Check Online Files. . . . . . . . . . . . . . . . . Determine Installation Order . . . . . . . . . . . . . Prepare the Environment (UNIX, Linux) . . . . . . . . . Creating the Group informix and User informix (UNIX, Linux) . Configure the Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-1 1-2 1-2 1-3 1-3 1-4
Chapter 2. Installing Client SDK and Informix Connect on UNIX and Linux Systems
Installation System Requirements for UNIX and Linux. . . . . . . The Informix Client Installation Application . . . . . . . . . . Client Products Installation Application Commands (UNIX and Linux) Installing Client Products in Console Mode . . . . . . . . . Installing Client Products in GUI Mode . . . . . . . . . . . Client Installation Log Files (UNIX and Linux) . . . . . . . . Alternative Installation Methods . . . . . . . . . . . . . . Performing a Silent Client Product Installation on UNIX and Linux . Extracting and Redistributing Client Products with Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1
2-1 2-1 2-1 2-2 2-3 2-3 2-4 2-4 2-5
Chapter 3. Installing Client SDK and Informix Connect on Mac OS X . . . . . . . . . 3-1 Chapter 4. Uninstalling Client SDK and Informix Connect on UNIX, Linux, and Mac OS X Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Using the Client Product Uninstallation Applications (UNIX, Linux, and Mac OS X) . . . . . Uninstalling Client SDK or Informix Connect in Console Mode (Default Mode) . . . . . Uninstalling After Using the Extraction Application with Command-Line Script (UNIX, Linux) . . . . . . . . . . . . . . . . . 4-1 . 4-1 . 4-2
Part 2. Installing Client Products on Windows Systems

Chapter 5. Preparing to Install Client SDK and Informix Connect on Windows Systems 5-1
System Requirements . . . . Database Server Requirements . Protocol Requirements . . . C Compiler Requirements . . Installation Location and Order
Copyright IBM Corp. 1996, 2011
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
5-1 5-1 5-1 5-1 5-2
iii
Informix .NET Provider (Windows) .
. 5-2
Chapter 6. Installing Client SDK and Informix Connect on Windows Systems . . . . . 6-1
About Client Product Installation on Windows . . . . . . . . . Installing Client SDK or Informix Connect in GUI Mode (Windows) . Performing a Silent Client Product Installation on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 . 6-1 . 6-2
Chapter 7. Post-Installation Client Product Tasks on Windows Systems . . . . . . . 7-1

Configuring IBM Informix Client Products on Windows Setting the Environment Variables . . . . . . Setting Database Server Information . . . . . . Setting Host Information. . . . . . . . . . Overriding Information . . . . . . . . . . Configuring OLE DB Provider . . . . . . . . . Common Installation Problems . . . . . . . . Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 7-1 7-2 7-3 7-4 7-4 7-5
Chapter 8. Uninstalling Client SDK on Windows Systems
. . . . . . . . . . . . . 8-1
. . . . . . . . . . . . . . . . . 8-1 . 8-1
Uninstalling or modifying Client SDK and Informix Connect in GUI mode (Windows) . Removing a Client SDK or Informix Connect Installation Using the Command Line . .
Part 3. Appendixes
Appendix A. Environment Variables . . . . . . . . . . . . . . . . . . . . . . . A-1
In this Appendix . . . Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 . A-1
Appendix B. Distribute Your IBM Informix Client Applications (Windows). . . . . . . B-1

In This Appendix . . . . . . . . . . . . . . . . Distribute IBM Informix Client Applications and Components . Client Runtime Component Redistribution Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 . B-1 . B-1
Appendix C. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Accessibility features for IBM Informix products Accessibility features . . . . . . . . . Keyboard navigation . . . . . . . . . Related accessibility information . . . . . IBM and accessibility . . . . . . . . . Dotted decimal syntax diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 C-1 C-1 C-1 C-1 C-1
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
iv
Client Products Installation Guide
Introduction
This introduction provides an overview of the information in this publication and describes the conventions that it uses.
About this Publication

This publication explains how to install IBM Informix Client Software Development Kit (Client SDK) and IBM Informix Connect by using stand-alone installation applications instead of the Informix software bundle that includes the database server product. This publication is written for database administrators and software engineers who are installing IBM Informix client products, and assumes that you are familiar with the operating system on your computer. Important: See the IBM Informix JDBC Driver Programmer's Guide for information about installation of the JDBC Driver.
What's new in installation for IBM Informix client products, Version 3.70
This publication includes information about new features and changes in existing functionality. For a complete list of what's new in this release, see the release notes or the information center at http://publib.boulder.ibm.com/infocenter/idshelp/v117/ topic/com.ibm.po.doc/new_features.htm.
Table 1. What's New in IBM Informix Client Products Installation Guide for Version 3.70.xC3 Overview Client SDK includes the DB-Access utility The DB-Access utility is included in IBM Informix Client Software Development Kit (Client SDK), version 3.70. The utility is installed with Client SDK or IBM Informix Connect only on platforms that support IBM Informix11.70. The DB-Access utility provides a user interface for typing, executing, and debugging SQL statements. You can use this utility to test applications before you release them for use in a production environment. Client SDK includes ConnectTest utility The ConnectTest utility is included in IBM Informix Client Software Development Kit (Client SDK), Version 3.70. The utility is installed with Client SDK or Informix Connect on the Windows 32-bit and 64-bit platforms. The Connect.Test utility is a user interface that can execute SQL queries and display the resulting data of the executed SQL query. Reference See the DB-Access utility information in the Client SDK Components on page vi.
See the ConnectTest utility information in the Client SDK Components on page vi.
Table 2. What's New in IBM Informix Client Products Installation Guide for Version 3.70.xC1 Overview Changes to installation commands Some installation commands changed to take advantage of new and changed functionality and to improve consistency across products and operating systems. You can remove specific products by using the following commands, which are in new subdirectories relative to the root directory: v uninstall/uninstall_clientsdk/uninstallclientsdk v uninstall/uninstall_connect/uninstallconnect Reference For information about how to install or uninstall Informix client products with the Informix software bundle installation and uninstallation applications, see the IBM Informix Installation Guide for Windows or the IBM Informix Installation Guide for UNIX, Linux, and Mac OS X. For commands to install Client SDK or Informix Connect individually, see Client Products Installation Application Commands (UNIX and Linux) on page 2-1, Chapter 6, Installing Client SDK and Informix Connect on Windows Systems, on page 6-1, or Chapter 3, Installing Client SDK and Informix Connect on Mac OS X, on page 3-1. For commands to uninstall Client SDK or Informix Connect individually, see Chapter 4, Uninstalling Client SDK and Informix Connect on UNIX, Linux, and Mac OS X Systems, on page 4-1 or Chapter 8, Uninstalling Client SDK on Windows Systems, on page 8-1 For commands to install or uninstall the IBM Informix JDBC Driver, see the IBM Informix JDBC Driver Programmer's Guide. New editions and product names IBM Informix Dynamic Server editions were withdrawn and new Informix editions are available. Some products were also renamed. The publications in the Informix library pertain to the following products: v IBM Informix database server, formerly known as IBM Informix Dynamic Server (IDS) v IBM OpenAdmin Tool (OAT) for Informix, formerly known as OpenAdmin Tool for Informix Dynamic Server (IDS) v IBM Informix SQL Warehousing Tool, formerly known as Informix Warehouse Feature For more information about the Informix product family, go to http://www.ibm.com/software/data/informix/.
Client SDK Components

Client SDK allows you to develop and run client applications. The following table describes the components of Client SDK. Applications that run on client computers require IBM Informix Connect to access database servers. Informix Connect is a runtime connectivity product composed of runtime libraries that are included in Client SDK.
vi
Table 3. Client SDK Components Component IBM Informix .NET Provider (Windows only) Description The IBM Informix .NET Provider is a .NET assembly that lets .NET applications access and manipulate data in IBM Informix databases. It does this by implementing several interfaces in the Microsoft .NET Framework that are used to access data from a database. Using the IBM Informix .NET Provider is more efficient than accessing the IBM Informix database through either of these two methods: v Using the Microsoft .NET Framework Data Provider for ODBC along with the IBM Informix ODBC Driver v Using the Microsoft .NET Framework Data Provider for OLE DB along with the IBM Informix OLE DB Provider For more information, see IBM Informix .NET Provider Reference Guide. Documentation Viewer Informix ESQL/C with XA support The viewer lets you see the release and machine notes in text format. An SQL embedded-language product that is used to create custom C applications. For more information, see the IBM Informix ESQL/C Programmer's Manual. The finderr utility on UNIX systems and the Informix Error Messages utility on Windows systems IBM Informix Object Interface for C++ These utilities enable you to obtain information about error messages, including corrective actions, that are specific to IBM Informix.
A C++ interface to develop object-oriented client applications for use with all IBM Informix database servers and client-side value objects for IBM Informix For more information, see the IBM Informix Object Interface for C++ Programmer's Guide.
IBM Informix GLS (Global Language Support)
An interface that allows IBM Informix products to use different locales that have defined conventions for a particular language, culture, or code set. For more information, see the IBM Informix ESQL/C Programmer's Manual and the IBM Informix GLS User's Guide.
IBM Informix ODBC Driver with MTS support
An IBM Informix implementation of the Open Database Connectivity (ODBC) 3.0 Level 1+ standard that supports Microsoft Transaction Server (MTS). This driver contains extensibility support for IBM Informix. For more information, see the IBM Informix ODBC Driver Programmer's Manual.
IBM Informix OLE DB Provider (Windows only)
A client-side, native OLE DB provider that implements full functionality for base-level providers and contains extensibility support for IBM Informix. For more information, see the IBM Informix OLE DB Provider Programmer's Guide.
Introduction
vii
Table 3. Client SDK Components (continued) Component The ILogin utility (Windows only) Description The ILogin Demo utility lets you quickly test the connection to IBM Informix. Click File > Run then enter the IBM Informix connection parameters. You must create the target database before you connect to it. IBM Informix Password Communications Support Module for client applications. Password CSM must also be installed on the Informix database server to which the client will connect. To verify that your Informix database server supports this feature, see the IBM Informix Administrator's Guide. The Connection Manager is a daemon utility that monitors the workload and status of all nodes in a high-availability cluster. This utility can direct connection requests for client applications to the appropriate server in the cluster and perform automatic server failover when the primary node goes down. The DB-Access component of CSDK is the same utility that is delivered with the IBM Informix server version 11.70.xC3, providing a standalone client command-line tool that can directly access an IBM Informix database instance. This dbaccess client supports the same user interface and functionality as the dbaccess server utility. The ConnectTest utility lets you test the connection to the IBM Informix server. You can start the utility from the shortcut in the Start menu or from the $INFORMIX/bin directory. The utility populates the server details from the registry registered by the Setnet32 utility. You can manually edit the utility to connect to other servers not listed in the registry, which does not modify the registry entry. The utility shows the resulting data of the executed SQL query.
Password CSM
Connection Manager
DB-Access
The ConnectTest utility (Windows only)
Note: Beginning with Client SDK Version 3.50.xC6, IBM Database Add-Ins for Visual Studio is no longer installed with Client SDK or Informix Connect. IBM Database Add-Ins for Visual Studio is available for download at: https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swgdaivs. The latest version of IBM Database Add-Ins for Visual Studio supports only the Data Server .NET Provider and does not support Client SDK Informix .NET Provider. Information about using the add-ins with the Client SDK Informix .NET Provider is available at: http://www-933.ibm.com/support/fixcentral/. Windows only: Client SDK and IBM Informix Connect packages include the Setnet 32 utility for configuring client products. Each package might include online help, example programs, and support programs.
IBM Data Server Driver

After completing an IBM Informix product installation in GUI or console mode on most operating systems, you must select whether to install the IBM Data Server Driver Package. If you select to install the driver, a separate, short installation application starts. If you do not install the driver during Informix product installation, you can install the driver separately later.
viii
The IBM Data Server Driver Package enables you to use IBM Data Server .NET Provider to develop .NET applications with Informix software. The IBM Data Server .NET Provider has several advantages including: v Better support for web application development in IBM Database Add-Ins for Visual Studio v Support for .NET framework 3.0, 3.5 v Support for LINQ, Silverlight, and AJAX development v ASP.NET dynamic data support v ADO.NET Entity Data Modeling (EDM) support IBM Data Server Driver Package installation does not affect an existing installation of the IBM Informix .NET Provider, which is also included in the Client SDK installation. You can use either or both of the .NET Providers. For more information about the differences between the Data Server .NET Provider and the Informix .NET Provider, see Differences between .NET Providers.
Differences between .NET Providers

There are runtime differences between the IBM Data Server .NET Provider and the IBM Informix .NET Provider. Knowing these differences will help you understand how each provider might affect existing applications and to select the provider that is right for your applications. Both providers are available as part of the Client SDK (CSDK) for Informix. For more information about these .NET Providers, see the IBM Data Server Provider for .NET Programmers Guide, Informix Edition or the IBM Informix .NET Provider Reference Guide. The following sections describe specific differences between the .NET providers.
IBM Informix .NET Provider

The IBM Informix .NET Provider, sometimes referred to as the CSDK .NET provider, works with only the Informix database server and internally uses the SQLI protocol to communicate with Informix. The Informix .NET Provider is no longer being enhanced for new .NET APIs.
IBM Data Server .NET Provider

The IBM Data Server .NET Provider, sometimes referred to as the Common .NET provider, is the next generation of the .NET provider for application development. This .NET provider includes a number of capabilities, especially in the area of web application development, making it the preferred .NET provider for new client development. The Data Server .NET Provider works with several different IBM data servers, including Informix, DB2 for Linux, UNIX, and Windows, and U2, and uses the DRDA protocol. This provider is composed of two different .NET provider assemblies that are designed for very specific application developer requirements: IBM.Data.DB2.dll Although the name of the provider indicates DB2, this is in fact the single .NET provider for IBM data servers including Informix and DB2. This is
Introduction
ix
the recommended assembly for new application development for Informix Version 11.10 or later, and this is the preferred .NET provider. IBM.Data.Informix.dll This .NET provider assembly was created to help migrate existing .NET applications that were developed by using the Informix .NET Provider to use the latest DRDA protocol. This assembly works with Informix Version 11.10 or later. This assembly includes additional support for some of the legacy Informix client features and is targeted only for .NET application development for Informix.
Comparison of supported features

There are several major differences between the features that are supported by the IBM Informix .NET provider and the IBM Data Server .NET Provider. Many of the features supported by the IBM Data Server .NET Provider are not supported by the IBM Informix .NET Provider. The following table shows these differences:
Table 4. Compare features supported by Informix .NET Provider and IBM Data Server .NET Provider Feature Protocol support Informix server support LOB (BLOB & CLOB) column size limit Support for .NET framework 3.0, 3.5 IBM Informix .NET Provider SQLI Any supported Informix version 4 TB No Supports 1.1 and 2.0 frameworks. Limited VSAI windows application support. No No No No IBM Data Server .NET Provider DRDA Informix v11.10 or later ONLY 2 GB Yes Supports 2.0, 3.0, and 3.5 frameworks. Yes Yes Yes Yes
Support for LINQ (Entity Framework) Silverlight and AJAX development support ASP.NET dynamic data support ADO.NET Entity Data Modeling (EDM) support Visual Studio Tools for Office (VSTO) development using EDM
No
Yes
VSAI support for Visual No Studio 2008, Web application development support, WPF and WWF enhancements
Yes
Table 4. Compare features supported by Informix .NET Provider and IBM Data Server .NET Provider (continued) Feature VSAI Designers to create tables, procedures, functions and triggers, run procedures and functions IBM Informix .NET Provider No IBM Data Server .NET Provider Yes
Unsupported keywords in the ConnectionString property

There are several connection string keywords that are not supported by the IBM Data Server .NET Provider. For example: v DB_LOCALE v CLIENT_LOCALE v EXCLUSIVE
Connection pooling settings

In the IBM Informix .NET Provider, the Connection Lifetime attribute specifies how long a connection can remain open. In the IBM Data Server .NET Provider, the Connection Lifetime attribute specifies the number of seconds that the connection can remain open and idle in the pool.
Server keyword in the ConnectionString property

In the IBM Informix .NET Provider, the SERVER keyword should be used to specify the INFORMIXSERVER name as setup in the SetNet utility. In the IBM Data Server .NET Provider, the SERVER keyword should be specified in the format <hostname>:<port_number>, where <hostname> is the machine name of the instance and <port_number> is the port on which the instance is listening.
Database keyword in the ConnectionString property

With the IBM Informix .NET Provider, you can connect to a server without specifying a database. With the IBM Data Server .NET Provider, database is a mandatory attribute. The IBM Informix .NET Provider allows specifying the value for the Database attribute in the format dbname@server. The IBM Data Server .NET Provider does not support this format.
String values in quotation marks in the ConnectionString property

The IBM Informix .NET Provider supports database, server, and password keyword values in quotation marks.
Introduction
xi
Applications that use the IBM Data Server .NET Provider can specify values in quotation marks for the database and password keywords only when specifying an alias for a catalog connection.
IfxConnection.ServerType property
For this property, the IBM Informix .NET Provider returns the value Informix. The IBM Data Server .NET Provider returns the value that is received from the database server to which it is connected. For example, the provider connected to an Informix database server installed on a UNIX 64-bit system might return IDS/UNIX64.
Unsupported data types in SQL statements

The IBM Data Server .NET Provider does not allow access to the LIST, MULTISET, SET, or ROW data types because the Informix DRDA server does not support these types. With the IBM Informix .NET Provider, you can select and return the values from the LIST, MULTISET, and ROW data types.
BYTE and TEXT data types

The IBM Data Server .NET Provider maps both Byte and BLOB data types to the IfxBlob data type. When binding an IfxBlob object as a parameter, applications must use the ::byte clause after the parameter marker. This clause indicates that the IfxBlob value corresponds to a byte column. Without the ::byte clause, a conversion error is returned. The IBM Data Server .NET Provider maps both Text and CLOB data types to the IfxClob data type. When binding an IfxClob object as a parameter, applications must use the ::text clause after the parameter marker. This clause indicates that the IfxClob value corresponds to a text column. Without the ::text clause, a conversion error is returned.
DB2Parameter clobParam; clobParam.IfxType = IfxType.Clob; ... cmd.CommandText = "CALL textSP(?::text)"; --cmd.ExecuteNonQuery();
Supported data types

The following table compares the more unusual Informix data types and how each .NET provider supports those data types.
Table 5. Differences between .NET provider support for unusual Informix data types Informix Data Type CLOB, BLOB Collection Interval DayToFraction IBM Informix .NET Provider Supported Supported Supported. This type must be read as a string. IBM Data Server .NET Provider Limited Support. The size limitation is 2 GB. Not supported Not supported
xii
Table 5. Differences between .NET provider support for unusual Informix data types (continued) Informix Data Type IntervalMonth LIST MONEY MULTISET ROW SET IBM Informix .NET Provider Supported Supported Supported Supported Supported Supported IBM Data Server .NET Provider Not supported Not supported Money will be treated as decimal data type. Not Supported Not Supported Not Supported
Comparing classes and structures

The following table compares the differences between the .NET provider support for the data type classes and structures support.
Table 6. Differences between .NET provider support for data type classes and structures Class / Structure IfxBlob IBM Informix .NET Provider Supported IBM Data Server .NET Provider Limited Support. Some methods return a NotImplemented exception. Limited Support. Some methods return a NotImplemented exception. Not Supported Not Supported Not Supported Not Supported Limited Support. Some methods return a NotImplemented exception. Limited Support. DRDA client supports 6 digits in the fractional part of DateTime. The Informix server supports 5 digits of the fractional value. Because of this difference, the least significant digit of the fraction will be truncated. A DateTime value read from the Informix server has a 0 (zero) added to the least significant digit to match the DRDA format. This change affects applications that access the IfxDateTime type from the IBM Informix .NET Provider.
IfxClob
Supported
IfxTimeSpan IfxMonthSpan IfxSmartLOBLocator IfxSmartLOB IfxDecimal
Supported Supported Supported Supported Supported
IfxDateTime
Supported
Introduction
xiii
Stored procedure differences

With the IBM Informix .NET Provider applications can read the return value of a stored procedure or function as a ReturnValue parameter. With the IBM Data Server .NET Provider applications by default can read the return value of a stored procedure or function as a data reader. To read it as a ReturnValue parameter, applications must set the ResultSetAsReturnValue parameter to true in the IfxCommand or IfxConnection object. To read it is a ReturnValue parameter, applications must set the ResultSetAsReturnValue property to true in the IfxCommand or IfxConnection object.
IfxCommand.ExecuteScalar() method
The following query is a sample SELECT query.
Cmd.CommandText = "SELECT COUNT(*) FROM Tab";
The data type that is returned depends on the .NET provider that you use: IBM Informix .NET Provider When you use the IBM Informix .NET Provider, this query returns the count as decimal type.
Decimal count = (Decimal) Cmd.ExecuteScalar();
IBM Data Server .NET Provider When you use the IBM Data Server .NET Provider, this query returns the count as Int32.
Int32 count = (Int32) Cmd.ExecuteScalar();
IfxDataReader.GetString() method
The IBM Data Server .NET Provider does not allow the IfxDataReader.GetString() method if the underlying value is null. A null value results in an InvalidCast exception. This behavior is in contrast to the IBM Informix .NET Provider, which allows a null value and returns an empty string.
Error messages
Some error messages received by the IBM Data Server .NET Provider might differ from those received by the IBM Informix .NET Provider. For example, the IBM Informix .NET Provider has tags such as [Informix .NET provider] in the error messages. The IBM Data Server .NET Provider has just [IBM] in the error messages. Additionally, the error codes might be different for the same type of error.
Additional documentation
Documentation about this release of IBM Informix products is available in various formats. You can access or install the product documentation from the Quick Start CD that is shipped with Informix products. To get the most current information, see the Informix information centers at ibm.com. You can access the information centers and other Informix technical information such as technotes, white papers, and IBM Redbooks publications online at http://www.ibm.com/software/data/swlibrary/.
xiv
Compliance with industry standards

IBM Informix products are compliant with various standards. IBM Informix SQL-based products are fully compliant with SQL-92 Entry Level (published as ANSI X3.135-1992), which is identical to ISO 9075:1992. In addition, many features of IBM Informix database servers comply with the SQL-92 Intermediate and Full Level and X/Open SQL Common Applications Environment (CAE) standards. The IBM Informix Geodetic DataBlade Module supports a subset of the data types from the Spatial Data Transfer Standard (SDTS)Federal Information Processing Standard 173, as referenced by the document Content Standard for Geospatial Metadata, Federal Geographic Data Committee, June 8, 1994 (FGDC Metadata Standard).
Syntax diagrams
Syntax diagrams use special components to describe the syntax for statements and commands.
Table 7. Syntax Diagram Components Component represented in PDF Component represented in HTML >>---------------------Meaning Statement begins.
----------------------->
Statement continues on next line. Statement continues from previous line. Statement ends. Required item. Optional item.
>--------------------------------------------->< --------SELECT-----------+-----------------+--------LOCAL------ ---+-----ALL-------+--+--DISTINCT-----+ ---UNIQUE------
Required item with choice. Only one item must be present.
---+------------------+--+--FOR UPDATE-----+ --FOR READ ONLY-- .---NEXT---------. ----+----------------+--+---PRIOR--------+ ---PREVIOUS-----
Optional items with choice are shown below the main line, one of which you might specify. The values below the main line are optional, one of which you might specify. If you do not specify an item, the value above the line will be used as the default.
Introduction
xv
Table 7. Syntax Diagram Components (continued) Component represented in PDF Component represented in HTML .-------,-----------. V | ---+-----------------+--+---index_name---+ ---table_name--- >>-| Table Reference |->< Table Reference |--+-----view--------+--| +------table------+ ----synonym------ Meaning Optional items. Several items are allowed; a comma must precede each repetition.
Reference to a syntax segment. Syntax segment.
How to read a command-line syntax diagram

Command-line syntax diagrams use similar elements to those of other syntax diagrams. Some of the elements are listed in the table in Syntax Diagrams. Creating a no-conversion job
onpladm create job job -p project -n -d device -D database
-t
table
(1) Setting the Run Mode -S server -T target
Notes: 1 See page Z-1
This diagram has a segment named Setting the Run Mode, which according to the diagram footnote is on page Z-1. If this was an actual cross-reference, you would find this segment on the first page of Appendix Z. Instead, this segment is shown in the following segment diagram. Notice that the diagram uses segment start and end components. Setting the run mode:
xvi
l c -f d p a u n N
To see how to construct a command correctly, start at the upper left of the main diagram. Follow the diagram to the right, including the elements that you want. The elements in this diagram are case-sensitive because they illustrate utility syntax. Other types of syntax, such as SQL, are not case-sensitive. The Creating a No-Conversion Job diagram illustrates the following steps: 1. Type onpladm create job and then the name of the job. 2. Optionally, type -p and then the name of the project. 3. Type the following required elements: v -n v -d and the name of the device v -D and the name of the database v -t and the name of the table 4. Optionally, you can choose one or more of the following elements and repeat them an arbitrary number of times: v -S and the server name v -T and the target server name v The run mode. To set the run mode, follow the Setting the Run Mode segment diagram to type -f, optionally type d, p, or a, and then optionally type l or u. 5. Follow the diagram to the terminator.
Keywords and punctuation

Keywords are words reserved for statements and all commands except system-level commands. When a keyword appears in a syntax diagram, it is shown in uppercase letters. When you use a keyword in a command, you can write it in uppercase or lowercase letters, but you must spell the keyword exactly as it appears in the syntax diagram. You must also use any punctuation in your statements and commands exactly as shown in the syntax diagrams.
Identifiers and names

Variables serve as placeholders for identifiers and names in the syntax diagrams and examples. You can replace a variable with an arbitrary name, identifier, or literal, depending on the context. Variables are also used to represent complex syntax elements that are expanded in additional syntax diagrams. When a variable appears in a syntax diagram, an example, or text, it is shown in lowercase italic.
Introduction
xvii
The following syntax diagram uses variables to illustrate the general form of a simple SELECT statement.
SELECT column_name FROM table_name
When you write a SELECT statement of this form, you replace the variables column_name and table_name with the name of a specific column and table.
How to provide documentation feedback

You are encouraged to send your comments about IBM Informix user documentation. Use one of the following methods: v Send e-mail to docinf@us.ibm.com. v In the Informix information center, which is available online at http://www.ibm.com/software/data/sw-library/, open the topic that you want to comment on. Click the feedback link at the bottom of the page, fill out the form, and submit your feedback. v Add comments to topics directly in the information center and read comments that were added by other users. Share information about the product documentation, participate in discussions with other users, rate topics, and more! Feedback from all methods is monitored by the team that maintains the user documentation. The feedback methods are reserved for reporting errors and omissions in the documentation. For immediate help with a technical problem, contact IBM Technical Support. For instructions, see the IBM Informix Technical Support website at http://www.ibm.com/planetwide/. We appreciate your suggestions.
xviii
Part 1. Installing Client Products on UNIX, Linux, and Mac OS X

This section discusses preparing to install IBM Informix client products on UNIX, Linux, and Mac OS X systems, explains the installation processes, discusses post-installation tasks, and documents how to uninstall these products. Important: The following topics of this documentation explain how to install Client SDK and Informix Connect as individual products using stand-alone client installation applications. Alternatively, you can install Client SDK or Informix Connect as part of the Informix software bundle installation media. The software bundle includes both the Informix database server and client products. For information about this installation method, see the IBM Informix Installation Guide for UNIX, Linux, and Mac OS X.
Chapter 1. Preparing to Install Client SDK and IBM Informix Connect on UNIX, Linux, and Mac OS X Systems
Overview of Client SDK and Informix Connect Installation
Before you install Client SDK or Informix Connect or connect a client application to a database server, complete the preparation steps applicable to the UNIX, Linux, or Mac OS X operating system on your computer. See the IBM Informix machine notes for a list of supported UNIX, Linux, and Mac operating systems on which you can install the products. Important: The following requirements might be lower for your system, depending on the operating system and environment. The Client SDK installation requires approximately 200 MB of disk space, and the Informix Connect installation requires approximately 175 MB of disk space. The installation requires approximately 512 MB RAM. Ensure that you have 1 GB free space available in your temporary directory (/tmp by default) before installation on UNIX or Linux. This is to allow the extraction of the installation media and for running the installation program. This location can be altered by setting the IATEMPDIR environment variable to a location that contains sufficient storage before invoking the installation program. If there is insufficient space in the default temporary location, the installation program attempts to write the information into the home directory for the user's account. Attention: v The $INFORMIXDIR path, including path separators, should not exceed 200 characters. v Client SDK does not support RPM installations. Tip: Do not use back or quit as a string in the $INFORMIXDIR path or in any Informix product installation configuration settings on UNIX or Linux, including passwords.
Determine Location
Take note of media location and installation location.
Media Location
The directory where the media files are located is called $MEDIADIR. This can be on a disk device, such as a CD, or a directory on a file server where the downloaded source file is uncompressed.
Installation Location
You can install Client SDK or IBM Informix Connect on the computer on which your applications run.
1-1
IBM Informix documentation refers to the installation directory as $INFORMIXDIR. If the environment variable INFORMIXDIR is set, the default installation location is the setting in this variable. When you install Client SDK and IBM Informix Connect with the installation application, you can accept the default directory or select your own directory. To preserve product files of earlier versions, create separate directories for each version of your IBM Informix products. Attention: The $INFORMIXDIR path, including path separators, should not exceed 200 characters.
Check Online Files

The product files include online informational files that answer specific technical questions. These files are installed in the directory $MEDIADIR/doc.
Determine Installation Order

Install the database server and client products in separate directories to avoid overwriting common files and for easier installation and problem solving. Continue to the next topic if you follow this recommendation. If you are installing client products and server products in the same $INFORMIXDIR directory, use the following table as a guide to the correct order.
Table 1-1. Order for Installing Client Products and Server Products in the Same Directory Database Server Versions 5.x 7.2x 7.3x 8.5x 9.2x 9.3x 9.4 10.0 11.x Versions of Client SDK and IBM Informix Connect 2.7 and prior Database server first Database server first Database server first Client products first Database server first Database server first Client products first Client products first N/A 2.8x Database server first Database server first Database server first Client products first Database server first Database server first Database server first Database server first N/A 2.9x Database server first Database server first Database server first Client products first Database server first Database server first Database server first Database server first Database server first 3.x Database server first Database server first Database server first Client products first Database server first Database server first Database server first Database server first Database server first
You might encounter problems if you install an older product after you install a new product. For example, if you install an older version of the finderr utility, the older version overwrites the newer version and you will not have the most current
1-2
listing of error message text and corrective action. If you encounter problems with the finderr utility, see IBM Informix Error Messages. Before the Client SDK, Version 2.01 release, clients and servers shared common message files. In later versions, the common message files for the client have new names. For more information about how to rename common message files, see the Client SDK release notes. If you install more than one IBM Informix product, complete all installation procedures for one product before you start to install the next product. Do not load the files from another IBM Informix product onto your computer until you complete the current installation. Attention: If you want to use IBM Informix ODBC Driver with an existing DSN that uses IBM Informix CLI driver or INTERSOLV DataDirect ODBC Driver, see the information about the DSN Migration Utility in the release notes for IBM Informix ODBC Driver.
Prepare the Environment (UNIX, Linux)

Prepare the environment for every shell within which you install or use IBM Informix client products. To find out if you must apply patches to your computer, see the machine notes. To complete a standard installation that runs as user informix, user and group informix must exist on the operating system before installation. Installation of a root-based Informix server is dependent on these user and group accounts, so the objects are present already if there is a database server installation on the computer. You can install the client product so that it runs on the computer without root and without user and group informix privileges. To do this, you must start the installation application as any user except root. The user account that performs the non-root installation is the owner of the installation. However, you cannot perform a non-root installation of a client product in an $INFORMIXDIR directory that has a standard, root-based installation of the Informix server.
Creating the Group informix and User informix (UNIX, Linux)

Create the group informix and user informix if they do not already exist. User and group informix are required operating system objects for root-based installation. They are not required for computers hosting a non-root installation of the product. To create the group informix and user informix: 1. Log in as user root. 2. Create the group informix using the groupadd utility followed by the name of the group, in this format: groupadd n informix where n is an unused group ID greater than 100. For AIX, use the mkgroup command instead of groupadd. 3. Create the user informix using the useradd utility followed by the group (informix) and user name (informix) in this format:
Chapter 1. Preparing to Install Client SDK and IBM Informix Connect on UNIX, Linux, and Mac OS X Systems
1-3
useradd -u n -g informix informix 4. Create a password for the user informix. To do this, use the passwd utility and the following command: passwd informix 5. If you use a network, propagate the new user name to all the systems on the network that must recognize the user informix. For example, on some systems, you (or the network administrator) must run the ypmake utility. Do not add members to the group informix unless you want those members to have administrative access to the database server.
Configure the Database Server

Before you connect a client application to a database server, configure your database server environment. For more information, see the IBM Informix Installation Guide for UNIX, Linux, and Mac OS X or the IBM Informix Administrator's Guide.
1-4
Installation System Requirements for UNIX and Linux
When you install client products on UNIX and Linux systems, there are certain system requirements depending on the specific product and your method of installation. The Client SDK and Informix Connect installation methods on UNIX and Linux systems are: v Installing as part of the database server installation application included in the IBM Informix software bundle media v Installing with a stand-alone client installation application v Installing using extraction with command-line script The Client SDK installation requires approximately 200 MB of disk space, and the Informix Connect installation requires approximately 175 MB of disk space. Some installation choices require additional disk space. Some installation choices require additional disk space. The installation application informs you of the total disk space required by your setup before you copy the binary files to your host computer. Attention: In addition to the product disk space requirements , ensure that you have 1 GB free space available in your temporary directory (/tmp by default) before installation on UNIX or Linux. This is to allow the extraction of the installation media and for running the installation program. This location can be altered by setting the IATEMPDIR environment variable to a location that contains sufficient storage before invoking the installation program. If there is insufficient space present in the default temporary location, the installation program will attempt to write the information into the home directory for the user's account.
The Informix Client Installation Application

This section describes how to install Client SDK and Informix Connect in console or GUI mode. Console installation is the default mode. For other methods, see Alternative Installation Methods on page 2-4.
Client Products Installation Application Commands (UNIX and Linux)

Information about installation commands for Client SDK and Informix Connect.
Purpose
The following syntax diagram illustrates the Client SDK and Informix Connect installation commands for GUI, console, and silent modes. If you do not specify an installation mode (GUI, console, or silent), then the installation application starts in console mode. Also, the usage of the -r option to create a response file for later silent installations is shown.
2-1
Run the following commands as root user.
Syntax
gui installclientsdk installconnect -i console silent -f path_name
(1) -r path_name
-help
Notes: 1 Do not use the -r option with the silent -f option in the same command. The -r option records the configuration of a GUI or console installation. The silent -f option starts a silent installation.
Parameters
Table 2-1. Syntax elements Element path_name Purpose Restrictions
Specifies the absolute path and file name for None the response file. The response file is a customized installation properties file that you can use for silent installations elsewhere.
The following table describes the installation application options.

Table 2-2. Installation options Option installclientsdk installconnect -i gui -i console -i silent -f path_name -r path_name Meaning Install Client SDK only. Install Informix Connect only. Start the installation program in GUI mode. Start the installation in console mode. If no option is provided, installation is started in console mode by default. Start a silent installation using the response file specified in path_name. See Performing a Silent Client Product Installation on UNIX and Linux on page 2-4 for more details. Create a response file from the installation in the designated path_name location. The response file contains an installation configuration that you want to deploy in more than one location. Alternatively, you can edit a template response file that is shipped with the installation media and not record an installation. Display list of supported options and their functions.
-help
Installing Client Products in Console Mode

The following steps outline how to install client products in console mode, which is the default mode, on UNIX and Linux.
2-2
You must be root user to perform this task. Alternatively, do not log in with root-level privileges if the client products will be used with a non-root installation of the database server. When installing in console mode, especially over a network, you might have to wait a few moments for the files to extract. 1. Run the command for the product you want to install:
./installclientsdk
or
./installconnect
2. Read the software license agreement. You must accept the license terms to install the product. 3. Proceed with the different settings until you receive the message that installation is complete. 4. When the installation is complete, exit the installation application.
Installing Client Products in GUI Mode

The following procedure outlines how to install Client SDK and Informix Connect in GUI mode. You must be root user to perform this task. Alternatively, do not log in with root-level privileges if the client products will be used with a non-root installation of the database server. 1. Run the command for the product you want to install:
./installclientsdk -i gui
or
./installconnect -i gui
2. Read the software license agreement. You must accept the terms to install the product. 3. Proceed through the GUI windows until you receive the message that installation is complete.
Client Installation Log Files (UNIX and Linux)

You can find information that will help identify and resolve installation errors in the installation log files. When you install Informix products, the installation application generates log files in $INFORMIXDIR. Log files are also created if you attempt to install any of the products but the installation application does not complete successfully. The following log files are commonly generated when you run a client installation application: v $INFORMIXDIR/IBM_Informix_Client-SDK_InstallLog.log for a Client SDK installation v $INFORMIXDIR/IBM_Informix_Connect_InstallLog.log for an Informix Connect installation v $INFORMIXDIR/IBM_Informix_GLS_InstallLog.log for a client installation that includes Global Language Support (GLS)
2-3
Alternative Installation Methods

The following table compares four alternative methods for installing Client SDK and Informix Connect. The table uses a Client SDK installation example for Format of Command; for an Informix Connect installation, substitute the corresponding Informix Connect command.
Table 2-3. Alternative Installation Methods Installation Method Silent installation Format of Command ./installclientsdk -i silent -f path_name Products Installed Reasons to Use Use to install Client SDK or Informix Connect, with product-specific command By using a response file (which you invoke in the -f path_name option), you can replicate a specific installation configuration on multiple computers with minimal or no user interaction. Silent installation can save much time for some user scenarios. Restrictions If you use the bundle.properties file as a template for your response file, you must change the response file setting for product license terms agreement to "Accept" for the file to function during silent installation.
Extraction with ./installclientsdk command-line -DLEGACY=TRUE script
Use to install Client SDK or Informix Connect individually.
None The extraction with command-line installation alternative can be helpful in one of the following scenarios: v you want to install the product to redistribute it to multiple computers quickly and with minimal disk space usage v you want to avoid using Java Runtime Environment (JRE) during redistribution of the product
Performing a Silent Client Product Installation on UNIX and Linux

To perform a silent installation, which is sometimes referred to as an unattended installation, you must create a response file that contains information about how you want the product installed. You invoke this response file in a command-line option to perform the silent installation. You must be logged in as root user to run the installation applications.
2-4
Attention: If you use the csdk.properties file or the conn.properties file as a template for your response file, you must change the response file setting for product license terms agreement to "Accept" for the file to function during silent installation. To deploy Client SDK or Informix Connect in multiple directories: 1. Establish a response file by doing one of the following actions: v On a command line, start a product installation application in GUI or console mode and specify the -r option to generate a response file. v Save a local copy of the csdk.properties file or the conn.properties file that is on the installation media, rename the file, and configure the settings for your environment and agreement to the license terms. Skip to step 3. 2. Copy the response file to the computer where you want to install the client product. 3. Run the silent installation command for the product or products that you want to install, indicating the absolute path to the response file after the -f option: v ./installclientsdk -i silent -f path_name to install Client SDK. v ./installconnect -i silent -f path_name to install Informix Connect. 4. Repeat steps 2 and 3 for each location where you want to deploy the same installation setup.
Extracting and Redistributing Client Products with Scripts

You can use the -DLEGACY=TRUE option with an installation command to extract files from the Informix client product media and then redistribute the software on other computers by using scripts. This method functions only on UNIX and Linux operating systems. Use this type of command format if you want to extract the client product files to redistribute them without adding a JRE or an uninstallation application to multiple host systems. You extract the product files by starting the installation application with the -DLEGACY=TRUE command on one computer. After you finish running the installation application, you can copy the files in the installation directory of the first computer to redistribute the product on other computers. 1. Run one of the following commands, depending on the product you are using: v ./installclientsdk -DLEGACY=TRUE v ./installconnect -DLEGACY=TRUE The installation application opens in console mode by default. If you want to run the installation application in GUI mode, enter the -i gui option at the end of the command. 2. Follow the instructions in the installation application. 3. Copy the contents of the installation directory and place them into the directory of another computer where you want to redistribute the products. The contents include the RUNasroot scripts that you use for redistribution. 4. Run the script for the product that you want to deploy on the other computer. You can deploy either Client SDK or Informix Connect in one location, not both.
Option RUNasroot.installclientsdk RUNasroot.installconnect Description Completes the redistribution of the Client SDK files. Completes the redistribution of the Informix Connect files.
2-5
2-6
Chapter 3. Installing Client SDK and Informix Connect on Mac OS X

Install IBM Informix client products on a Mac OS X computer by running the graphical user interface (GUI) installation application. Obtain the installation media by downloading the .dmg file for Client SDK or Informix Connect. Alternatively, you can install from the .app files on a CD or DVD. You must have system administrator credentials to run the installation application. Typical installations require the following approximate amount of disk space: v Client SDK: 200 MB v Informix Connect: 175 MB The installation application automatically creates group informix and user informix if they are not on your computer. You are not required to create these group and user IDs on your host computer manually. If you have upgraded a Version 3.50 or earlier Client SDK or Informix Connect installation to Version 3.70 and it does not initialize or start after you have upgraded the host computer operating system to Snow Leopard (Mac OS X 10.6), the IDs for user informix and group informix might require changes. For more information, see the Client SDK Release Notes in the directory $MEDIADIR/doc of your installation media or at http://publib.boulder.ibm.com/infocenter/idshelp/ v117/index.jsp. To install Client SDK or Informix Connect on Mac OS X: 1. You can install from a downloaded file or from a disk: a. Installing from a downloaded file: Open the self-extracting .dmg file, and then double-click the installer icon in the Finder window to start the installation application. b. Installing from a disk: Double-click the installer icon in the Finder window for either Client SDK or Informix Connect. 2. Enter the path for the installation or accept the default provided by the installation application. 3. Complete the remaining installation steps by following the text and replying to prompts in the GUI.
3-1
3-2
Chapter 4. Uninstalling Client SDK and Informix Connect on UNIX, Linux, and Mac OS X Systems
Using the Client Product Uninstallation Applications (UNIX, Linux, and Mac OS X)
You can uninstall IBM Informix client products with an uninstallation application in GUI, console, or silent mode on UNIX, Linux, and Mac OS X. Which mode you select depends on your objectives and system environment. Important: v Do not remove any IBM Informix products by manually deleting files. v If Client SDK is installed in the same directory as the Informix database server: You must uninstall Informix before you uninstall Client SDK. Do not remove Global Language Support (GLS) because both products have dependencies on this feature.
Uninstalling Client SDK or Informix Connect in Console Mode (Default Mode)

You must be logged in as root user to perform this task for root-based installations. For non-root installations, either the installation owner or root user can remove the product. If you want to remove the product as root user, verify that the installation is not in use or in production before uninstalling. To uninstall a client product in console mode: 1. From $INFORMIXDIR, as root user, run one of the following commands: v uninstall/uninstall_csdk/uninstallcsdk v uninstall/uninstall_connect/uninstallconnect You can specify the -i console option with the command, but passing this option is not required. 2. Follow the prompts to complete the uninstallation.
Uninstalling Client SDK or Informix Connect in GUI Mode

You must be logged in as root user to perform this task for root-based installations. For non-root installations, either the installation owner or root user can remove the product. If you want to remove the product as root user, verify that the installation is not in use or in production before uninstalling. To uninstall a client product in GUI mode: 1. From $INFORMIXDIR, as the root user, run one of the following commands: v uninstall/uninstall_csdk/uninstallclientsdk -i gui v uninstall/uninstall_connect/uninstallconnect -i gui You can use the option -i swing in place of the option -i gui. 2. Follow the prompts to complete the uninstallation.
4-1
Uninstalling After Using the Extraction Application with Command-Line Script (UNIX, Linux)
If you have used the extraction application with command-line script to install Client SDK, and you want to uninstall the server, you must remove the IBM Informix product files manually. To remove the files manually, run the following command from the $INFORMIXDIR directory as the root user:
rm -rf productfiles
4-2
Part 2. Installing Client Products on Windows Systems

This section discusses preparing to install IBM Informix client products on Windows systems, explains the installation processes, and discusses post-installation tasks and how to uninstall these products. Important: The following topics of this documentation explain how to install Client SDK and Informix Connect as individual products using stand-alone client installation applications. Alternatively, you can install Client SDK or Informix Connect as part of the Informix software bundle installation media. The software bundle includes both the Informix database server and client products. For information about Note: this installation method, see the IBM Informix Installation Guide for Windows.
Chapter 5. Preparing to Install Client SDK and Informix Connect on Windows Systems
You install IBM Informix products on Windows systems by using a Windows installation program that copies files to your client computer. Install IBM Informix products only as licensed by IBM. You cannot transfer software from one computer to another, or to another portion of your network, without re-registration and the written consent of IBM. Before you install Client SDK or Informix Connect, you must install the appropriate operating-system patches and comply with the software, system, database server, protocol, compiler, and driver-manager requirements. This information can be found in the appropriate IBM Informix documentation. For example, if you use the ODBC driver manager you can read about the driver manager requirements in the IBM Informix ODBC Driver Programmer's Manual. To install Client SDK or Informix Connect on Windows systems, you must have Administrator privileges.
System Requirements
Before installing an Informix client product on a Windows system, verify that your computer complies with the minimum hardware and disk space requirements. The following list describes the system requirements for client products and Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Windows 7 systems. v Hardware: Pentium 3 or higher microprocessor v RAM: 256 megabytes v Hard-disk storage: 200 megabytes
Database Server Requirements

You can use Client SDK and Informix Connect on client computers that connect to Informix databases. For a list of compatible Informix database servers, see the online release notes for each client component.
Protocol Requirements
IBM Informix client products work with any TCP/IP protocol that complies with Windows Sockets 1.1. To configure your client product utilities, select a protocol through the Setnet32 utility. For instructions, see Setting Database Server Information on page 7-2.
C Compiler Requirements
IBM Informix client products are certified with the Microsoft Visual C++ compiler, Version 8.0. For individual components for other supported compilers, see the release notes.
5-1
Installation Location and Order

Before you install client products, verify that the installation location and the installation order are correct. Do not install Client SDK, Version 3.70, into a directory that contains a previous version. Uninstall the previous version before you install Version 3.70. For more information about installation order, see Determine Installation Order on page 1-2.
Informix .NET Provider (Windows)

The Informix .NET Provider is automatically installed when you install Client SDK if the Microsoft .NET Framework is already installed on the system. The Informix .NET Provider is copied and registered to the Global Assembly Cache (GAC). Client SDK requires the full Microsoft .NET Framework SDK. Informix Connect only requires the Microsoft .NET Framework Redistributable Package.
5-2
Chapter 6. Installing Client SDK and Informix Connect on Windows Systems

About Client Product Installation on Windows
To install Client SDK on Windows systems, run the installation application. The installation application for Windows allows you to install all components in a default directory or you can select a different installation directory and select which components you want to install. To install Client SDK or Informix Connect on Windows systems, you must have Administrator privileges. If you log on to Windows without specifying a domain, only the local system is checked. The following sections describe IBM Informix client product installation options, how to install your software, and solutions to installation problems. Attention: You must install Client SDK products before you run Enterprise Replication commands and before you convert the syscdr database. For more information, see the IBM Informix Enterprise Replication Guide.
Installing Client SDK or Informix Connect in GUI Mode (Windows)

You can install an Informix client product using a minimal, typical, or custom installation setup of the GUI installation application. You must have Administrator privileges to install Client SDK or Informix Connect. To install Client SDK or Informix Connect: 1. Copy the installation media to the target computer. If the entire media is still in .zip archive format, extract the media. 2. Exit all other applications. 3. Open the installclientsdk.exe file to install Client SDK, or the installconnect.exe file to install Informix Connect. 4. Read the GUI Introduction information. 5. Read the software license agreement and, if you accept the agreement, select I accept the terms of the license agreement. You must accept the license agreement terms to proceed with the installation. 6. Select a destination folder for the installation. You can accept the default folder location or select a different location. 7. From the Install Set drop-down box, select the installation set of products you would like to install. The GUI displays a description of each feature when you click it in the feature tree. v Typical is a full installation of all features in the client product. v Minimal is a minimal installation of features from the client product. v Custom allows you to select which features you want to install. By default, all features are selected, so you must clear features that you want to omit. 8. Review the preinstallation summary.
6-1
After you click Install, the selected features will be installed. You are given the option to also install the IBM Data Server Driver Package, and receive notification of the installation status. If you install the driver package, a new installation wizard will open after you click Done.
Performing a Silent Client Product Installation on Windows

To perform a silent installation, which is sometimes referred to as an unattended installation, you must create a response file that contains information about how you want the product installed. You invoke this response file in a command-line option to perform the silent installation. You must have Windows Administrator privileges to perform this task. Attention: If you use the csdk.properties or conn.properties file as a template for your response file, you must change the response file setting to accept the license terms agreement. To accept license terms agreement, update LICENSE_ACCEPTED=FALSE to LICENSE_ACCEPTED=TRUE . To deploy Client SDK or Informix Connect in multiple directories: 1. Establish a response file by doing one of the following: v On a command line, start a product installation in GUI mode and specify the -r option to generate a response file. v Save a local copy of the csdk.properties file or the conn.properties file that is on the installation media, rename the file, and configure the settings for your environment and agreement to the license terms. Skip to step 3. 2. Copy the response file to the computer where you want to install the client product. 3. Run the silent installation command for the product or products that you want to install, indicating the absolute path to the response file after the -f option: v installclientsdk.exe -i silent -f path_name to install Client SDK. v installconnect.exe -i silent -f path_name to install Informix Connect. 4. Repeat steps 2 and 3 for each location where you want to deploy the same installation setup.
6-2
Chapter 7. Post-Installation Client Product Tasks on Windows Systems

Configuring IBM Informix Client Products on Windows Systems
This section describes how to use the Setnet32 utility to configure Client SDK products. The Setnet32 utility sets or modifies environment variables and network parameters that IBM Informix products use at run time. The environment variables and network parameters are stored in the Windows system registry and are valid for every IBM Informix client product that you install. This section is divided into the following steps: v Setting the Environment Variables v Setting Database Server Information on page 7-2 v Setting Host Information on page 7-3 To set component-specific environment variables, see individual product documentation. The Setnet32 utility has the following four pages: v Environment allows you to set environment variables. v Server Information allows you to set database server network information. v Host Information allows you to set your host computer and login information. v About Setnet32 provides information about the Setnet32 utility.
Setting the Environment Variables

To obtain information about IBM Informix products and the environment in which they run, client products must access environment variables. Some environment variables are required and others are optional. To set environment variables: 1. Double-click Setnet32 in the folder that contains the Client SDK products. The IBM Informix Setnet32 window opens. 2. Click the Environment tab to display the Environment page, which has the following elements: v IBM Informix Client/Server Environment Select an environment variable to edit. After you select an environment variable, the environment variable name is displayed above the Variable Name text box. v Edit Environment Variable Type a new value in the text box, edit the existing value, or select a value by clicking the down arrow. Click Clear to assign a null value to that environment variable. After you make your change, click Set to save that value. v Save/Load
7-1
Click Load From File to load your environment variables and their values from a specific file. However, you cannot load environment variables from a specific file unless the Setnet32 utility has already created that file. (Use the Save To File option to create a file.) Click Save To File to save your environment variables and their values to a specific file. v Use my settings The Setnet32 entries are stored under HKEY_LOCAL_MACHINE upon installation. To save the settings in HKEY_CURRENT_USER and set that as the default registry to modify the settings, select the Use my settings and click Apply. All environment settings are then copied over to HKEY_CURRENT_USER. To revert to the HKEY_LOCAL_MACHINE entries, clear Use my settings and click Apply. The Use my settings check box is an entry stored under HKEY_CURRENT_USER as DEFAULT_USER_SETTING, and can be either LM for local machine (default) or CU for current user. For more information about environment variables, see Appendix A, Environment Variables, on page A-1 and the IBM Informix Guide to SQL: Reference. For more information about environment variables for locales, see the IBM Informix GLS User's Guide.
Setting Database Server Information

A client application connects to an Informix database server that is running on a computer that can be reached through the network. To establish the connection, use Setnet32 to specify the location of the Informix database server on the network and the network communications protocol to use. You must obtain this information from the administrator of the database server you want to use. To set database server information: 1. Double-click Setnet32 in the folder that contains the Client SDK products. The Informix Setnet32 window opens. 2. Click the Server Information tab to display the Server Information page, which has the following elements: v Informix Server Select an existing Informix database server or type the name of a new database server. v Host Name Select the host computer with the database server that you want to use or type the name of a new host computer. v Protocolname Select a network protocol from a list of protocols that the installation procedure provides. v Service Name Specify the service name that is associated with a specific database server. Type either the service name or the port number that is assigned to the database server on the host computer. You must obtain this information from the database server administrator.
7-2
Requirement: If you enter a service name, it must be defined on the client computer in the services file in the Windows installation directory. This file is located in system32\drivers\etc\services. The service definition must match the definition on the database server host computer. v Options Enter options specific to the database server. For more information, see the IBM Informix Administrator's Guide. v Make Default Server Sets the INFORMIXSERVER environment variable to the name of the current database server to make it the default database server. v Delete Server Deletes the definition of a database server from the Windows registry. It also deletes the host name, protocol name, and service name associated with that database server. 3. Click OK to save the values.
Setting Host Information

A client application can make connections only to a host computer that it can access through the network. You describe a connection to a host computer by specifying host parameters. To set Host Information: 1. Double-click Setnet32 in the folder that contains the Client SDK products. The IBM Informix Setnet32 window opens. 2. Click the Host Information tab to display the Host Information page, which has the following elements: v Current Host This field displays host computers previously defined in the current Windows registry. Select the name of a host computer with which to establish a network connection or edit or retype a name on the list to define a new host name. v User Name This field displays the user name for an account on the currently selected host computer. This text box accepts a case-sensitive value with a maximum length of 18 characters. v Password Option Select one of the following password options: Ask Password At Runtime Your application prompts the user for a password. For information about how to use the sqlauth() function to prompt for a password and verify it, see the IBM Informix ESQL/C Programmer's Manual. No password The user account has no password. When the application opens a new database, that application does not send a password to the database server. If the host computer of the database server requires a password, the connection fails, and you receive an error. Password The user account has a password that matches the encrypted value that the Password text box displays. When the application opens a new database, the database server compares the password that the user enters with the login
7-3
password for the host computer of the database server. If the passwords are not identical, the user cannot connect to that database server across a network. v Password This field, which the Password option activates, displays asterisks ( * ) that represent the account password. When this field is enabled, it accepts a password value with a maximum length of 18 characters. The value is case-sensitive and cannot contain any spaces. To enter a new password, place the cursor inside the Password text box and type the new password. Asterisks ( * ) represent the characters that you type. v Delete Host Click Delete Host to delete the name of the currently selected host computer from the Windows registry and the user name, password option, and password that is associated with that host computer. For more information about host parameters, see your IBM Informix Administrator's Guide.
Overriding Information
You can use a set of environment variables with the function call ifx_putenv to override the information that was entered in the Server Information and Host Information pages of the Setnet32 utility. To use these environment variables, set the INFORMIXSERVER environment variable to a valid database server name. Overrides affect only that database server. Client SDK, Version 3.70, supports the following WIN32 override environment variables. For more information about these environment variables, see the IBM Informix ESQL/C Programmer's Manual.
Table 7-1. WIN32 Override Environment Variables Environment Variable WIN32HOST WIN32USER WIN32PASS WIN32ASKPASSATCONNECT WIN32SERVICE WIN32PROTOCOL Overrides the Value For The HOST network parameter The USER network parameter The PASSWORD network parameter The PASSWORD OPTION network parameter The SERVICE network parameter The PROTOCOL network parameter
Configuring OLE DB Provider

To enable your IBM Informix database server for OLE DB access, a database administrator must run the SQL registration script, coledbp.sql, against the sysmaster database as user informix. To drop OLE DB support, a database administrator must run the SQL unregistration script, doledbp.sql, against the sysmaster database as user informix.
7-4
Common Installation Problems

This section describes the most common installation problems and the corresponding solutions for users who receive their product materials directly from IBM. If any of these problems persist, contact Technical Support at http:// www.ibm.com/software/data/informix/support. If you receive your IBM Informix product materials from an Electronic Software Download (ESD) vendor, consult the vendor documentation for information about how to solve any installation problems that you might encounter. v Problem. You receive the following error message:
Error 1311. Source File "d:\data.cab" Not Found.
Drive letter and path/filename can vary. Solution. This is a Windows security error that occurs when the installation application that is running as the local system user is denied access to the .cab file. There are two ways to resolve this error: Option 1: Copy the installation files to your hard disk and run the installation from there. Option 2: Change the Security Option, as follows: 1. 2. 3. 4. 5. Click Start > Settings > Control Panel > Administrative Tools. Select Local Security Policy. Expand the Local Policies folder. Select Security Options. From the right pane, depending on Windows version, select one of the following options: Devices: Restrict CD access to locally logged-on user only. Restrict CD access to locally logged-on user only. 6. Change your selection to Disabled.
7-5
7-6
Chapter 8. Uninstalling Client SDK on Windows Systems

Uninstalling or modifying Client SDK and Informix Connect in GUI mode (Windows)
You can remove a Client SDK or Informix Connect installation quickly through a shortcut on the Windows Start menu. To uninstall Client SDKor Informix Connect: 1. On the Start menu, click All Programs. 2. Click the appropriate Informix client product group. 3. Click the uninstallation option. The individual client products cannot be installed by using the Add/Remove Programs section of the Windows Control Panel.
Removing a Client SDK or Informix Connect Installation Using the Command Line
You can start uninstallation of a client product on the command line. You must have Windows administrator privileges to complete the uninstallation. 1. Open a command-line environment. 2. Run one of the following commands, depending on which product you are removing: v %INFORMIXDIR%\uninstall\uninstall_clientsdk\uninstallclientsdk.exe v %INFORMIXDIR%\uninstall\uninstall_connect\uninstallconnect.exe
8-1
8-2
Part 3. Appendixes
Appendix A. Environment Variables

In this Appendix
This appendix provides a list of client-supported environment variables and their possible values and points you to where you can look for more information.
Environment variables
Client SDK, Version 3.70, supports the following environment variables. For more information about these environment variables, see their descriptions in the respective publications.
Environment variable CC8BITLEVEL Purpose Specifies how the C-language compiler processes non-ASCII (8-bit and multibyte) characters. Specifies the locale that the client application uses to perform read/write operations that involve the keyboard, display, file, or printer on the client computer. Publication reference and possible values IBM Informix GLS User's Guide Default is 2. IBM Informix GLS User's Guide Any valid locale specifier. No default.
CLIENT_LOCALE
COLLCHAR
Specifies a collation sequence for characters. IBM Informix Guide to SQL: Provided for backward compatibility with NLS Reference products. Specifies the locale of all the databases that a client application accesses in a single connection (the database locale). When set to 1, enables compatibility with ALS products. When turned on (y), causes the preprocessor to check for Informix extensions to ANSI-standard SQL syntax at compile time and causes an application to check for Informix extensions at run time. Enables pre-7.2 systems that use nonstandard or rare code sets to access databases that store data in a standard code set. Maximum size = 23 characters. Provided for backward compatibility with NLS and ALS products. When set to 1, enables compatibility with ASCII products. IBM Informix GLS User's Guide
DB_LOCALE
DBALSBC DBANSIWARN
IBM Informix ESQL/C Programmer's Manual Values: 0 or 1 IBM Informix Guide to SQL: Reference Default is n.
DBAPICODE
IBM Informix ESQL/C Programmer's Manual
DBASCIIBC DBCENTURY
IBM Informix ESQL/C Programmer's Manual Values: 0 or 1
Specifies how to expand values of IBM Informix Guide to SQL: two-digit-year DATE and DATETIME values. P Reference Values: P, R, or C Default = past century, R = present century, C = closest is R. century. Provides support for Asian-locale code set. Overrides the code set that DB_LOCALE specifies. Provided for backward compatibility with Version 4.x and 5.x ALS products. IBM Informix ESQL/C Programmer's Manual Same values as ALS DBAPICODE. Default is 8859-1: (unless the informix.rc file specifies another system-wide default)
DBCODESET
A-1
Environment variable DBCONNECT
Purpose Specifies whether connections are restricted. Provides backward compatibility for client applications that are based on earlier versions of IBM Informix products.
Publication reference and possible values IBM Informix ESQL/C Programmer's Manual Values: 1 or 3
DBCSCONV
Controls code-set conversion initialization. IBM Informix ESQL/C Programmer's Maximum size is eight characters. Provided Manual Values: 1 or 2:codesetname for backward compatibility with ALS products. See 5.0 ALS documentation. Forces the user-specified DB_LOCALE value to override default restrictions on accessing databases with locales that are different than DB_LOCALE. Provided for backward compatibility with Version 6.0 ALS database servers. Maximum number of display bytes (1-2) and storage bytes (1-4) for the characters in up to three code sets. Display and storage widths are separated by commas; code sets are separated by colons. Maximum size of this field is, therefore, 11 characters. Provided for backward compatibility with ALS products. Specifies the end-user format for DATE values so that they can conform with various international date conventions. Provided for backward compatibility with pre-7.2 products. GL_DATE is recommended for 7.2 ESQL/C applications. Specifies the number of decimal digits to use when storing a DECIMAL, SMALLFLOAT, or FLOAT data type in a character buffer Dbaccess only. Specifies the subdirectory of the Informix installation directory that contains the product-specific message (.iem) files. Specifies the end-user format for MONEY values so that they can conform with various international and local monetary conventions. IBM Informix ESQL/C Programmer's Manual Values: 0 or 1
DBCSOVERRIDE
DBCSWIDTH
IBM Informix ESQL/C Programmer's Manual Example: 1,1:2,3 means a display and storage width of 1 byte for code set 1; a display width of 2 bytes and a storage width of 3 bytes for code set 2. Default is MDY4 unless NLS variable LC_TIME is activated.
DBDATE
DBFLTMASK
IBM Informix Guide to SQL: Reference Values: 016 Default is 16.
DBLANG
IBM Informix Guide to SQL: Reference Default is \msg. IBM Informix Guide to SQL: ReferenceIBM Informix GLS User's Guide Default is $.,.
DBMONEY
DBMONEYSCALE
IBM Informix ESQL/C Programmer's Specifies the total number of digits and number of decimal digits for monetary values. Manual Provided for backward compatibility with ALS products. Identifies the database servers that contain databases that the application accesses. IBM Informix GLS User's Guide
DBPATH DBSS2 DBSS3 DBTEMP
Maximum size is four characters. Provided for IBM Informix ESQL/C Programmer's backward compatibility with ALS products. ManualValues: 0x000xff or 0255 Maximum size is four characters. Provided for IBM Informix ESQL/C Programmer's backward compatibility with ALS products. Manual Values: 0x000xff or 0255 Specifies the directory on the client computer that the client processor uses to store temporary files (also called swap files). IBM Informix Guide to SQL: Reference Default is \tmp.
A-2
Environment variable DBTIME
Purpose Specifies the end-user format for DATETIME values so that they can conform with various international date conventions. GL_DATETIME is recommended for 7.2 ESQL/C applications. Provided for backward compatibility with pre-7.2 products.
Publication reference and possible values IBM Informix Guide to SQL: Reference IBM Informix GLS User's Guide Default is %Y-%m-%d %H:%M:%S.
DELIMIDENT
Indicates whether (y) or (n) to interpret strings IBM Informix Guide to SQL: in double quotation marks as delimited Reference Default is n. identifiers. Indicates whether the ESQL/C processor automatically invokes the ESQL/C multibyte filter (value=1 and CC8BITLEVEL<3, or not value=0). Overrides the default size of the fetch buffer. IBM Informix GLS User's Guide
ESQLMF
FET_BUF_SIZE
IBM Informix Guide to SQL: Reference Any valid buffer size, in bytes. Default value depends on row size. IBM Informix GLS User's Guide IBM Informix GLS User's Guide IBM Informix Administrator's GuideValues: yes or no. Default is no. Default is 0.
GL_DATE GL_DATETIME IFX_DISABLE_IPV6
Specifies a customized end-user format for DATE values. Specifies a customized end-user format for DATETIME values. Disables IPv6 support for a single database instance or for a single client application. Overrides the global setting and directs the optimizer to use subquery flattening for all sessions.
IFX_FLAT_USCQ
INFORMIXCONRETRY
IBM Informix Guide to SQL: Specifies the maximum number of additional connection attempts made to a database server Reference Default is 1. in the time limit that CONTIME specifies. Specifies the number of seconds an SQL CONNECT statement continues to try to establish a connection before it generates an error. Identifies the location of the client programs, library files, message files, header files, and other IBM Informix software components. INFORMIXDIR must always be set. Identifies the default database server. Specifies the name of the computer on which the central registry is located. Specifies the language environment (called a locale) for an NLS database that an application accesses. Provided for backward compatibility with NLS products. Specifies a collation or sort sequence for data in NCHAR and NVARCHAR columns of an NLS database. Provided for backward compatibility with NLS products. IBM Informix Guide to SQL: Reference Default is 60(seconds).
INFORMIXCONTIME
INFORMIXDIR
IBM Informix Guide to SQL: Reference Default is C:\INFORMIX.
INFORMIXSERVER INFORMIXSQLHOSTS LANG
IBM Informix Guide to SQL: Reference IBM Informix Guide to SQL: Reference IBM Informix ESQL/C Programmer's Manual Default is C.
LC_COLLATE
IBM Informix ESQL/C Programmer's Manual Default is the value that LANG specifies.
Appendix A. Environment Variables
A-3
Environment variable LC_CTYPE
Purpose
Publication reference and possible values
Specifies character attributes such as character IBM Informix ESQL/C Programmer's classification and case conversion of regular Manual Default is the value that expressions for data in NCHAR and LANG specifies. NVARCHAR columns of an NLS database. Provided for backward compatibility with NLS products. Specifies the end-user format for MONEY values in an NLS database. Provided for backward compatibility with NLS products. Specifies the end-user format for numeric values in an NLS database. Provided for backward compatibility with NLS products. IBM Informix ESQL/C Programmer's Manual Default is the value that LANG specifies. IBM Informix ESQL/C Programmer's Manual Default is the value that LANG specifies.
LC_MONETARY
LC_NUMERIC
LC_TIME
Specifies the end-user format for DATE and IBM Informix ESQL/C Programmer's Manual Default is the value that DATETIME values in an NLS database. Provided for backward compatibility with NLS LANG specifies. products. Allows default table privileges for PUBLIC when a new table is created in a database that is not ANSI compliant. Enables optimized message transfers (message chaining) for all SQL statements in an application. Enables optimize-OPEN-FETCH-CLOSE functionality in an IBM Informix ESQL/C application that uses DECLARE and OPEN statements to execute a cursor. Can be used to change the location temporary space directory used during installation. This is useful if there is not enough space in the default /tmp directory. IBM Informix ESQL/C Programmer's Manual Default is to allow privileges. IBM Informix Guide to SQL: Reference Default is the value that LANG specifies. IBM Informix Guide to SQL: Reference Default is the value that LANG specifies. Any valid path.
NODEFDAC
OPTMSG
OPTOFC
TMP
A-4
Appendix B. Distribute Your IBM Informix Client Applications (Windows)

In This Appendix
This appendix discusses the technical and legal requirements that you must observe when you distribute applications that are created using IBM Informix client APIs (such as IBM Informix ESQL/C and IBM Informix ODBC Driver) on Windows platforms. With your client application files, you might distribute and install IBM Informix client runtime components that are required by your application. To install these components, you can either: v Require your customers to install the components separately v Record the installation process and run the resulting script as part of your client application's installation program By using prerecorded installation scripts to install and configure IBM Informix client APIs , you can enable your customers to bypass the installation windows that normally are displayed. Such an installation is referred to as a silent installation.
Distribute IBM Informix Client Applications and Components

When you distribute a client application that you developed by using an IBM Informix client API, you might decide to distribute IBM Informix components that are required by your application at runtime. The following table lists the IBM Informix components that your customer needs in order to run your client application.
Table B-1. IBM Informix Component Needed to Run Client Application Client Development API IBM Informix Client SDK IBM Informix .NET Provider IBM Informix ESQL/C IBM Informix ODBC Driver IBM Informix Object Interface for C++ IBM Informix OLE DB Provider DataBlade API Components Required at Runtime IBM Informix Connect IBM Informix Connect IBM Informix Connect IBM Informix Connect IBM Informix Connect IBM Informix Connect (including MDAC, obtained by recording a custom installation) IBM Informix Connect
Client Runtime Component Redistribution Guidelines

IBM Informix runtime components can be redistributed. You can redistribute IBM Informix runtime components in the following two ways: v By installing all required components
B-1
v By installing specific components (for example, you can redistribute only the files that are required by IBM Informix OLE DB Provider) Attention: Do not copy single files or directories from any IBM Informix client API into your application installation; doing so violates your Technical Support agreement or contract.
B-2
Appendix C. Accessibility
IBM strives to provide products with usable access for everyone, regardless of age or ability.
Accessibility features for IBM Informix products

Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use information technology products successfully.
Accessibility features
The following list includes the major accessibility features in IBM Informix products. These features support: v Keyboard-only operation. v Interfaces that are commonly used by screen readers. v The attachment of alternative input and output devices. Tip: The information center and its related publications are accessibility-enabled for the IBM Home Page Reader. You can operate all features by using the keyboard instead of the mouse.
Keyboard navigation
This product uses standard Microsoft Windows navigation keys.
Related accessibility information

IBM is committed to making our documentation accessible to persons with disabilities. Our publications are available in HTML format so that they can be accessed with assistive technology such as screen reader software. You can view the publications in Adobe Portable Document Format (PDF) by using the Adobe Acrobat Reader.
IBM and accessibility

See the IBM Accessibility Center at http://www.ibm.com/able for more information about the IBM commitment to accessibility.
Dotted decimal syntax diagrams

The syntax diagrams in our publications are available in dotted decimal format, which is an accessible format that is available only if you are using a screen reader. In dotted decimal format, each syntax element is written on a separate line. If two or more syntax elements are always present together (or always absent together), the elements can appear on the same line, because they can be considered as a single compound syntax element. Each line starts with a dotted decimal number; for example, 3 or 3.1 or 3.1.1. To hear these numbers correctly, make sure that your screen reader is set to read punctuation. All syntax elements that have the same dotted decimal number (for example, all syntax elements that have the number 3.1) are mutually exclusive
C-1
alternatives. If you hear the lines 3.1 USERID and 3.1 SYSTEMID, your syntax can include either USERID or SYSTEMID, but not both. The dotted decimal numbering level denotes the level of nesting. For example, if a syntax element with dotted decimal number 3 is followed by a series of syntax elements with dotted decimal number 3.1, all the syntax elements numbered 3.1 are subordinate to the syntax element numbered 3. Certain words and symbols are used next to the dotted decimal numbers to add information about the syntax elements. Occasionally, these words and symbols might occur at the beginning of the element itself. For ease of identification, if the word or symbol is a part of the syntax element, the word or symbol is preceded by the backslash (\) character. The * symbol can be used next to a dotted decimal number to indicate that the syntax element repeats. For example, syntax element *FILE with dotted decimal number 3 is read as 3 \* FILE. Format 3* FILE indicates that syntax element FILE repeats. Format 3* \* FILE indicates that syntax element * FILE repeats. Characters such as commas, which are used to separate a string of syntax elements, are shown in the syntax just before the items they separate. These characters can appear on the same line as each item, or on a separate line with the same dotted decimal number as the relevant items. The line can also show another symbol that provides information about the syntax elements. For example, the lines 5.1*, 5.1 LASTRUN, and 5.1 DELETE mean that if you use more than one of the LASTRUN and DELETE syntax elements, the elements must be separated by a comma. If no separator is given, assume that you use a blank to separate each syntax element. If a syntax element is preceded by the % symbol, that element is defined elsewhere. The string following the % symbol is the name of a syntax fragment rather than a literal. For example, the line 2.1 %OP1 means that you should refer to a separate syntax fragment OP1. The following words and symbols are used next to the dotted decimal numbers: ? Specifies an optional syntax element. A dotted decimal number followed by the ? symbol indicates that all the syntax elements with a corresponding dotted decimal number, and any subordinate syntax elements, are optional. If there is only one syntax element with a dotted decimal number, the ? symbol is displayed on the same line as the syntax element (for example, 5? NOTIFY). If there is more than one syntax element with a dotted decimal number, the ? symbol is displayed on a line by itself, followed by the syntax elements that are optional. For example, if you hear the lines 5 ?, 5 NOTIFY, and 5 UPDATE, you know that syntax elements NOTIFY and UPDATE are optional; that is, you can choose one or none of them. The ? symbol is equivalent to a bypass line in a railroad diagram. Specifies a default syntax element. A dotted decimal number followed by the ! symbol and a syntax element indicates that the syntax element is the default option for all syntax elements that share the same dotted decimal number. Only one of the syntax elements that share the same dotted decimal number can specify a ! symbol. For example, if you hear the lines 2? FILE, 2.1! (KEEP), and 2.1 (DELETE), you know that (KEEP) is the default option for the FILE keyword. In this example, if you include the FILE keyword but do not specify an option, default option KEEP is applied. A default option also applies to the next higher dotted decimal number. In
C-2
this example, if the FILE keyword is omitted, default FILE(KEEP) is used. However, if you hear the lines 2? FILE, 2.1, 2.1.1! (KEEP), and 2.1.1 (DELETE), the default option KEEP only applies to the next higher dotted decimal number, 2.1 (which does not have an associated keyword), and does not apply to 2? FILE. Nothing is used if the keyword FILE is omitted. * Specifies a syntax element that can be repeated zero or more times. A dotted decimal number followed by the * symbol indicates that this syntax element can be used zero or more times; that is, it is optional and can be repeated. For example, if you hear the line 5.1* data-area, you know that you can include more than one data area or you can include none. If you hear the lines 3*, 3 HOST, and 3 STATE, you know that you can include HOST, STATE, both together, or nothing. Notes: 1. If a dotted decimal number has an asterisk (*) next to it and there is only one item with that dotted decimal number, you can repeat that same item more than once. 2. If a dotted decimal number has an asterisk next to it and several items have that dotted decimal number, you can use more than one item from the list, but you cannot use the items more than once each. In the previous example, you can write HOST STATE, but you cannot write HOST HOST. 3. The * symbol is equivalent to a loop-back line in a railroad syntax diagram. + Specifies a syntax element that must be included one or more times. A dotted decimal number followed by the + symbol indicates that this syntax element must be included one or more times. For example, if you hear the line 6.1+ data-area, you must include at least one data area. If you hear the lines 2+, 2 HOST, and 2 STATE, you know that you must include HOST, STATE, or both. As for the * symbol, you can only repeat a particular item if it is the only item with that dotted decimal number. The + symbol, like the * symbol, is equivalent to a loop-back line in a railroad syntax diagram.
Appendix C. Accessibility
C-3
C-4
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
D-1
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy,
D-2
modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml. Adobe, the Adobe logo, and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Intel, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.
Notices
D-3
D-4
Index Special characters

.app file 3-1 .dmg file 3-1 .iem file extension A-1 .NET Provider vi .NET providers ix, 5-2 DB_LOCALE environment variable A-1 DBALSBC environment variable A-1 DBANSIWARN environment variable A-1 DBAPICODE environment variable A-1 DBASCIIBC environment variable A-1 DBCENTURY environment variable A-1 DBCSCONV environment variable A-1 DBCSOVERRIDE environment variable A-1 DBCSWIDTH environment variable A-1 DBDATE environment variable A-1 DBFLTMASK environment variable A-1 DBMONEY environment variable A-1 DBMONEYSCALE environment variable A-1 DBPATH environment variable A-1 DBSS2 environment variable A-1 DBSS3 environment variable A-1 DBTEMP environment variable A-1 DBTIME environment variable A-1 DELIMIDENT environment variable A-1 Delimited identifiers A-1 Disabilities, visual reading syntax diagrams C-1 Disability C-1 Disk space 2-1 doledbp.sql script 7-4 Dotted decimal format of syntax diagrams C-1
A
Accessibility C-1 dotted decimal format of syntax diagrams C-1 keyboard C-1 shortcut keys C-1 syntax diagrams, reading in a screen reader C-1
C
CC8BITLEVEL environment variable A-1 Client Installation Windows 6-1 Client SDK Environment Variables A-1 installation 6-1 Runtime components B-1 uninstall 8-1 uninstalling 4-1 Client SDK using a GUI 8-1 Uninstalling 8-1 CLIENT_LOCALE environment variable A-1 coledbp.sql script 7-4 COLLCHAR environment variable A-1 commands uninstalling client products 4-1 uninstalling Client SDK 4-1 uninstalling Informix Connect 4-1 commandsinstallconnect installclientsdk 2-1 compliance with standards xv Configuring Informix products 7-1 the environment 7-1 Connect, redistribution guidelines B-1 Connection Manager vi Connections A-1
E
Enterprise Replication 6-1 Environment configuration 7-1 environment variables 7-4 Environment variables CC8BITLEVEL A-1 CLIENT_LOCALE A-1 COLLCHAR A-1 Database locale, setting language features A-1 Database servers default A-1 DB_LOCALE A-1 DBALSBC A-1 DBANSIWARN A-1 DBAPICODE A-1 DBASCIIBC A-1 DBCENTURY A-1 DBCODESET A-1 DBCONNECT environment variable A-1 DBCSCONV A-1 DBCSOVERRIDE A-1 DBCSWIDTH A-1 DBDATE A-1 DBFLTMASK A-1 DBLANG environment variable A-1 DBMONEY A-1 DBMONEYSCALE A-1 DBPATH A-1 DBSS2 A-1 DBSS3 A-1 DBTEMP A-1 DBTIME A-1 DELIMIDENT A-1
D
Data Server .NET Provider ix Data Server Driver, IBM See IBM Data Server Driver Database Add-Ins for Visual Studio vi Database Server requirements Windows 5-1 Database servers identifying A-1 setting parameters in Setnet32 7-2 DATE data type A-1 DATETIME data type A-1 Copyright IBM Corp. 1996, 2011
X-1
Environment variables (continued) Environment variables DBCONNECT A-1 DBLANG A-1 INFORMIXCONTIME A-1 INFORMIXDIR A-1 INFORMIXSERVER A-1 LANG A-1 LC_COLLATE A-1 LC_CTYPE A-1 LC_MONETARY A-1 LC_NUMERIC A-1 LC_TIME A-1 NODEFDAC A-1 OPTMSG A-1 OPTOFC A-1 TMP A-1 ESQLMF A-1 FET_BUF_SIZE A-1 GL_DATE A-1 GL_DATETIME A-1 IFX_FLAT_USCQ A-1 INFORMIXCONRETRY A-1 INFORMIXCONTIME environment variable A-1 INFORMIXSERVER environment variable A-1 INFORMIXSQLHOSTS A-1 INFORMIXSQLHOSTS environment variable A-1 LANG environment variable A-1 LC_COLLATE environment variable A-1 LC_CTYPE environment variable A-1 LC_MONETARY environment variable A-1 LC_NUMERIC environment variable A-1 LC_TIME environment variable A-1 Messages, optimized transfers A-1 MONEY data type A-1 NCHAR data type A-1 NLS environment A-1 NODEFDAC environment variable A-1 NVARCHAR data type A-1 OPTMSG environment variable A-1 OPTOFC environment variable A-1 setting 7-1 TMP environment variable A-1 Environment Variables 7-4 Client SDK A-1 Error log 2-3 ESQL/C vi ESQLMF environment variable A-1 extracting installation media 2-5
H
HKEY_CURRENT_USER 7-1 HKEY_LOCAL_MACHINE 7-1 Host information, setting 7-3 Host parameters 7-3
I
IBM Data Server Driver viii IFX_FLAT_USCQ environment variable A-1 ILogin utility vi industry standards xv Informix .NET Provider ix, 5-2 Informix Connect definition vi installation 6-1 redistribution guidelines B-1 uninstalling 4-1 INFORMIXCONRETRY environment variable Install medium 2-1 installation silent 2-4, 6-2 unattended 2-4, 6-2 Installation determining directory location 1-1 language compiler 5-2 order 5-2 order of 1-2 problems 7-5 running scripts for 2-1 using a GUI 6-1 installation, order 1-2 installclientsdk command 2-1 installconnect command 2-1 installing by extracting media with script 2-5
A-1
L
Language compiler 5-2 legacy installation support Linux installation 1-1 Log files 2-3 2-5
M
Mac OS X installing client products 3-1 Mac OS X installation 1-1 Message file A-1 Microsoft .NET Framework 5-2 Microsoft Visual C++ compiler 5-2 MONEY data type A-1 MTS vi
F
FET_BUF_SIZE environment variable File extensions, .iem A-1 files 2-4, 6-2 response 2-4, 6-2 A-1
G
GL_DATE environment variable A-1 GL_DATETIME environment variable A-1 GLS. vi group informix 1-3, 3-1
N
NLS environment A-1 non-root installation 1-3
O
Object Interface for C++ ODBC-MTS vi vi
X-2
OLE DB Provider vi, 7-4 Order of installation 5-2 overriding information 7-4 Overriding Information 7-4
V
Visual disabilities reading syntax diagrams C-1
P
Password CSM vi Processor, storing temporary files Product configuration 7-1 Protocols Windows 5-1 A-1
W
Windows database server requirements installing Client SDK 6-1 system requirements 5-1 Windows Registry 7-2, 7-3 5-1
R
redistributing Informix products 2-5 response file 2-4, 6-2 Runtime components Client SDK B-1
S
Screen reader reading syntax diagrams C-1 scripts for installing by extracting media Server parameters 7-2 services file 7-2 Setnet32 utility product configuration 7-1 Setting environment variables 7-1 Shortcut keys keyboard C-1 silent installation 2-4, 6-2 Snow Leopard 3-1 SQL scripts coledbp.sql 7-4 doledbp.sql 7-4 standards xv Syntax diagrams reading in a screen reader C-1 System requirements Windows 5-1 2-5
T
TCP/IP protocol Windows 5-1 Troubleshooting common installation problems 7-5
U
unattended installation see also silent installation Uninstallation using a GUI 8-1 UNIX installation 1-1 user informix 1-3, 3-1 2-4, 6-2
Index
X-3
X-4
Printed in USA
GC27-3560-02

Client Install Guide

Uploaded by

Copyright:

Available Formats

Client Install Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Client Install Guide

Uploaded by

Copyright:

Available Formats

Informix Product Family Informix Client Software Development Kit

IBM Informix Client Products Installation Guide

Informix Product Family Informix Client Software Development Kit

IBM Informix Client Products Installation Guide

Part 1. Installing Client Products on UNIX, Linux, and Mac OS X

Part 2. Installing Client Products on Windows Systems

5-1 5-1 5-1 5-1 5-2

Informix .NET Provider (Windows) .

Chapter 7. Post-Installation Client Product Tasks on Windows Systems . . . . . . . 7-1

Chapter 8. Uninstalling Client SDK on Windows Systems

Appendix B. Distribute Your IBM Informix Client Applications (Windows). . . . . . . B-1

Appendix C. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Client Products Installation Guide

About this Publication

Copyright IBM Corp. 1996, 2011

Client SDK Components

Client Products Installation Guide

IBM Informix GLS (Global Language Support)

IBM Informix ODBC Driver with MTS support

IBM Informix OLE DB Provider (Windows only)

The ConnectTest utility (Windows only)

IBM Data Server Driver

Client Products Installation Guide

Differences between .NET Providers

IBM Informix .NET Provider

IBM Data Server .NET Provider

Comparison of supported features

Client Products Installation Guide

Unsupported keywords in the ConnectionString property

Connection pooling settings

Server keyword in the ConnectionString property

Database keyword in the ConnectionString property

String values in quotation marks in the ConnectionString property

Unsupported data types in SQL statements

BYTE and TEXT data types

Supported data types

Client Products Installation Guide

Comparing classes and structures

IfxTimeSpan IfxMonthSpan IfxSmartLOBLocator IfxSmartLOB IfxDecimal

Supported Supported Supported Supported Supported

Stored procedure differences

Client Products Installation Guide

Compliance with industry standards

>--------------------------------------------->< --------SELECT-----------+-----------------+--------LOCAL------ ---+-----ALL-------+--+--DISTINCT-----+ ---UNIQUE------

Required item with choice. Only one item must be present.

---+------------------+--+--FOR UPDATE-----+ --FOR READ ONLY-- .---NEXT---------. ----+----------------+--+---PRIOR--------+ ---PREVIOUS-----

Reference to a syntax segment. Syntax segment.

How to read a command-line syntax diagram

(1) Setting the Run Mode -S server -T target

Notes: 1 See page Z-1

Client Products Installation Guide

Keywords and punctuation

Identifiers and names

How to provide documentation feedback

Client Products Installation Guide

Part 1. Installing Client Products on UNIX, Linux, and Mac OS X

Copyright IBM Corp. 1996, 2011

Client Products Installation Guide

Copyright IBM Corp. 1996, 2011

Check Online Files