Informix Product Family

Informix Client Software Development Kit

Version 3.50

IBM Informix Client Products

Installation Guide



GC23-9413-06
Informix Product Family
Informix Client Software Development Kit
Version 3.50

IBM Informix Client Products

Installation Guide



GC23-9413-06
 Note
Before using this information and the product it supports, read the information in “Notices” on page F-1.

Edition
This edition replaces GC23-9413-05.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
About this Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
What's New in Installation For Client SDK, Version 3.50 . . . . . . . . . . . . . . . . . . . . vii
Client SDK Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
IBM Data Server Driver Installation Option (Windows only) . . . . . . . . . . . . . . . . . . . x
Differences between .NET Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Software Dependencies (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Additional documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Compliance with industry standards. . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Syntax diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
How to read a command-line syntax diagram . . . . . . . . . . . . . . . . . . . . . . xviii
Keywords and punctuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Identifiers and names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
How to provide documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . xix

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 . . . . . . . . . . . . . . . . . . . 1-1
Determine Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Check Online Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Determine Installation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Prepare the Environment (UNIX, Linux) . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Creating the Group informix and User informix (UNIX, Linux) . . . . . . . . . . . . . . . . . 1-3
Configure the Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Load Product Files (UNIX and Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Extracting Product Files (Mac OS X) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Chapter 2. Installing Client SDK and Informix Connect on UNIX and Linux Systems 2-1
Installation System Requirements for UNIX and Linux. . . . . . . . . . . . . . . . . . . . . 2-1
Client SDK and Informix Connect as Part of the IBM Informix Installation Application . . . . . . . . . . 2-2
The Informix Client Installation Application . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Installation Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Installing in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Installing in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Using the Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Alternative Installation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Installing in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Performing a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Installing Using Extraction With Command-Line Script . . . . . . . . . . . . . . . . . . . 2-8
Installing Client SDK and IBM Informix Connect in Extraction with Command-Line Mode . . . . . . . 2-9
Installing by Invoking the JAR File Directly . . . . . . . . . . . . . . . . . . . . . . . 2-10
Installing Client SDK or Informix Connect by Invoking the JAR File . . . . . . . . . . . . . . . 2-11

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
Uninstalling Using the Uninstall Application . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling in console (default) mode (UNIX, Linux) . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling in GUI mode (UNIX, Linux) . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling in GUI mode (Mac OS X) . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling in silent mode (UNIX, Linux) . . . . . . . . . . . . . . . . . . . . . . . . 4-2

© Copyright IBM Corp. 1996, 2011 iii

Uninstalling After Using the Extraction Application with Command-Line Script (UNIX, Linux) . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Database Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Protocol Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
C Compiler Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Installation Location and Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Install Informix .NET Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Chapter 6. Installing Client SDK and Informix Connect on Windows Systems . . . . . 6-1
About Client Product Installation on Windows . . . . . . . . . . . . . . . . . . . . . . . 6-1
Use the Windows Installation Program to Install Client SDK . . . . . . . . . . . . . . . . . . 6-1
Installing IBM Informix Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Installing Client SDK from the Command Line Using msiexec . . . . . . . . . . . . . . . . . . 6-3
Installing Client SDK with Silent Installation . . . . . . . . . . . . . . . . . . . . . . . 6-4
Common msiexec Command Operations . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Setting Public Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Installing Client SDK by Using the Command Line: Advertised Mode . . . . . . . . . . . . . . 6-6
Installing IBM Data Server Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

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

Configuring IBM Informix Client Products on Windows Systems . . . . . . . . . . . . . . . . . 7-1
Setting the Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Setting Database Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Setting Host Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Overriding Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Configuring OLE DB Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Common Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Modifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Repairing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Chapter 8. Uninstalling Client SDK on Windows Systems . . . . . . . . . . . . . 8-1

Uninstalling Client SDK by Using the Windows Control Panel . . . . . . . . . . . . . . . . . . 8-1
Uninstalling or modifying Client SDK and Informix Connect in GUI mode (Windows) . . . . . . . . . . 8-1
Uninstalling Client SDK by Using the Command Line . . . . . . . . . . . . . . . . . . . . . 8-1

Part 3. Appendixes

Appendix A. Environment Variables . . . . . . . . . . . . . . . . . . . . . . . A-1

In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B. Distribute IBM Informix Client Applications and Components . . . . . . B-1

Client Runtime Component Redistribution Guidelines . . . . . . . . . . . . . . . . . . . . . B-1
IBM Informix Client Application Distribution Options . . . . . . . . . . . . . . . . . . . . . B-1
Your customers order IBM Informix Connect directly from IBM and install it themselves . . . . . . . . B-2
You ship the IBM Informix Connect product with your client application; your customer installs it . . . . . B-3
You ship IBM Informix Connect on the same CD as your client application; your customer installs it . . . . B-3
You ship IBM Informix Connect on the same CD as your client application; your customers install it silently
when they install your application . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
For internal use: you ship IBM Informix Connect on the same CD as your client application; your employees
install it silently when they install your application. . . . . . . . . . . . . . . . . . . . . B-5

Appendix C. Installing IBM Informix Connect C and C++ Client Runtime Components C-1

iv Client Products Installation Guide

Creating the Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Creating the Client Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Creating Your Client Application Installation Program. . . . . . . . . . . . . . . . . . . . . C-2
Installing Client Runtime Components . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Configuring the Client Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

Appendix D. Verifying the Results of Silent Installation . . . . . . . . . . . . . . D-1

Appendix E. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Accessibility features for IBM Informix products. . . . . . . . . . . . . . . . . . . . . . . E-1
Accessibility features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Keyboard navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Related accessibility information . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
IBM and accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Dotted decimal syntax diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Contents v
vi 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 Client SDK, Version 3.50

This publication includes information about new features and changes in existing
functionality.

The following changes are relevant to this publication.

Table 1. What's New in IBM Informix Client Products Installation Guide Version 3.50.xC9
Overview Reference
You can use IBM Data Server Driver to For more information about the IBM Data
install and evaluate the common client Server Driver, see the IBM Data Server Driver
drivers with Informix. The current Data for JDBC and SQLJ for Informix.
Server Driver package available is Version 9.7
FP4.

Table 2. What's New in IBM Informix Client Products Installation Guide Version 3.50.xC8
Overview Reference
New editions and product names For more information about the Informix
product family, go to http://www.ibm.com/
IBM Informix Dynamic Server editions were software/data/informix/.
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

© Copyright IBM Corp. 1996, 2011 vii

 Table 3. What's New in IBM Informix Client Products Installation Guide Version 3.50.xC6
Overview Reference
IBM Data Server Driver installation option “IBM Data Server Driver Installation Option
(Windows only) (Windows only)” on page x

You can install IBM Data Server Driver when Chapter 5, “Preparing to Install Client SDK
you install Client SDK or IConnect. and Informix Connect on Windows Systems,”
on page 5-1
IBM Database Add-Ins for Visual Studio “Client SDK Components”
installation discontinued (Windows only)

IBM Database Add-Ins for Visual Studio

(VSAI) is no longer installed with Client SDK
or IConnect, but is downloadable for
installation.

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.
Table 4. Client SDK Components
Component Description
IBM Informix .NET The IBM Informix .NET Provider is a .NET assembly that lets
Provider (Windows .NET applications access and manipulate data in IBM Informix
only) 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 The viewer lets you see the release and machine notes in text
format.
Informix ESQL/C with An SQL embedded-language product that is used to create
XA support custom C applications.

For more information, see the IBM Informix ESQL/C Programmer's

Manual.
The finderr utility on These utilities enable you to obtain information about error
UNIX systems and the messages, including corrective actions, that are specific to IBM
Informix Error Informix.
Messages utility on
Windows systems

viii Client Products Installation Guide

Table 4. Client SDK Components (continued)
Component Description
IBM Informix Object A C++ interface to develop object-oriented client applications for
Interface for C++ 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 An interface that allows IBM Informix products to use different
(Global Language locales that have defined conventions for a particular language,
Support) 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 An IBM Informix implementation of the Open Database
Driver with MTS Connectivity (ODBC) 3.0 Level 1+ standard that supports
support 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 A client-side, native OLE DB provider that implements full
Provider (Windows functionality for base-level providers and contains extensibility
only) support for IBM Informix.

For more information, see the IBM Informix OLE DB Provider

Programmer's Guide.
The ILogin utility The ILogin Demo utility lets you quickly test the connection to
(Windows only) IBM Informix. Click File > Run then enter the IBM Informix
connection parameters. You must create the target database
before you connect to it.
Password CSM 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.
Connection Manager 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.
DB-Access 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.

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=swg-
daivs.

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

Introduction ix
 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 Installation Option (Windows only)

After installing Client SDK or IBM Informix Connect installation on Windows, you
have the option of also installing IBM Data Server Driver.

Installing Data Server Driver with Client SDK or Informix Connect enables you to
use IBM Data Server .NET Provider to develop .NET applications for IBM
Informix. Data Server .NET Provider has several advantages including:
v Better Database Add-Ins for Visual Studio support for web application
development
v Support for .NET framework 3.0, 3.5
v Support for LINQ, Silverlight, and AJAX development
v ASP.NET data support
v ADO.NET Entity Data Modeling (EDM) support

The Data Server Driver installation option does not affect the 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 Programmer‘s 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.

x Client Products Installation Guide

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
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 5. Compare features supported by Informix .NET Provider and IBM Data Server .NET
Provider
IBM Data Server .NET
Feature IBM Informix .NET Provider Provider
Protocol support SQLI DRDA
Informix server support Any supported Informix Informix v11.10 or later ONLY
version
LOB (BLOB & CLOB) 4 TB 2 GB
column size limit
Support for .NET No Yes
framework 3.0, 3.5
Supports 1.1 and 2.0 Supports 2.0, 3.0, and 3.5
frameworks. Limited VSAI frameworks.
windows application support.
Support for LINQ No Yes
(Entity Framework)
Silverlight and AJAX No Yes
development support
ASP.NET dynamic data No Yes
support
ADO.NET Entity Data No Yes
Modeling (EDM)
support

Introduction xi
 Table 5. Compare features supported by Informix .NET Provider and IBM Data Server .NET
Provider (continued)
IBM Data Server .NET
Feature IBM Informix .NET Provider Provider
Visual Studio Tools for No Yes
Office (VSTO)
development using
EDM
VSAI support for Visual No Yes
Studio 2008, Web
application
development support,
WPF and WWF
enhancements
VSAI Designers to No Yes
create tables,
procedures, functions
and triggers, run
procedures and
functions

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.

xii Client Products Installation Guide

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.

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.

Introduction xiii
 Table 6. Differences between .NET provider support for unusual Informix data types
IBM Informix .NET IBM Data Server .NET
Informix Data Type Provider Provider
CLOB, BLOB Supported Limited Support. The size
limitation is 2 GB.
Collection Supported Not supported
Interval DayToFraction Supported. This type must Not supported
be read as a string.
IntervalMonth Supported Not supported
LIST Supported Not supported
MONEY Supported Money will be treated as
decimal data type.
MULTISET Supported Not Supported
ROW Supported Not Supported
SET 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 7. Differences between .NET provider support for data type classes and structures
IBM Informix .NET IBM Data Server .NET
Class / Structure Provider Provider
IfxBlob Supported Limited Support. Some
methods return a
NotImplemented exception.
IfxClob Supported Limited Support. Some
methods return a
NotImplemented exception.
IfxTimeSpan Supported Not Supported
IfxMonthSpan Supported Not Supported
IfxSmartLOBLocator Supported Not Supported
IfxSmartLOB Supported Not Supported
IfxDecimal Supported Limited Support. Some
methods return a
NotImplemented exception.

xiv Client Products Installation Guide

Table 7. Differences between .NET provider support for data type classes and
structures (continued)
IBM Informix .NET IBM Data Server .NET
Class / Structure Provider Provider
IfxDateTime Supported 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.

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
Introduction xv
 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.

Software Dependencies (Linux)

If you are working on Linux, verify that you have an RPM Package Manager
(RPM) installation.

Most current Linux distributions include RPM. For more information about RPM
or to obtain a copy of RPM, see the RPM website at http://www.rpm.org.

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/sw-
library/.

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).

IBM Informix Dynamic Server (IDS) Enterprise Edition, Version 11.50 is certified
under the Common Criteria. For more information, see Common Criteria
Certification: Requirements for IBM Informix Dynamic Server, which is available at
http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US
&FNC=SRX&PBL=SC23-7690-00.

xvi Client Products Installation Guide

Syntax diagrams
Syntax diagrams use special components to describe the syntax for statements and
commands.
Table 8. 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.

--------SELECT---------- Required item.

--+-----------------+--- Optional item.

’------LOCAL------’

---+-----ALL-------+--- Required item with choice.

+--DISTINCT-----+ Only one item must be
’---UNIQUE------’ present.

---+------------------+--- Optional items with choice

+--FOR UPDATE-----+ are shown below the main
’--FOR READ ONLY--’ line, one of which you might
specify.

.---NEXT---------. The values below the main

----+----------------+--- line are optional, one of
+---PRIOR--------+ which you might specify. If
’---PREVIOUS-----’ you do not specify an item,
the value above the line is
used by default.

.-------,-----------. Optional items. Several items

V | are allowed; a comma must
---+-----------------+--- precede each repetition.
+---index_name---+
’---table_name---’

>>-| Table Reference |->< Reference to a syntax

segment.
Table Reference Syntax segment.
|--+-----view--------+--|
+------table------+
’----synonym------’

Introduction xvii
 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 -n -d device -D database

-p project

-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:

l
c
-f
d u n N
p
a

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

xviii Client Products Installation Guide

 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.

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 email to [email protected].
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.

Introduction xix
 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.

xx Client Products Installation Guide

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.

© Copyright IBM Corp. 1996, 2011

Client Products Installation Guide
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.

Attention:
v The $INFORMIXDIR path, including path separators, should not exceed 200
characters.
v Client SDK does not support RPM installations.

Use the following methods to install IBM Informix Client Software Development
Kit (Client SDK), Version 3.50 and IBM Informix Connect, Version 3.50 on UNIX or
Linux:
v installation application
v command line
v Informix installation program

For Mac OS X, the only way to install the products is with an installation
application.

Also check individual product manuals for installation and configuration tasks that
this publication does not cover.

Install IBM Informix products only as licensed by IBM. You must not transfer
software from one computer to another or to another portion of your network
without re-registration and the written consent of IBM.

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.

IBM Informix documentation refers to the installation directory as

$INFORMIXDIR. If the environment variable INFORMIXDIR is set, the default

© Copyright IBM Corp. 1996, 2011 1-1

 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 Versions of Client SDK and IBM Informix Connect
Server
Versions 2.7 and prior 2.8x 2.9x 3.x
5.x Database server Database server Database server Database server
first first first first
7.2x Database server Database server Database server Database server
first first first first
7.3x Database server Database server Database server Database server
first first first first
8.5x Client products Client products Client products Client products
first first first first
9.2x Database server Database server Database server Database server
first first first first
9.3x Database server Database server Database server Database server
first first first first
9.4 Client products Database server Database server Database server
first first first first
10.0 Client products Database server Database server Database server
first first first first
11.x N/A N/A Database server Database server
first 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
listing of error message text and corrective action. If you encounter problems with
the finderr utility, see IBM Informix Error Messages.

1-2 Client Products Installation Guide

 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.

Creating the Group informix and User informix (UNIX, Linux)

Create the group informix and user informix if they do not already exist.

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:
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.

Chapter 1. Preparing to Install Client SDK and IBM Informix Connect on UNIX, Linux, and Mac OS X Systems 1-3
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.

Load Product Files (UNIX and Linux)

As the last step before you install, you must load the product files.

For information about loading vendor product files, see individual vendor
documentation.

To load the product files on UNIX and Linux:

1. Confirm that you are logged in as user root.
2. Access the product files directly from a CD.
3. To access the product files from a fileserver, enter the appropriate tar, cpio, or
other command:
v On some UNIX platforms you can use the following tar command to place
the product files in the current directory:
tar xvf filename
v On some UNIX platforms you can use the following cpio command to place
the product files in the current directory.
cpio -icdumvB < filename
In this command, filename is the path name of the cpio file that contains the
product files.

Extracting Product Files (Mac OS X)

If you obtained the installation media for Mac OS X by downloading the files, then
you must extract the product from the compressed .dmg file before you can run the
installation application.

The installation application runs when you open the clients package file. file for
the client that you want to install.If you have received the media on a disk, then
you are not required to extract product files to access the file. However, media
distributed by Internet downloading is compressed and must be extracted.

To extract the product files on Mac OS X:

Open the self-extracting .dmg file to have access to the clients installation package
file.

1-4 Client Products Installation Guide

Chapter 2. Installing Client SDK and Informix Connect on
UNIX and Linux Systems
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
v Installing by invoking the JAR file directly

Depending on the installation method you select, you need differing amounts of
disk space, as describe in the following table.
Table 2-1. Installation Medium and Disk Space Required
Minimum Amount of Disk Space Required for
Installation Medium and Method Installation
Installing from a disk using the
Informix Connect
installation application.
165 MB
Client SDK
190 MB
Downloading the installation
Informix Connect
application files to the installation
315 MB
machine.
Client SDK
340 MB
Using the extraction option and then
Informix Connect
running command-line script.
190 MB
Client SDK
215 MB
Using the extraction option and then
Informix Connect
running command-line script on
290-340 MB
Linux.
Client SDK
315-365 MB

© Copyright IBM Corp. 1996, 2011 2-1

 Attention: Ensure that you have 170 MB free space available in your /tmp
directory before installation if you are using the JRE that is part of the installation
application. If you are using a JRE already present on the host computer, you need
less than 1 MB. This space requirement is included in the total disk space
requirements listed in the previous table.

Do not remove your /tmp directory after installation. The /tmp directory is used
during both the install and uninstall to store and manage files. Removing the
directory may corrupt your setup and require a complete product reinstallation.

Client SDK and Informix Connect as Part of the IBM Informix

Installation Application
You can install Client SDK or Informix Connect as part of the IBM Informix
installation application.

For information about

this installation method, see the IBM Informix Installation Guide for UNIX, Linux, and
Mac OS X or the Quick Beginnings for IBM Informix Dynamic Server Express Edition.

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-5.

Installation Syntax
The following syntax diagram illustrates the installation options for Informix client
products.

installconn

installclientsdk -gui -log logfilename

-javahome Java dir -tempdir temp path -is:freediskblocks
-is:nospacecheck


(1)
-help

Notes:
1 No other options are valid with this option.
Table 2-2. Syntax Elements
Element Purpose Restrictions
Java dir Specifies the JRE on the host computer to use The JRE must be
during installation instead of the JRE provided version 1.4.2 or
by the installation program higher.
logfilename Specifies a non-default log filename None

2-2 Client Products Installation Guide

 Table 2-2. Syntax Elements (continued)
Element Purpose Restrictions
temp path Specifies the path to temporary directory. If None
you receive an error during file extraction that
there is not enough space in the /tmp
directory, set the -tempdir option to a different
temporary directory.

The following table describes the installation application options.

Table 2-3. Installation Options
Option Meaning
installconn Install Informix Connect only
installclientsdk Install IBM Informix only
-gui Start the installation program in GUI mode
-log Log installation program progress
-javahome Use specified JRE. To force the installation program to use the
bundled JRE and ignore any local JREs, use the -javahome none
argument.
-tempdir Use specified temporary directory.
-is:freediskblocks Use to determine if there is adequate space for the product
installation files before starting the installation.
-is:nospacecheck Use to prevent the installation program from checking if there is
adequate space for product installation files. Use with caution: if
there is not enough space to extract the temporary files, the
installation program will fail.
-help Display list of supported options and their functions

Installing in Console Mode

The following steps outline how to install client products in GUI or console mode
on UNIX and Linux.

Note: When installing in console mode, especially over a network, you might have
to wait a few moments for the files to extract.

To install The following steps outline how to install client

products in GUI or console mode on UNIX and Linux. in console
mode:
1. As root, run the command for the product you want to install, as shown in
“Installation Syntax” on page 2-2:
./installclientsdk
or
./installconn
The installation application begins in console mode.
2. Read the license agreement and accept the terms; then enter 1 to continue the
installation procedure.
3. Accept the default directory, or select a different directory and enter 1 to
continue.

Chapter 2. Installing Client SDK and Informix Connect on UNIX and Linux Systems 2-3
 4. Select Typical for the suggested setups or select Custom for more configuration
options.
5. Enter 1 to continue the installation procedure.
The screen will show summary information including directory, components
installed, and total size.
Client SDK installation on Linux zSeries®: If you receive the message - For input
string: "", ignore this message and enter 3 to finish the installation if the
summary information screen is correct.
6. When the installation is complete, enter 3 to finish and exit the wizard.

Installing in GUI Mode

The following procedure shows how to install Client SDK and IBM Informix
Connect in GUI mode.

Requirement: Installing in GUI mode requires an X Windows system.

Note: When installing in GUI mode, especially over a network, you might have to
wait a few moments for the files to extract.

To install Client SDK or Informix Connect in GUI mode:

1. As root, run the command with for the product you want to install with the
-gui option, as shown in “Installation Syntax” on page 2-2:
installclientsdk -gui
or
installconn -gui
Issuing either of these commands will launch the installation application in
GUI mode.
2. Click Next to progress through the screens.
3. Read the license agreement and accept the terms; then click Next to continue.
4. When prompted, accept the default directory or specify a different directory.
5. Check the items you want to select.
6. Click Next to continue installing.
Client SDK installation on Linux zSeries: If you receive the message - For input
string: "", ignore this message and click the option to finish the installation if
the summary information screen is correct.

Using the Log Files

You can find information that will help identify and resolve installation errors in
two different types of log files.

Find the log files at the following locations:

v Installation-related log files:
– For successful installations:
- Client SDK: $INFORMIXDIR/tmp/csdk-version-install.log
- Informix Connect: $INFORMIXDIR/tmp/iconnect-version-install.log
– For unsuccessful installations:
- Client SDK: tempdir/informix/csdk-version-install.log
- Informix Connect: tempdir/informix/iconnect-version-install.log
v Product log files:

2-4 Client Products Installation Guide

 – Client SDK: $INFORMIXDIR/tmp/csdklog.txt
– Informix Connect: $INFORMIXDIR/tmp/connlog.txt

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-4. Alternative Installation Methods
Installation
Method Format of Command Products Installed Reasons to Use Restrictions
Silent ./installclientsdk Use to install Uses preset installation Install as root user.
installation -silent -options Client SDK or file (.ini file) that can be Unless you specify
mysilent.ini Informix Connect, saved and reused as a -acceptlicense=yes on
with custom template the command line, or set
configuration the -W lafiles.license
Accepted property to the
value of true, the
installation will not
continue.
Extraction with ./installclientsdk Use to install The extraction with None
command-line -legacy Client SDK or command-line
script Informix Connect installation alternative
individually. 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
Invoking JAR java -cp csdk.jar run Use to install Provides a faster To use this installation
file directly Client SDK or installation method option, you must have a
Informix Connect, version of JRE 1.32 or
with higher.
product-specific
command

Installing in Silent Mode

You can install Client SDK and Informix Connect with no user interaction, after
editing the properties in the .ini file. The following syntax diagram illustrates the
installation options for the silent installation.

Chapter 2. Installing Client SDK and Informix Connect on UNIX and Linux Systems 2-5
 Silent Installation Syntax


installconn -silent -acceptlicense=yes

installclientsdk -options optionfile

-log logfilename -javahome Java dir -tempdir temp path


-is:freediskblocks (1)
-is:nospacecheck -help

Notes:
1 No other options are valid with this option.
Table 2-5. Elements for Silent Installation Options
Element Purpose Restrictions
optionfile Specifies file name of .ini file to preset installation None
properties
Java dir Specifies the JRE on the host computer to use during The JRE must
installation instead of the JRE provided by the be version 1.4.2
installation program or higher.
logfilename Specifies a non-default log filename None
temp path Specifies path to temporary directory. If you receive an None
error during file extraction that there is not enough
space in the /tmp directory, set the -tempdir option to a
different temporary directory.

The following table describes the silent installation options.

Table 2-6. Silent Installation Options
Option Meaning
-silent Set the installation program to silent mode
-acceptlicense=yes Accept license
-options Provide location of .ini where you can preset installation
properties
installconn Install Informix Connect only
installclientsdk Install Client SDK only
-log Log installation program progress
-javahome Use specified JRE. To force the installation program to use the
bundled JRE and ignore any local JREs, use the -javahome none
argument.
-tempdir Point to temporary directory other than /tmp
-is:freediskblocks Use to determine if there is adequate space for the product
installation files before starting the installation.
-is:nospacecheck Use to prevent the installation program from checking if there is
adequate space for product installation files. Use with caution: If
there is not enough space to extract the temporary files, the
installation program will fail.
-help Display list of supported options and their functions

2-6 Client Products Installation Guide

 To perform a silent installation of Client SDK, you can modify the values in the
csdk.ini file to set properties or accept default values.

To perform a silent installation of Informix Connect, you can modify the values in
the conn.ini file or accept default values.

The following table describes these properties.

Table 2-7. Properties for silent.ini file
Properties Possible Values Description
-P installLocation= Valid directory; for example: Specifies the directory into which the
/usr/informix (default) product will be installed
-W setupTypes.selectedSetupTypeId= typical (default) Specifies setup type

custom
-P csdk.active= true Indicates whether product or features is
selected for installation.
false (default)
Informix Connect and the full Client SDK
cannot both be installed at the same time
or into the same location.
-P iconnect.active= true (default) Indicates whether product or features is
selected for installation.
false
Informix Connect and Client SDK cannot
be installed at the same time.
-SP CSDK/UNIX/csdk.jar true (default) Indicates whether product or features is
clientfeature.active= selected for installation.
false
Only applicable for a Client SDK
installation with the Custom option.
-P messagesfeature.active= true (default) Indicates whether the error messages
feature is selected for installation
false
-P glsfeature.active= true (default) Indicates whether the error GLS feature is
selected for installation
false
-G licenseAccepted true Accepts license. Value of false stops the
false installation process. No value is needed if
you accept the license at the command
line.

You can find the license in

$MEDIADIR/doc/license.

Performing a Silent Installation

Follow these steps to perform a silent installation.

To perform a silent installation:

1. Copy csdk.ini or conn.ini to any readable location and rename: myclient.ini.
2. Edit the *.ini file in your directory.
Use this file to configure the install with the options specified. If you do not
edit these values or specify the *.ini file when you specify a silent install, the
installation program will use default values.

Chapter 2. Installing Client SDK and Informix Connect on UNIX and Linux Systems 2-7
 3. As the root user, run the silent installation of Client SDK or Informix Connect
in the following way:
installclientsdk -silent -options myclient.ini
or run the silent installation of Informix Connect in the following way:
installconn -silent -options myclient.ini

Installing Using Extraction With Command-Line Script

As an alternative to using the installation programs, you can generate script-based
installable media, and you can later install Client SDK and Informix Connect by
using command-line options. The extraction mode uses the installation program to
extract the media and provide the Software License Agreement. After the
extraction, when you are ready to install the product, you must run the
command-line installation script.

Extraction Syntax


installconn -legacy

installclientsdk -gui -log logfilename


-javahome Java dir -tempdir temp path -is:freediskblocks
-is:nospacecheck

The following table explains the syntax elements.

Table 2-8. Syntax Elements
Element Purpose Restrictions
Java dir Specifies the JRE on the host computer to use during The JRE must be
installation instead of the JRE provided by the version 1.4.2 or
installation program higher.
logfilename Specifies a non-default log filename None
temp path Specifies the path to temporary directory. If you receive None
an error during file extraction that there is not enough
space in the /tmp directory, set the -tempdir option to a
different temporary directory.

The following table describes the extraction options.

Table 2-9. Installation Options
Option Meaning
installconn Extract Informix Connect only
installclientsdk Extract Client SDK only
-gui Start the extraction in GUI mode
-log Log installation program progress
-javahome Use specified JRE. To force the installation program to use the
bundled JRE and ignore any local JREs, use the -javahome none
argument.
-tempdir Point to temporary directory other than /tmp
-is:freediskblocks Use to determine if there is adequate space for the product
installation files before starting the extraction.

2-8 Client Products Installation Guide

 Table 2-9. Installation Options (continued)
Option Meaning
-is:nospacecheck Use to prevent the installation program from checking if there is
adequate space for product installation files. Use with caution: If
there is not enough space to extract the temporary files, the
extraction program will fail.
-help Display list of supported options and their functions

No installation-provided JRE and no uninstallation program will be present after

this installation.

Use this option if you want to install the products in a different location or
redistribute it.

Installing Client SDK and IBM Informix Connect in Extraction

with Command-Line Mode
Use these instructions to install Client SDK and IBM Informix Connect in
extraction with command-line mode.

To install Client SDK and IBM Informix Connect in extraction with

command-line mode:
1. As root, run one of the following options to extract the product files:
./installclientsdk -legacy
or
./installconn -legacy
The installation program is used for the extraction.
You can use the -legacy argument in default console mode or GUI mode, but
not silent installation mode. The following instructions are for the default
console mode.
2. Enter 1 to progress through the installation screens.
The Software License Agreement is displayed.
3. After you read the license agreement, enter 1 to accept the terms.
4. Specify an installation directory or accept the default directory.
The client product and installation files are extracted.
5. Select Finish to exit the wizard.
Installable media are now available. You can copy, archive, and distribute the
files at this point. You can then install Client SDK or IBM Informix Connect
without using the installation program or Java.
6. To install Client SDK or IBM Informix Connect, set $INFORMIXDIR to the
destination directory of the separately installable product and, as root user, run
the installation script:
./installclientsdk
or
./installconn

Note: This instruction differs from the instruction for the pre-2.90 command-line
installation, which must have been as the informix user.

Chapter 2. Installing Client SDK and Informix Connect on UNIX and Linux Systems 2-9
 Installing by Invoking the JAR File Directly
The following syntax diagram illustrates the installation options you can use when
the Client SDK or Informix Connect .jar file is invoked directly. To use this
installation option, you must have a version of JRE 1.32 or higher.

Direct JAR Invocation Installation Syntax

java -cp CSDK/UNIX/csdk.jar:ICONNECT/UNIX/conn.jar: run

relative_directory/csdk.jar
relative_directory/conn.jar

-P legacy.active=true -p logFile logfilename

-swing

-is:freediskblocks -silent -acceptlicense=yes
-is:nospacecheck -options optionfile

Table 2-10. Elements for the JAR-Invoked Installation Options

Element Purpose Restrictions
relative_directory Specifies the path to the specified .jar file. If None
you run the command from the directory where
the .jar file is located, do not specify a path.
logfile Specifies a non-default log file name None
optionfile Specifies file name of .ini file to preset None
installation properties

The following table describes the Java-invoked application options.

Table 2-11. JAR-Invoked Installation Options
Option Meaning
csdk.jar The installation application for Client SDK
conn.jar The installation application for Informix Connect
-P legacy.active=true Extract files but do not install the product
-p logfile Log installation program progress
-is:freediskblocks Use to determine if there is adequate space for the product
installation files before starting the installation.
-is:nospacecheck Use to prevent the installation program from checking if there
is adequate space for product installation files. Use with
caution: If there is not enough space to extract the temporary
files, the installation program will fail.
-swing Set the Java-invoked application to GUI mode
-silent Set the Java-invoked application to silent mode
-options Use with optionfile. Specifies file name of .ini file to preset
installation properties

2-10 Client Products Installation Guide

Installing Client SDK or Informix Connect by Invoking the JAR
File
You can install Client SDK or Informix Connect by invoking the JAR file directly.

To install Client SDK or Informix Connect by invoking the JAR file directly:

Invoke Java on the installation program, using the command that corresponds to
the products you want to install; for example:
java -cp csdk.jar run

You must run this command from the directory of the csdk.jar file.

Chapter 2. Installing Client SDK and Informix Connect on UNIX and Linux Systems 2-11
2-12 Client Products Installation Guide
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 .pkg 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: 150 MB
v Informix Connect: 110 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.50 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/
v115/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.

© Copyright IBM Corp. 1996, 2011 3-1

3-2 Client Products Installation Guide
Chapter 4. Uninstalling Client SDK and Informix Connect on
UNIX, Linux, and Mac OS X Systems
Uninstalling Using the Uninstall Application
You can uninstall IBM Informix client products with an uninstallation application,
which you can run in different modes for most operating systems.

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.

Use any of the following console, GUI, or silent methods to uninstall Client SDK
and Informix Connect on UNIX or Linux. If you are uninstalling on Mac OS X, the
only method available is documented in this topic.

Uninstalling in console (default) mode (UNIX, Linux)

To uninstall IBM Informix client products in console (default) mode:
1. From $INFORMIXDIR, as the root user, run one of the following commands:
v java -jar uninstall_conn/uninstall.jar
v java -jar uninstall_csdk/uninstall.jar
2. Follow the prompts to complete the uninstall.

Uninstalling in GUI mode (UNIX, Linux)

To uninstall IBM Informix client products in GUI mode on UNIX or Linux:
1. From $INFORMIXDIR, as the root user, run one of the following commands:
v java -jar uninstall_conn/uninstall.jar -gui
v java -jar uninstall_csdk/uninstall.jar -gui
2. Follow the prompts to complete the uninstallation.

Uninstalling in GUI mode (Mac OS X)

Note: When you uninstall Client SDK or Informix Connect, the registered IBM
Informix ODBC Driver is unregistered if this registered driver is on the system.
The uninstallation application also prompts you to confirm that you want to delete
the user-defined sqlhosts file entries used by ODBC connections.

To uninstall IBM Informix client products in GUI mode on Mac OS X:

1. As the root user, from $INFORMIXDIR run the following command:
v java -jar uninstall_csdk/uninstall.jar -swing
2. Follow the prompts to complete the uninstall.

© Copyright IBM Corp. 1996, 2011 4-1

 Uninstalling in silent mode (UNIX, Linux)
To uninstall IBM Informix client products in silent mode:
1. From $INFORMIXDIR, as the root user, run one of the following commands:
v java -jar uninstall_conn/uninstall.jar -silent
v java -jar uninstall_csdk/uninstall.jar -silent
2. No interaction is required to complete the uninstall in silent mode.

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 Client Products Installation Guide

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.

Note: For information about this installation method, see the IBM Informix
Installation Guide for Windows.

© Copyright IBM Corp. 1996, 2011

Client Products Installation Guide
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 systems.
v Hardware: Pentium 3 or higher microprocessor
v RAM: 256 megabytes
v Hard-disk storage: 115 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 5.0 and Version 6.0. For individual components for other supported
compilers, see the release notes.

© Copyright IBM Corp. 1996, 2011 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.50, into a directory that contains a previous
version. Uninstall the previous version before you install Version 3.50.

For more information about installation order, see “Determine Installation Order”
on page 1-2.

Note: Beginning with Client SDK Version 3.50.xC6, you can install a 32-bit version
and a 64-bit version of the same client product on the same host computer.

Install Informix .NET Provider

Beginning with Client SDK, Version 2.9, the Informix .NET Provider is
automatically installed when you install the Client SDK if the Microsoft .NET
Framework is already installed on the system. The .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.

If you do not have the .NET Framework installed, and want to install the Informix
.NET Provider, complete the following steps:
1. Select the Custom installation.
2. Enable the .NET Provider option.
The Informix .NET Provider is copied to the target dir\bin directory, but will
not register it because GAC will not be present.

5-2 Client Products Installation Guide

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.

The Windows Installer service prevents a product from being installed over an
existing installation of the same product version. If you run the installation a
second time, the service prompts you to repair, modify, or uninstall the existing
product.

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.

Note: Beginning with Client SDK Version 3.50.xC6, you can install a 32-bit version
and a 64-bit version of the same client product on the same host computer.

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.

Use the Windows Installation Program to Install Client SDK

To install Client SDK, load the product files and use the installation program to
install the products. Perform the following steps for either the Complete or the
Custom option.

To install Client SDK:

1. Exit all Windows programs.
2. Load the CD for Client SDK into the CD drive.
You can also download the network installation.
3. The installation application starts automatically. The IBM Informix Client SDK
Setup begins.
If the installation application does not start automatically, you can start it
manually. Click Start > Programs > Command Prompt or Start > Run. Type
d:\setup in the Run window or at the command prompt (where d: is the CD
drive).
Alternatively, you can open Windows Explorer and double-click the setup.exe
file icon. If the Windows Installer service not installed on your computer, the
Client SDK package installs it for you. You must then reboot your computer
before you proceed with the Client SDK installation.
4. Click Next.
The License Agreement window opens.

© Copyright IBM Corp. 1996, 2011 6-1

 5. Click Next to accept the IBM Standard License.
a. Click to display the terms of the license.
The License panel detects the language that your system is using and
displays the terms in that language, when available. The default language
is English.
b. When the terms are displayed in a language other than English, you can
click View In English to view the terms in English or print the terms by
clicking Print.
The Customer Information window opens and displays the default user name
and organization name.
6. Click Next to accept the default user and organization names, or type in new
values and click Next.
The Setup Type window opens.
When you install Client SDK, Visual Studio .NET 2005 integration utilities
automatically start if .NET SDK 1.1 is detected by the installation application.
7. Select Complete setup to install all of the components into the default
directory (C:\Program Files\IBM\Informix\Client-SDK).
For a Custom setup, select Custom and click Next. When the Destination
Folder window opens, click Change to modify the destination folder, and then
click Next. When the Custom Setup window opens, clear the features that you
do not want to install and click Next.
The Ready to Install the Program window opens.
8. Click Next.
9. Click Install to begin the product installation.
10. To install the Data Server Driver, check the Launch the IBM Data Server
Driver Installation box and click Finish.
11. At the Data Server Driver Welcome screen, follow the prompts to complete the
DSD installation.

Installing IBM Informix Connect

Use the following instructions to install IBM Informix Connect.

Note: IBM Informix OLE DB Provider is a Custom installation option and is not
installed if you select a Typical installation. IBM Informix OLE DB Provider
installation requires administrative privileges.

To install IBM Informix Connect:

1. Exit all Windows programs.
2. Load the CD for IBM Informix Connect into the CD drive.
3. Read the readme.txt file in the root directory of the CD. This file might have
information you need before you continue.
4. Click Start > Programs > Command Prompt or Start > Run to start the Setup
utility.
5. In the Run dialog box or at the DOS prompt, type d:\setup (where d: is the
CD drive).
6. Press ENTER or click OK.
The Welcome window opens.
7. Click Next.
The User Information window opens.

6-2 Client Products Installation Guide

 8. Type your name and company name in the appropriate fields.
9. Click Next.
The Choose Destination Location window opens.
10. Type the directory where you want the IBM Informix product to be installed.
The default installation directory is C:\Program Files\ibm\informix\connect.
To select another directory, click Browse.
11. Click Next.
The Setup Type window opens.
12. Select an installation type: Typical or Custom.
13. Click Next.
If you select the Custom installation type, the Select Components window
opens. If you did not select Custom installation, go to step 16.
14. Check the boxes of the components and subcomponents that you want to
install.
Disk-space requirements are listed next to each component and
subcomponent.
15. Click Next.
The Select Program Folder window opens.
16. Specify the folder where you want to store Product Binaries.
For Typical mode, accept the default folder, which is C:\Program
Files\IBM\Informix\Connect or INFORMIX. For Custom mode, select
another existing folder, or type the name of a new folder to create.
17. Click Next.
The Start Copying Files window opens.
18. Click Next if all the information is correct. Click Back to return to previous
screens and change installation options.
19. If no errors occur during the installation procedure, the Setup Complete
window opens.
20. To install the Data Server Driver, check the Launch the IBM Data Server
Driver Installation box and click Finish.
21. At the Data Server Driver Welcome screen, follow the prompts to complete
the DSD installation.
22. Click Finish to exit Setup.

You might be prompted to reboot your computer at this point. If so, restarting
your computer now is recommended.

During this procedure, the Setup utility copies the client product software to your
computer, creates the Setnet32 icon and other icons in the INFORMIX program
folder, and creates the INFORMIX subkey of the Windows Registry.

If the Setup utility generates an error message, see “Common Installation

Problems” on page 7-5.

Installing Client SDK from the Command Line Using msiexec

You can install Client SDK from the command line by using the Windows Installer
API. To do this, the Windows Installer Service must be installed on your system.

Chapter 6. Installing Client SDK and Informix Connect on Windows Systems 6-3
 You can specify the type of installation by using msiexec command options. For
more information about the various command-line options for msiexec, see the
Windows Installer help on the Microsoft website.

You can specify the type of user interface that will be used during the installation
by using the /q command-line option. For instance, to run the install in silent
mode, with no error messages or end of installation indication, enter the following
command, where file pathname refers to the location of the .msi file on the media:
msiexec /i ".msi file pathname" /qn

To install Client SDK in silent mode, with no error messages, but with a window
at the end of the installation that indicates success or failure, enter the following
command:
msiexec /i ".msi file pathname" /qn+

Similarly, you can use the /qf and /qf+ options for a full user interface installation.
The /qf+ option displays a window at the end of the installation that indicates
success or failure.

Installing Client SDK with Silent Installation

You can specify an alternative value for INSTALLDIR on the command line. The
following methods can be used to install Client SDK or Informix Connect in silent
mode, where file pathname refers to the location of the .msi file on the media.

For all three methods if you do not include INSTALLDIR in the msiexec
command, the installation will use the following default values:
v Client SDK
drive\program files\informix\client-sdk
v Informix Connect
drive\program files\informix\connect
v Method 1
Use the following command
msiexec.exe /i ".msi file pathname" /qn+ INSTALLDIR="path of
installation location" /L*v log file name
v Method 2
Run the transformgenerator.exe file, which is included on the Client SDK media.
Provide the name and path of the .msi file and click OK. Use the following
command to perform a silent installation using the transform file:
msiexec.exe /i ".msi file pathname" /qn+
TRANSFORMS=".mst file pathname" INSTALLDIR="path of the
installation location" /L*v "log file name"
v Method 3
Use the following command:
setup.exe /s /v"TRANSFORMS=\".mst file name\"
INSTALLDIR=\"path of installation location\" /qn+ /L*v \"log
file name\""

Common msiexec Command Operations

The following table lists some common installation operations and their
corresponding command-line options.

6-4 Client Products Installation Guide

 Table 6-1. Common Installation Operations
Operation Command-line option
Install msiexec.exe /i ".msi file path name"
Uninstall msiexec.exe /x ".msi file path name"
Install to network msiexec.exe /a ".msi file path name"
Repair installation msiexec.exe /f ".msi file path name"
Advertise (to machine) msiexec.exe /jm ".msi file path name"
Advertise (to current user) msiexec.exe /ju ".msi file path name"

The msiexec command also accepts a product code instead of a path to an MSI
package.

Setting Public Properties

You can set public properties of an installation program (those properties with
uppercase names) at the command line. For example, an installation derives the
default user and company names from the Windows registry and stores them as
the public installer properties USERNAME and COMPANYNAME.

To set the user and company names at the command line, enter the following
command:
msiexec.exe /i ".msi file pathname"
COMPANYNAME="My company" USERNAME="username"

Property names are case sensitive. Enclose a property value in quotation marks if
the value contains any spaces.

You can also specify an alternative value for INSTALLDIR by using the following
command:
msiexec.exe /i ".msi file pathname"
INSTALLDIR="NewLocation path"

An administrator can prevent a product from being uninstalled by setting the

ARPNOREMOVE property to 1 at the command line. To prevent users from
modifying installed files, set ARPNOREMOVE to 1, and disable the Repair button
by setting ARPNOREPAIR to 1 in the Add/Remove Programs control panel.

Logging
Use the/L argument to msiexec to create a log file at setup runtime.

For example, to store all error and warning messages in a text log file, enter the
following command:
msiexec.exe /i ".msi file pathname" /L D:\install.log

To log every action performed by the setup program, use the following command:
msiexec.exe /i ".msi file pathname"
SERIALNUMBER="serial number"
KEY="key" /L*v D:\install.log

By default, the msiexec command creates a log file in the user's Temp folder only
when an error occurs.

Chapter 6. Installing Client SDK and Informix Connect on Windows Systems 6-5
 Installing Client SDK by Using the Command Line: Advertised
Mode
When you run an advertised installation of a product, all of the entry points of the
product, such as shortcuts or file types, are created on your computer, but no files
are physically copied until the user invokes a shortcut or opens a file of the
registered type.

Before you run the IBM Informix Client SDK installation in advertised mode, you
must generate a transform file by using the TransformGenerator tool on your CD.
This file is required to run the installation.

To generate a transform file:

1. Run TransformGenerator.exe from your product CD.
2. Enter the following information into the edit fields:
v Complete path of the IBM Informix Client SDK file
v Complete path where you want to save the generated transform file
3. Click OK.
The following message is displayed: Transform file generated successfully.
4. Use this transform file to run the advertised installation as shown in the
following command:
msiexec /jm ".msi file pathname" /t "transform (.mst) file pathname"

For more information about the command-line options for the Windows Installer
Service, see the help for Windows Installer Service, which is downloadable from
the Microsoft Web site.

Installing IBM Data Server Driver

You can install the IBM Data Server Driver Package as part of Client SDK or
Informix Connect installation, or you can install the driver separately later.

The option to install the IBM Data Server Driver is available at the end of a Client
SDK or Informix Connect installation in GUI or console mode.

If you do not install the driver as part of Client SDK or Informix Connect
installation, you can install it later.

If you are upgrading, repairing, or modifying your existing Client SDK or Informix
Connect installation, you can install the driver in either of the following ways:
v Uninstall your existing Client SDK or Informix Connect installation, start a new
installation of Client SDK or Informix Connect in GUI or console mode, and
select the IBM Data Server Driver installation option.
v Complete the Client SDK or Informix Connect upgrade or modification, and
then install the driver directly from the IBM Data Server Driver Package
directory in the top-level directory of the installation media.

6-6 Client Products Installation Guide

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

© Copyright IBM Corp. 1996, 2011 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 Client Products Installation Guide

 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

Chapter 7. Post-Installation Client Product Tasks on Windows Systems 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.50, 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 Overrides the Value For
WIN32HOST The HOST network parameter
WIN32USER The USER network parameter
WIN32PASS The PASSWORD network parameter
WIN32ASKPASSATCONNECT The PASSWORD OPTION network parameter
WIN32SERVICE The SERVICE network parameter
WIN32PROTOCOL 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 Client Products Installation Guide

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. Click Start > Settings > Control Panel > Administrative Tools.
2. Select Local Security Policy.
3. Expand the Local Policies folder.
4. Select Security Options.
5. 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.

Modifying the Installation

You can modify which components are installed by adding or removing Client
SDK features.

To modify the installation:

1. Click Start > Settings > Control Panel > Add/Remove Programs.
2. Click the Change or Remove Programs tab.
3. Select IBM Informix Client SDK.
4. Click Change.
The Informix Client SDK Setup window opens.
5. Click Next.
The Program Maintenance window opens.
6. Click Modify to change program features.
7. Click Next.
The Custom Setup window opens.
8. Click an icon to view the installation options.
9. Select an option from the drop-down list box.

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

 10. Click Next.
The Ready to Modify the Program window opens.
11. Click Install to modify the installation.
The IBM Informix Client SDK window opens.
12. Click Finish to complete the modification.

Repairing the Installation

You can repair errors in the installation procedure, such as missing or corrupted
files.

To repair the installation:

1. Click Start > Settings > Control Panel > Add/Remove Programs.
2. Click the Change or Remove Programs tab.
3. Select IBM Informix Client SDK.
4. Click Change.
The Informix Client SDK Setup window opens.
5. Click Next
6. Click Repair.
7. Click Next.
The Ready to Repair the Program window opens.
8. Click Install.
The IBM Informix Client SDK Setup box opens.
9. Click Finish to complete the repair.

7-6 Client Products Installation Guide

Chapter 8. Uninstalling Client SDK on Windows Systems
Uninstalling Client SDK by Using the Windows Control Panel
The Client SDK is available from two sources: CD and a downloadable network
installation. You must use the same source to uninstall the product that you used
to install it. In other words, you cannot install from the CD and then uninstall by
running the network installation.

To uninstall Client SDK from the Control Panel:

1. Click Start > Settings > Control Panel > Add/Remove Programs.
2. Click the Change or Remove Programs tab.
3. Select IBM Informix Client SDK from the list of applications.
4. Click Remove.
The IBM Informix Client SDK Setup window opens.
5. Click Next.
The Program Maintenance window opens.
6. Click Remove.
The Remove the Program window opens.
7. Click Remove to complete Client SDK file removal.

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.

Uninstalling Client SDK by Using the Command Line

You can uninstall Client SDK from your computer by using the command line.

You can uninstall Client SDK from your computer by entering the following
command, where file pathname refers to the location of the .msi file on the media:
msiexec /x ".msi file pathname"

© Copyright IBM Corp. 1996, 2011 8-1

8-2 Client Products Installation Guide
Part 3. Appendixes

© Copyright IBM Corp. 1996, 2011

Client Products Installation Guide
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.50, supports the following environment variables. For more
information about these environment variables, see their descriptions in the
respective publications.

Publication reference and possible

Environment variable Purpose values
CC8BITLEVEL Specifies how the C-language compiler IBM Informix GLS User's Guide
processes non-ASCII (8-bit and multibyte) Default is 2.
characters.
CLIENT_LOCALE Specifies the locale that the client application IBM Informix GLS User's Guide Any
uses to perform read/write operations that valid locale specifier. No default.
involve the keyboard, display, file, or printer
on the client computer.
COLLCHAR Specifies a collation sequence for characters. IBM Informix Guide to SQL:
Provided for backward compatibility with NLS Reference
products.
DB_LOCALE Specifies the locale of all the databases that a IBM Informix GLS User's Guide
client application accesses in a single
connection (the database locale).
DBALSBC When set to 1, enables compatibility with ALS IBM Informix ESQL/C Programmer's
products. Manual Values: 0 or 1
DBANSIWARN When turned on (y), causes the preprocessor IBM Informix Guide to SQL:
to check for Informix extensions to Reference Default is n.
ANSI-standard SQL syntax at compile time
and causes an application to check for
Informix extensions at run time.
DBAPICODE Enables pre-7.2 systems that use nonstandard IBM Informix ESQL/C Programmer's
or rare code sets to access databases that store Manual
data in a standard code set. Maximum size =
23 characters. Provided for backward
compatibility with NLS and ALS products.
DBASCIIBC When set to 1, enables compatibility with IBM Informix ESQL/C Programmer's
ASCII products. Manual Values: 0 or 1
DBCENTURY 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.
DBCODESET Provides support for Asian-locale code set. IBM Informix ESQL/C Programmer's
Overrides the code set that DB_LOCALE Manual Same values as ALS
specifies. Provided for backward compatibility DBAPICODE. Default is 8859-1:
with Version 4.x and 5.x ALS products. (unless the informix.rc file specifies
another system-wide default)

© Copyright IBM Corp. 1996, 2011 A-1

 Publication reference and possible
Environment variable Purpose values
DBCONNECT Specifies whether connections are restricted. IBM Informix ESQL/C Programmer's
Provides backward compatibility for client Manual Values: 1 or 3
applications that are based on earlier versions
of IBM Informix products.
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.
DBCSOVERRIDE Forces the user-specified DB_LOCALE value IBM Informix ESQL/C Programmer's
to override default restrictions on accessing Manual Values: 0 or 1
databases with locales that are different than
DB_LOCALE. Provided for backward
compatibility with Version 6.0 ALS database
servers.
DBCSWIDTH Maximum number of display bytes (1-2) and IBM Informix ESQL/C Programmer's
storage bytes (1-4) for the characters in up to Manual Example: 1,1:2,3 means a
three code sets. Display and storage widths display and storage width of 1
are separated by commas; code sets are byte for code set 1; a display width
separated by colons. Maximum size of this of 2 bytes and a storage width of 3
field is, therefore, 11 characters. Provided for bytes for code set 2.
backward compatibility with ALS products.
DBDATE Specifies the end-user format for DATE values Default is MDY4 unless NLS
so that they can conform with various variable LC_TIME is activated.
international date conventions. Provided for
backward compatibility with pre-7.2 products.
GL_DATE is recommended for 7.2 ESQL/C
applications.
DBFLTMASK Specifies the number of decimal digits to use IBM Informix Guide to SQL:
when storing a DECIMAL, SMALLFLOAT, or Reference Values: 0–16 Default is 16.
FLOAT data type in a character buffer
Dbaccess only.
DBLANG Specifies the subdirectory of the Informix IBM Informix Guide to SQL:
installation directory that contains the Reference Default is \msg.
product-specific message (.iem) files.
DBMONEY Specifies the end-user format for MONEY IBM Informix Guide to SQL:
values so that they can conform with various ReferenceIBM Informix GLS User's
international and local monetary conventions. Guide Default is $.,.
DBMONEYSCALE Specifies the total number of digits and IBM Informix ESQL/C Programmer's
number of decimal digits for monetary values. Manual
Provided for backward compatibility with ALS
products.
DBPATH Identifies the database servers that contain IBM Informix GLS User's Guide
databases that the application accesses.
DBSS2 Maximum size is four characters. Provided for IBM Informix ESQL/C Programmer's
backward compatibility with ALS products. ManualValues: 0x00–0xff or 0–255
DBSS3 Maximum size is four characters. Provided for IBM Informix ESQL/C Programmer's
backward compatibility with ALS products. Manual Values: 0x00–0xff or 0–255
DBTEMP Specifies the directory on the client computer IBM Informix Guide to SQL:
that the client processor uses to store Reference Default is \tmp.
temporary files (also called swap files).

A-2 Client Products Installation Guide

 Publication reference and possible
Environment variable Purpose values
DBTIME Specifies the end-user format for DATETIME IBM Informix Guide to SQL:
values so that they can conform with various Reference IBM Informix GLS User's
international date conventions. GL_DATETIME Guide Default is %Y-%m-%d
is recommended for 7.2 ESQL/C applications. %H:%M:%S.
Provided for backward compatibility with
pre-7.2 products.
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.
ESQLMF Indicates whether the ESQL/C processor IBM Informix GLS User's Guide
automatically invokes the ESQL/C multibyte
filter (value=1 and CC8BITLEVEL<3, or not
value=0).
FET_BUF_SIZE Overrides the default size of the fetch buffer. IBM Informix Guide to SQL:
Reference Any valid buffer size, in
bytes. Default value depends on
row size.
GL_DATE Specifies a customized end-user format for IBM Informix GLS User's Guide
DATE values.
GL_DATETIME Specifies a customized end-user format for IBM Informix GLS User's Guide
DATETIME values.
IFX_DISABLE_IPV6 Disables IPv6 support for a single database IBM Informix Administrator's
instance or for a single client application. GuideValues: yes or no. Default is
no.
IFX_FLAT_USCQ Overrides the global setting and directs the Default is 0.
optimizer to use subquery flattening for all
sessions.
INFORMIXCONRETRY Specifies the maximum number of additional IBM Informix Guide to SQL:
connection attempts made to a database server Reference Default is 1.
in the time limit that CONTIME specifies.
INFORMIXCONTIME Specifies the number of seconds an SQL IBM Informix Guide to SQL:
CONNECT statement continues to try to Reference Default is 60(seconds).
establish a connection before it generates an
error.
INFORMIXDIR Identifies the location of the client programs, IBM Informix Guide to SQL:
library files, message files, header files, and Reference Default is C:\INFORMIX.
other IBM Informix software components.
INFORMIXDIR must always be set.
INFORMIXSERVER Identifies the default database server. IBM Informix Guide to SQL:
Reference
INFORMIXSQLHOSTS Specifies the name of the computer on which IBM Informix Guide to SQL:
the central registry is located. Reference
LANG Specifies the language environment (called a IBM Informix ESQL/C Programmer's
locale) for an NLS database that an application Manual Default is C.
accesses. Provided for backward compatibility
with NLS products.
LC_COLLATE Specifies a collation or sort sequence for data IBM Informix ESQL/C Programmer's
in NCHAR and NVARCHAR columns of an Manual Default is the value that
NLS database. Provided for backward LANG specifies.
compatibility with NLS products.

Appendix A. Environment Variables A-3

 Publication reference and possible
Environment variable Purpose values
LC_CTYPE 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.
LC_MONETARY Specifies the end-user format for MONEY IBM Informix ESQL/C Programmer's
values in an NLS database. Provided for Manual Default is the value that
backward compatibility with NLS products. LANG specifies.
LC_NUMERIC Specifies the end-user format for numeric IBM Informix ESQL/C Programmer's
values in an NLS database. Provided for Manual Default is the value that
backward compatibility with NLS products. LANG specifies.
LC_TIME Specifies the end-user format for DATE and IBM Informix ESQL/C Programmer's
DATETIME values in an NLS database. Manual Default is the value that
Provided for backward compatibility with NLS LANG specifies.
products.
NODEFDAC Allows default table privileges for PUBLIC IBM Informix ESQL/C Programmer's
when a new table is created in a database that Manual Default is to allow
is not ANSI compliant. privileges.
OPTMSG Enables optimized message transfers (message IBM Informix Guide to SQL:
chaining) for all SQL statements in an Reference Default is the value that
application. LANG specifies.
OPTOFC Enables optimize-OPEN-FETCH-CLOSE IBM Informix Guide to SQL:
functionality in an IBM Informix ESQL/C Reference Default is the value that
application that uses DECLARE and OPEN LANG specifies.
statements to execute a cursor.
TMP Can be used to change the location temporary Any valid path.
space directory used during installation. This
is useful if there is not enough space in the
default /tmp directory.

A-4 Client Products Installation Guide

Appendix B. 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 Components Required at Runtime
IBM Informix Client SDK IBM Informix Connect
IBM Informix .NET Provider IBM Informix Connect
IBM Informix ESQL/C IBM Informix Connect
IBM Informix ODBC Driver IBM Informix Connect
IBM Informix Object Interface for C++ IBM Informix Connect
IBM Informix OLE DB Provider IBM Informix Connect (including MDAC,
obtained by recording a custom installation)
DataBlade API 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
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.

IBM Informix Client Application Distribution Options

The following sections explain your options for distributing your IBM Informix
client application and describe the agreements that you must make with IBM to
acquire the legal rights to redistribute IBM Informix client runtime components
with your application.

The following table lists the five options for distributing IBM Informix client
applications and refers you to detailed information about each option.

Option Agreement Required

Your customers order required components directly from IBM None
and install them themselves.

© Copyright IBM Corp. 1996, 2011 B-1

 Option Agreement Required
You ship the required components with your client Redistribution agreement
application; your customer installs them.
You ship required components on the same CD as your client Manufacturing agreement
application; your customer installs them.
You ship required components on the same CD as your client Manufacturing agreement
application; your customers install them silently when they
install your application.
You distribute your application within your company (not for Multiuser license (no
sale), and you distribute required components on the same special agreement);
CD as your client application; your customers install them Distribution limited to
silently when they install your application. number of licensed users

The following sections provide details about these agreements. These sections
primarily discuss IBM Informix Connect, which is the most commonly
redistributed runtime component.

Your customers order IBM Informix Connect directly from IBM

and install it themselves
These are the requirements when your customers order IBM Informix Connect
directly from IBM and install it themselves.

The installation documentation for your application must clearly tell your
customers that they are responsible for ordering IBM Informix Connect from IBM
and for installing it themselves. List the versions of IBM Informix Connect that you
tested with the application. The installation documentation for your application
must also supply the following information so that your customer can complete
the installation of IBM Informix Connect:
v Installation option: typical, compact, or custom. If customers need to use the
custom option, explain which components they must install.
v Destination directory
v Which directory to set as $INFORMIXDIR

Category Comment
Redistribution effort No need for you to redistribute IBM Informix Connect.
Ease of installation Your customer must acquire IBM Informix Connect from IBM and
install it separately; your customer might already have the correct
version of IBM Informix Connect installed.
Customer cost IBM Informix Connect is a free product. Your customers can
purchase technical support from IBM.
Version compatibility IBM might ship a version other than the version that you tested
your application with.

Risks:

Earlier version: the application might not work.

Later version: risk unknown because the combination of

application and IBM Informix Connect has not been tested. IBM
commits to backward compatibility of the runtime files, but
without testing, the risk cannot be assessed.

B-2 Client Products Installation Guide

 Category Comment
Technical support for Because your customer acquires IBM Informix Connect directly
your Customer from IBM, they can easily arrange for technical support and are
likely to address problems directly to IBM.

You ship the IBM Informix Connect product with your client
application; your customer installs it
These are the requirements when you ship the IBM Informix Connect product with
your client application and your customer installs it.

You must have redistribution rights through a contract with IBM, and you must
have pre-ordered the IBM Informix Connect product with license agreements.

In the installation documentation for your application, you must clearly state the
customer's responsibility for installing the version of IBM Informix Connect that is
supplied with the application. Supply your customers with the following
information so that they can install IBM Informix Connect:
v Installation option: typical, compact, or custom. If the custom option is required,
tell your customers which components they must install.
v Destination directory
v Which directory to set as $INFORMIXDIR

Category Comment
Redistribution effort You must include a copy of IBM Informix Connect with the
application distribution.
Ease of installation Your customer must separately install IBM Informix Connect;
customer might already have the correct version of IBM Informix
Connect installed.
Customer cost Your customers can purchase technical support from IBM.
Version compatibility IBM might ship a version other than the version that you tested
your application with.

Risks:

Earlier version: the application might not work.

Later version: risk unknown because the combination of

application and IBM Informix Connect has not been tested. IBM
commits to backward compatibility of the runtime files, but
without testing, the risk cannot be assessed.
Technical support for You have three options:
your Customer v Customers call you directly for support.
v You purchase support for each specific customer (you must
supply IBM with customer name) at the time of ordering
product and license agreements from IBM.
v You ask your customers to order technical support from IBM.

You ship IBM Informix Connect on the same CD as your client

application; your customer installs it
These are the requirements when you ship IBM Informix Connect on the same CD
as your client application and your customer installs it.

Appendix B. Distribute IBM Informix Client Applications and Components (Windows) B-3
 You must have a manufacturing contract or license with IBM. You have the option
of ordering license agreements in blocks or individually at point of sale. For details
about establishing such a relationship with IBM, call IBM Sales at 1-800-331-1763.

The application installation documentation must clearly state the customer's

responsibility for installing the version of Informix Connect that is supplied with
the application. Supply your customers with the following information so that they
can install Informix Connect:
v Where to find the IBM Informix Connect setup.exe file (either on its own CD or
in an Informix Connect directory on the application CD)
v Installation option: typical, compact, or custom. If the custom option is required,
tell your customers which components they must install.
v Destination directory
v Which directory to set as $INFORMIXDIR

Category Comment
Redistribution effort You must include a copy of Informix Connect with the application
distribution.
Ease of installation Your customer must separately install Informix Connect; customer
might already have the correct version of Informix Connect
installed.
Customer cost Your customers can purchase technical support from IBM.
Version compatibility IBM might ship a version other than the version that you tested
your application with.

Risks:

Earlier version: the application might not work.

Later version: risk unknown because the combination of

application and Informix Connect has not been tested. IBM
commits to backward compatibility of the runtime files, but
without testing, the risk cannot be assessed.
Technical support for You have three options:
your Customer v Customers call you directly for support.
v You purchase support for each specific customer (you must
supply IBM with customer name) at the time of ordering
product and license agreements from IBM.
v You ask your customers to order technical support from IBM.

You ship IBM Informix Connect on the same CD as your client

application; your customers install it silently when they install
your application
These are the requirements when you ship IBM Informix Connect on the same CD
as your client application and your customers install it silently when they install
your application.

You must have a manufacturing contract or license with IBM Informix Connect.
You have the option of ordering license agreements in blocks or individually at
point of sale. For details about establishing such a relationship with IBM, call IBM
Sales at 1-800-331-1763.

B-4 Client Products Installation Guide

 Record each Informix Connect installation. For details about recording an
installation, refer to Appendix C, “Installing IBM Informix Connect C and C++
Client Runtime Components,” on page C-1.

Also supply the customer with the license agreement.

Category Comment
Redistribution effort Must embed the Informix Connect installation program into the
application installation program.
Ease of installation Informix Connect is installed automatically for the customer.
Customer cost Technical support can be purchased.
Version compatibility IBM might ship a version other than the version that you tested
your application with.

Risks:

Earlier version: the application might not work.

Later version: risk unknown because the combination of

application and Informix Connect has not been tested. IBM
commits to backward compatibility of the runtime files, but
without testing, the risk cannot be assessed.
Technical support for You have three options:
your Customer v Customers call you directly for support.
v You purchase support for each specific customer (you must
supply IBM with customer name) at the time of ordering
product and license agreements from IBM.
v You ask your customers to order technical support from IBM.

For internal use: you ship IBM Informix Connect on the same
CD as your client application; your employees install it
silently when they install your application
These are the requirements when you ship IBM Informix Connect on the same CD
as your client application to your employees and your employees install it silently
when they install your application.

You must have a multiuser license of Informix Connect or a redistribution contract

or license with IBM. You agree to keep track of how many users are on the
Informix Connect license and to add users to this license when needed.

Record each Informix Connect installation. For details about recording an

installation, refer to Appendix C, “Installing IBM Informix Connect C and C++
Client Runtime Components,” on page C-1.

After your employees install Informix Connect, they are bound by the license
agreement.

Appendix B. Distribute IBM Informix Client Applications and Components (Windows) B-5
B-6 Client Products Installation Guide
Appendix C. Installing IBM Informix Connect C and C++ Client
Runtime Components
This section describes how to install C and C++ client runtime components.

To package IBM Informix Connect C and C++ client runtime components with
your client application and install them on your customers' computers:
1. Create an installation script for the client runtime components.
2. Create a client configuration file.
3. Create your client application installation program, which must invoke the
installation script that you created in step 1, and configure the client according
to the configuration file you that created in step 2.

The following sections tell you how to perform these steps.

Creating the Installation Script

Your client application installation program invokes the installation script to install
required IBM Informix Connect client runtime components when your customers
install your client application.

To create an installation script, use the InstallShield Setup utility to record the
installation of the IBM Informix Connect client runtime components that are
required by your client application.

Warning: If you record the installation process on a computer where

INFORMIXDIR has already been set, your installation script will fail to install
IBM Informix Connect client runtime components correctly.

To create the installation script:

1. Insert the Client SDK or Informix Connect installation disk in your CD drive.
2. Click Start > Run.
3. Open a DOS window by typing cmd.
4. In the DOS window, change directory to the directory on the CD that contains
the setup.exe file.
5. Enter the following command at the command prompt:
setup -r
The -r option records the options that you specify during installation to a file
named setup.iss in the Windows directory.
6. Install Client SDK or Informix Connect. Enter the options that you want your
customers to use with your client application.
For details about installing Client SDK, see “Installation System Requirements
for UNIX and Linux” on page 2-1.

© Copyright IBM Corp. 1996, 2011 C-1

Creating the Client Configuration File
When you create the client configuration file, the Setnet32 utility records the
desired client configuration. When your customers install the application, it uses
the client configuration file to invoke the Setnet32 utility.

To create the configuration file:

1. Launch the Setnet32 utility and specify the client computer settings that your
application requires.
2. Click Save to File.
3. Browse to the directory where you want the configuration file to be saved.
4. Enter a name for the file.
5. Click Save.
The file is saved with a .nfx file extension.

Creating Your Client Application Installation Program

Your client application installation program must meet certain criteria.

Your client application installation program must:

v install your application
v install required IBM Informix client runtime components
v configure the IBM Informix settings on your customer's computer

Instructions for completing these tasks are provided in the following sections.

Installing Client Runtime Components

When your customer installs your application, the IBM Informix components are
installed silently; that is, no installation windows are displayed while these
components are being installed.

To verify that the IBM Informix components were successfully installed, your
customer can check the installation log file. For details, see Appendix D, “Verifying
the Results of Silent Installation,” on page D-1.

When you prepare your installation media master, place all IBM Informix files
together in the same directory. These files include the CD image of the IBM
Informix client runtime components, the installation script (the setup.iss file), and
the client configuration file (the .nfx file).

To invoke the installation script from your client installation program:

1. Change directory to the directory that contains the CD image of the IBM
Informix client runtime components (which includes an IBM-supplied
setup.exe file that installs the client runtime components).
2. Enter the following command:
setup -s
The Setup program silently installs the Informix client runtime components.
When installation is complete, the Setup program creates a log file. For details
about logging, see Appendix D, “Verifying the Results of Silent Installation,” on
page D-1.

C-2 Client Products Installation Guide

 Requirement: You must install the Informix runtime components before you can
configure the client computer as described in the following section.

Configuring the Client Computer

To configure the customer's computer to run with your IBM Informix client
application, your client application installation program must invoke the IBM
Informix Setnet32 utility, which must specify the file in which you stored the
required client settings.

To configure the client computer from your client installation program:

1. Change to the directory that contains the CD image of the IBM Informix client
runtime components (which must include the .nfx file in which you stored the
desired client configuration settings).
2. Enter the following command:
setnet32 -l filename.nfx
In this example, filename refers to the file in which you stored the client
configuration settings.

Appendix C. Installing IBM Informix Connect C and C++ Client Runtime Components (Windows) C-3
C-4 Client Products Installation Guide
Appendix D. Verifying the Results of Silent Installation
When your client application installation program runs a silent installation script to
install IBM Informix client runtime components, InstallShield logs the results of
the silent installation.

Your customers or technical support representatives can check this log file to
determine whether the installation succeeded. By default, results are logged in a
file named setup.log that is located in the same directory as the CD image.

The setup.log file contains the following three sections:

v InstallShield Silent identifies the version of InstallShield Silent that was used in
the silent installation.
v Application identifies the installed application's name and version and the
company name.
v ResponseResult contains the result code that indicates whether the silent
installation succeeded. The following table lists the result codes that
InstallShield returns.
Table D-1. Description of Result Codes
Result Code Description
0 Installation was successful.
-1 General error occurred.
-2 Invalid mode specified.
-3 Required data not found in the setup.iss file.
-4 Not enough memory available.
-5 File does not exist.
-6 Cannot write to the installation script file.
-7 Unable to write to the log file.
-8 Invalid path to the InstallShield Silent installation script file was
specified.
-9 Not a valid list type (string or number).
-10 Data type is invalid.
-11 Unknown error occurred during setup.
-12 Dialog boxes are out of order.
-51 Cannot create the specified folder.
-52 Cannot access the specified file or folder.
-53 Invalid option selected.

The following example shows a log file for a successful silent installation:
[InstallShield Silent]
Version=v5.00.000
File=Log File

[Application]
Name=InstallShield5
Version=5.00.000

© Copyright IBM Corp. 1996, 2011 D-1

 Company=InstallShield

[ResponseResult]
ResultCode=0

D-2 Client Products Installation Guide

Appendix E. 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

© Copyright IBM Corp. 1996, 2011 E-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 refers 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
this example, if the FILE keyword is omitted, default FILE(KEEP) is used.

E-2 Client Products Installation Guide

 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 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 E. Accessibility E-3

E-4 Client Products Installation Guide
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.

© Copyright IBM Corp. 1996, 2011 F-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,

F-2 Client Products Installation Guide

 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 F-3
F-4 Client Products Installation Guide
Index
Special characters Database servers
identifying A-1
.app file 3-1 setting parameters in Setnet32 7-2
.dmg file 1-4, 3-1 DATE data type A-1
.iem file extension A-1 DATETIME data type A-1
.NET Provider viii DB_LOCALE environment variable A-1
.NET providers x, 5-2 DBALSBC environment variable A-1
DBANSIWARN environment variable A-1
DBAPICODE environment variable A-1
A DBASCIIBC environment variable A-1
Accessibility E-1 DBCENTURY environment variable A-1
dotted decimal format of syntax diagrams E-1 DBCSCONV environment variable A-1
keyboard E-1 DBCSOVERRIDE environment variable A-1
shortcut keys E-1 DBCSWIDTH environment variable A-1
syntax diagrams, reading in a screen reader E-1 DBDATE environment variable A-1
Advertising 6-6 DBFLTMASK environment variable A-1
DBMONEY environment variable A-1
DBMONEYSCALE environment variable A-1
C DBPATH environment variable A-1
DBSS2 environment variable A-1
CC8BITLEVEL environment variable A-1 DBSS3 environment variable A-1
Client Installation DBTEMP environment variable A-1
Windows 6-1 DBTIME environment variable A-1
Client Runtime Components DELIMIDENT environment variable A-1
installing C-1 Delimited identifiers A-1
Client SDK Disabilities, visual
distribution options, overview B-1 reading syntax diagrams E-1
Environment Variables A-1 Disability E-1
installing 6-1, C-2 Disk space 2-1
installing silently 6-4 Distribution options overview
installing using Windows program 6-1 Client SDK B-1
Runtime components B-1 doledbp.sql script 7-4
uninstall 8-1 Dotted decimal format of syntax diagrams E-1
Client SDK using a
GUI 8-1
Uninstalling 8-1
CLIENT_LOCALE environment variable A-1 E
coledbp.sql script 7-4 Enterprise Replication 6-1
COLLCHAR environment variable A-1 Environment configuration 7-1
Command line, installing from 6-4 environment variables 7-4
Command-line mode installation 2-2 Environment variables
Client SDK 2-9 CC8BITLEVEL A-1
Informix Connect 2-9 CLIENT_LOCALE A-1
Compatibility 2-2 COLLCHAR A-1
compliance with standards xvi Database locale, setting language features A-1
Configuring Database servers
Informix products 7-1 default A-1
the environment 7-1 DB_LOCALE A-1
Connect, redistribution guidelines B-1 DBALSBC A-1
Connection Manager viii DBANSIWARN A-1
Connections A-1 DBAPICODE A-1
cpio command 1-4 DBASCIIBC A-1
DBCENTURY A-1
DBCODESET A-1
D DBCONNECT environment variable A-1
DBCSCONV A-1
Data Server .NET Provider x DBCSOVERRIDE A-1
Data Server Driver, IBM DBCSWIDTH A-1
See IBM Data Server Driver DBDATE A-1
Database Add-Ins for Visual Studio viii DBFLTMASK A-1
Database Server requirements DBLANG environment variable A-1
Windows 5-1 DBMONEY A-1

© Copyright IBM Corp. 1996, 2011 X-1

Environment variables (continued) group informix 1-3, 3-1
DBMONEYSCALE A-1
DBPATH A-1
DBSS2 A-1
DBSS3 A-1
H
HKEY_CURRENT_USER 7-1
DBTEMP A-1
HKEY_LOCAL_MACHINE 7-1
DBTIME A-1
Host information, setting 7-3
DELIMIDENT A-1
Host parameters 7-3
Environment variables
DBCONNECT A-1
DBLANG A-1
INFORMIXCONTIME A-1 I
INFORMIXDIR A-1 IBM Data Server Driver x
INFORMIXSERVER A-1 IFX_FLAT_USCQ environment variable A-1
LANG A-1 ILogin utility viii
LC_COLLATE A-1 industry standards xvi
LC_CTYPE A-1 Informix .NET Provider x, 5-2
LC_MONETARY A-1 Informix Connect
LC_NUMERIC A-1 definition viii
LC_TIME A-1 installing 6-2
NODEFDAC A-1 redistribution guidelines B-1
OPTMSG A-1 INFORMIXCONRETRY environment variable A-1
OPTOFC A-1 Install medium 2-1
TMP A-1 Installation
ESQLMF A-1 Client runtime components C-1
FET_BUF_SIZE A-1 determining directory location 1-1
GL_DATE A-1 language compiler 5-2
GL_DATETIME A-1 order 5-2
IFX_FLAT_USCQ A-1 order of 1-2
INFORMIXCONRETRY A-1 problems 7-5
INFORMIXCONTIME environment variable A-1 procedure 2-2
INFORMIXSERVER environment variable A-1 repairing 7-6
INFORMIXSQLHOSTS A-1 running scripts for 2-2
INFORMIXSQLHOSTS environment variable A-1 silent 6-4
LANG environment variable A-1 using Setup 6-1
LC_COLLATE environment variable A-1 Installation script, recording C-1
LC_CTYPE environment variable A-1 installation, order 1-2
LC_MONETARY environment variable A-1 installclientsdk 2-3
LC_NUMERIC environment variable A-1 installconn 2-3
LC_TIME environment variable A-1 installing, Client SDK
Messages, optimized transfers A-1 from command-line 6-4
MONEY data type A-1 Installing, Client SDK C-2
NCHAR data type A-1 extraction With command-line script 2-8
NLS environment A-1 using Windows program 6-1
NODEFDAC environment variable A-1
NVARCHAR data type A-1
OPTMSG environment variable A-1
OPTOFC environment variable A-1
L
Language compiler 5-2
setting 7-1
Linux installation 1-1
TMP environment variable A-1
Log files 2-4
Environment Variables 7-4
creating 6-5
Client SDK A-1
Logging 6-5
Error log 2-4
ESQL/C viii
ESQLMF environment variable A-1
M
Mac OS X
F extracting installation media 1-4
installing client products 3-1
FET_BUF_SIZE environment variable A-1
Mac OS X installation 1-1
File extensions, .iem A-1
Message file A-1
Microsoft .NET Framework 5-2
Microsoft Visual C++ compiler 5-2
G MONEY data type A-1
GL_DATE environment variable A-1 msiexec command 6-4
GL_DATETIME environment variable A-1 MTS viii
GLS. viii

X-2 Client Products Installation Guide

N TCP/IP protocol
Windows 5-1
NLS environment A-1 Transform file 6-6
non-root installation 1-3 TransformGenerator.exe 6-6
Troubleshooting
common installation problems 7-5
O
Object Interface for C++ viii
ODBC-MTS viii U
OLE DB Provider viii, 7-4 Uninstallation
Order of installation 5-2 using a GUI 8-1
overriding information 7-4 Uninstalling
Overriding Information 7-4 command line 8-1
UNIX installation 1-1
user informix 1-3, 3-1
P
Password CSM viii
Processor, storing temporary files A-1 V
Product configuration 7-1 Visual disabilities
properties reading syntax diagrams E-1
silent .ini file 2-6
Protocols
Windows 5-1
Public properties W
setting 6-5 Windows
database server requirements 5-1
installing Client SDK 6-1
R system requirements 5-1
Windows Installer Service
Recording, installation script C-1 command line options 6-6
Runtime components described 6-4
Client SDK B-1 Windows Registry 7-2, 7-3

S
Screen reader
reading syntax diagrams E-1
Server parameters 7-2
services file 7-2
Setnet32 utility
product configuration 7-1
recording configuration C-2
silently configuring C-3
Setting environment variables 7-1
Shortcut keys
keyboard E-1
Silent install 6-4
Silent installation
verifying D-1
silent mode, installation in 2-6
Snow Leopard 3-1
SQL scripts
coledbp.sql 7-4
doledbp.sql 7-4
standards xvi
Syntax
client product install command 2-2
Syntax diagrams
reading in a screen reader E-1
System requirements
Windows 5-1

T
tar command 1-4

Index X-3
X-4 Client Products Installation Guide



Printed in USA

GC23-9413-06