IBM Informix


Version 3.0

IBM Informix Client Products Installation Guide

G229-6401-01
IBM Informix


Version 3.0

IBM Informix Client Products Installation Guide

G229-6401-01
 Note:
Before using this information and the product it supports, read the information in “Notices” on page D-1.

This edition replaces G229-6401-00.

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 International Business Machines Corporation 1996, 2007. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
In This Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Client SDK Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Software Dependencies (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Feature, Product, and Platform Markup . . . . . . . . . . . . . . . . . . . . . . . . . x
Example Code Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Compliance with Industry Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
How to Read a Command-Line Syntax Diagram . . . . . . . . . . . . . . . . . . . . . . xii
Keywords and Punctuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Identifiers and Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
IBM Welcomes Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Part 1. Installing Client Products on UNIX and Linux

Chapter 1. Preparing to Install Client SDK and IBM Informix Connect on UNIX and
Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
About Installing Client SDK and IBM Informix Connect . . . . . . . . . . . . . . . . . . . . 1-1
Determine Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Check Online Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Determine Installation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Prepare the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Creating the Group informix and User informix . . . . . . . . . . . . . . . . . . . . . . 1-4
Configure Your Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Load Product Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Chapter 2. Installing Client SDK on UNIX and Linux Systems . . . . . . . . . . . . 2-1

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Client SDK and IConnect as Part of the Informix Dynamic Server Installation Application . . . . . . . . . 2-2
Client SDK and IConnect with the 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 IConnect by Invoking the JAR File . . . . . . . . . . . . . . . . . . 2-10
Installing Client SDK or IConnect Using RPM Package Manager (Linux) . . . . . . . . . . . . . 2-11
Installing a Package File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Chapter 3. Post-Installation Client Products Tasks on UNIX and Linux . . . . . . . . 3-1

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Package-Manager Failures (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

© Copyright IBM Corp. 1996, 2007 iii

Chapter 4. Uninstalling Client SDK and IConnect on UNIX and Linux Systems . . . . 4-1
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling Using the Uninstall Application . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling in console (default) mode . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling in GUI mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling in silent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling After Using the Extraction Application with Command-Line Script . . . . . . . . . . . . 4-1
Uninstalling Using RPM (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Part 2. Installing Client Products on Microsoft Windows Systems

Chapter 5. Preparing to Install Client SDK on Windows Systems . . . . . . . . . . 5-1

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Prepare to Install Client SDK and IBM Informix Connect . . . . . . . . . . . . . . . . . . . . 5-1
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Database Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Protocol Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
C Compiler Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Microsoft Driver Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Installation Location and Order . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Install .NET Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Chapter 6. Installing Client SDK on Windows Systems . . . . . . . . . . . . . . . 6-1

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Installing Client SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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-4
Installing Client SDK with Silent Installation . . . . . . . . . . . . . . . . . . . . . . . 6-4
Common msiexec Command Operations . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Setting Public Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Installing Client SDK by Using the Command Line: Advertised Mode . . . . . . . . . . . . . . 6-6

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

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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-5
Common Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Modifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Repairing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

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

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Uninstalling Client SDK by Using the Windows Control Panel . . . . . . . . . . . . . . . . . . 8-1
Uninstall 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 Your IBM Informix Client Applications (Windows) . . . . . . . B-1

iv IBM Informix Client Products Installation Guide

In This Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Distribute IBM Informix Client Applications and Components . . . . . . . . . . . . . . . . . . B-1
Client Runtime Component Redistribution Guidelines . . . . . . . . . . . . . . . . . . . . B-1
IBM Informix Client Application Distribution Options . . . . . . . . . . . . . . . . . . . . B-2
Installing Informix C and C++ Client Runtime Components . . . . . . . . . . . . . . . . . . . B-6
Creating the Installation Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
Creating the Client Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Creating Your Client Application Installation Program . . . . . . . . . . . . . . . . . . . . B-7
Installing Client Runtime Components . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Configuring the Client Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Verifying the Results of Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . B-8

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

Accessibility features for IBM Informix Dynamic Server . . . . . . . . . . . . . . . . . . . . C-1
Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Keyboard Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Related Accessibility Information . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
IBM and Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Dotted Decimal Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

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

Contents v
vi IBM Informix Client Products Installation Guide
Introduction
In This Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Client SDK Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Software Dependencies (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Feature, Product, and Platform Markup . . . . . . . . . . . . . . . . . . . . . . . . . x
Example Code Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Compliance with Industry Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
How to Read a Command-Line Syntax Diagram . . . . . . . . . . . . . . . . . . . . . . xii
Keywords and Punctuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Identifiers and Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
IBM Welcomes Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

In This 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 Developer's
Kit (Client SDK), Version 3.0, and IBM Informix Connect, Version 3.0, on
computers that use UNIX®, Linux, and Windows. This publication is written for
database administrators or software engineers who are installing IBM Informix
client products, and assumes that you are familiar with the operating procedures
of your computer and with your operating systems.

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. IBM Informix Connect is
a runtime connectivity product composed of runtime libraries that are included in
Client SDK.

© Copyright IBM Corp. 1996, 2007 vii

 Table 1. Client SDK Components
Component Description
® ®
IBM Informix .NET The IBM Informix .NET Provider is a .NET assembly that lets
Provider .NET applications access and manipulate data in IBM Informix
(Windows® 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 an 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.
ESQL/C with XA An SQL embedded-language product that is used to create
support custom C applications.

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

Manual.
IBM Informix Object A C++ interface to develop object-oriented client applications for
Interface for C++ use with all Informix database servers and client-side value
objects for Dynamic Server.

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
locales that have defined conventions for a particular language,
culture, or code set.

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

Manual and the IBM Informix GLS User's Guide.
IBM Informix ODBC An Informix implementation of the Open Database Connectivity
Driver with MTS (ODBC) 3.0 Level 1+ standard that supports Microsoft
support Transaction Server (MTS). This driver contains extensibility
support for Dynamic Server.

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 functionality for base-level providers and contains extensibility
(Windows only) support for Dynamic Server.

For more information, see the IBM Informix OLE DB Provider

Programmer's Guide.
IBM Informix JDBC An Informix implementation of the Microsoft Java™ Database
Driver Connectivity (JDBC) standard.

For more information, see the IBM Informix JDBC Driver

Programmer's Guide.
Microsoft Data Access A component that upgrades elements of the Windows
Components environment, such as the Driver Manager.
(Windows only)
For more information, see the Microsoft Web site.

viii IBM Informix Client Products Installation Guide

 Table 1. Client SDK Components (continued)
Component Description
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 Dynamic Server Administrator's Guide.

Windows Only

Client SDK and IBM Informix Connect packages include the Setnet32 utility for
configuring client products. Each package might include online help, example
programs, and support programs
End of Windows Only

Software Dependencies (Linux)

If you have Linux installed on your computer, this publication assumes that RPM
Package Manager (RPM) is also installed. Most current Linux distributions include
RPM. For more information about RPM or to obtain a copy of RPM, see the RPM
Web site at www.rpm.org.

Documentation Conventions
This section describes the following conventions, which are used in the product
documentation for IBM Informix Dynamic Server:
v Typographical conventions
v Feature, product, and platform conventions
v Syntax diagrams
v Command-line conventions
v Example code conventions

Typographical Conventions
This publication uses the following conventions to introduce new terms, illustrate
screen displays, describe command syntax, and so forth.

Convention Meaning
KEYWORD Keywords of SQL, SPL, and some other programming languages appear
in uppercase letters in a serif font.
italics Within text, new terms and emphasized words appear in italics. Within
syntax and code examples, variable values that you are to specify
appear in italics.
boldface Names of program entities (such as classes, events, and tables),
environment variables, file names, path names, and interface elements
(such as icons, menu items, and buttons) appear in boldface.
monospace Information that the product displays and information that you enter
appear in a monospace typeface.
KEYSTROKE Keys that you are to press appear in uppercase letters in a sans serif
font.

Introduction ix
 Convention Meaning
> This symbol indicates a menu item. For example, “Choose Tools >
Options” means choose the Options item from the Tools menu.

Feature, Product, and Platform Markup

Feature, product, and platform markup identifies paragraphs that contain
feature-specific, product-specific, or platform-specific information. Some examples
of this markup follow:

Dynamic Server

Identifies information that is specific to IBM Informix Dynamic Server

End of Dynamic Server

Windows Only

Identifies information that is specific to the Windows operating system

End of Windows Only

This markup can apply to one or more paragraphs within a section. When an
entire section applies to a particular product or platform, this is noted as part of
the heading text, for example:
Table Sorting (Windows)

Example Code Conventions

Examples of SQL code occur throughout this publication. Except as noted, the code
is not specific to any single IBM Informix application development tool.

If only SQL statements are listed in the example, they are not delimited by
semicolons. For instance, you might see the code in the following example:
CONNECT TO stores_demo
...

DELETE FROM customer

WHERE customer_num = 121
...

COMMIT WORK
DISCONNECT CURRENT

To use this SQL code for a specific product, you must apply the syntax rules for
that product. For example, if you are using DB–Access, you must delimit multiple
statements with semicolons. If you are using an SQL API, you must use EXEC SQL
at the start of each statement and a semicolon (or other appropriate delimiter) at
the end of the statement.

Tip: Ellipsis points in a code example indicate that more code would be added in
a full application, but it is not necessary to show it to describe the concept
being discussed.

For detailed directions on using SQL statements for a particular application

development tool or SQL API, see the documentation for your product.

x IBM Informix Client Products Installation Guide

Additional Documentation
You can view, search, and print all of the product documentation from the IBM
Informix Dynamic Server information center on the Web at http://
publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp.

For additional documentation about IBM Informix Dynamic Server and related
products, including release notes, machine notes, and documentation notes, go to
the online product library page at http://www.ibm.com/software/data/informix/
pubs/library/. Alternatively, you can access or install the product documentation
from the Quick Start CD that is shipped with the product.

Compliance with Industry Standards

The American National Standards Institute (ANSI) and the International
Organization of Standardization (ISO) have jointly established a set of industry
standards for the Structured Query Language (SQL). 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.

Syntax Diagrams
This guide uses syntax diagrams built with the following components to describe
the syntax for statements and all commands other than system-level commands.
Table 2. 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-----+ One and only one item must
’---UNIQUE------’ be present.

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

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

Introduction xi
Table 2. Syntax Diagram Components (continued)
Component represented in PDF Component represented in HTML Meaning
.---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 will
be used as the 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------’

How to Read a Command-Line Syntax Diagram

The following command-line syntax diagram uses some of the elements 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

The second line in 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 in 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.

xii IBM Informix Client Products Installation Guide

 Setting the Run Mode:

l
c
-f
d u n N
p
a

To see how to construct a command correctly, start at the top left of the main
diagram. Follow the diagram to the right, including the elements that you want.
The elements in this diagram are case sensitive because they illustrate utility
syntax. Other types of syntax, such as SQL, are not case sensitive.

The Creating a No-Conversion Job diagram illustrates the following steps:

1. Type onpladm create job and then the name of the job.
2. Optionally, type -p and then the name of the project.
3. Type the following required elements:
v -n
v -d and the name of the device
v -D and the name of the database
v -t and the name of the table
4. Optionally, you can choose one or more of the following elements and repeat
them an arbitrary number of times:
v -S and the server name
v -T and the target server name
v The run mode. To set the run mode, follow the Setting the Run Mode
segment diagram to type -f, optionally type d, p, or a, and then optionally
type l or u.
5. Follow the diagram to the terminator.

Keywords and Punctuation

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

You must also use any punctuation in your statements and commands exactly as
shown in the syntax diagrams.

Identifiers and Names

Variables serve as placeholders for identifiers and names in the syntax diagrams
and examples. You can replace a variable with an arbitrary name, identifier, or
literal, depending on the context. Variables are also used to represent complex
syntax elements that are expanded in additional syntax diagrams. When a variable
appears in a syntax diagram, an example, or text, it is shown in lowercase italic.

The following syntax diagram uses variables to illustrate the general form of a
simple SELECT statement.

Introduction xiii


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.

IBM Welcomes Your Comments

We want to know about any corrections or clarifications that you would find
useful in our publications, which will help us improve future versions. Include the
following information:
v The name and version of the publication that you are using
v Section and page number
v Your suggestions about the publication

Send your comments to us at the following e-mail address:

[email protected]

This e-mail address is reserved for reporting errors and omissions in our
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.

xiv IBM Informix Client Products Installation Guide

Part 1. Installing Client Products on UNIX and Linux
This section discusses preparing to install IBM Informix client products on UNIX
and Linux® systems, explains the installation processes, and discusses
post-installation tasks and how to uninstall.

© Copyright IBM Corp. 1996, 2007

IBM Informix Client Products Installation Guide
Chapter 1. Preparing to Install Client SDK and IBM Informix
Connect on UNIX and Linux Systems
In This Chapter
This chapter discusses preparing to install IBM Informix Client Software
Developer’s Kit (Client SDK), Version 3.0, and IBM Informix Connect, Version 3.0
(IBM Informix Connect), on UNIX and Linux systems. For a comprehensive list of
Client SDK components, see the introduction.

About Installing Client SDK and IBM Informix Connect

Client SDK and IBM Informix Connect have numerous installation options.

Use the following methods to install IBM Informix Client Software Developer’s Kit
(Client SDK), Version 3.0 and IBM Informix Connect (IConnect), Version 3.0 on
UNIX or Linux :
v installation application
v command line
v Dynamic Server installation program
v RPM Package Manager (Linux only)
.

Before you install Client SDK or IConnect or connect a client application to a

database server, perform the following preliminary tasks:
v “Determine Location”
v “Check Online Files” on page 1-2
v “Determine Installation Order” on page 1-2
v “Prepare the Environment” on page 1-4
v “Configure Your Database Server” on page 1-4
v “Load Product Files” on page 1-4

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 reregistration and the written consent of IBM.

Determine Location
Take note of media location, install location, and (optionally) Java location.

Media Location

The directory where the media files reside is called $MEDIADIR. This can be on a
disk device, such as a CD, or a directory on a fileserver where the downloaded
source file is uncompressed.

© Copyright IBM Corp. 1996, 2007 1-1

 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 install directory as $INFORMIXDIR. If

$INFORMIXDIR is set in the environment, this will be the default install location.
When you install Client SDK and IBM Informix Connect with the installation
application, you can accept the default install directory or choose your own install
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. In addition, do not attempt to install a 32-bit version
and a 64-bit version of Client SDK in the same INFORMIXDIR
directory.

Java Location (Optional)

If an acceptable JVM is found in the $PATH, from $JAVAHOME, or

$JAVA_HOME, this will be used before the bundled JVM.

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 choose to 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.0x
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

1-2 IBM Informix Client Products Installation Guide

 Table 1-1. Order for Installing Client Products and Server Products in the Same
Directory (continued)
Database Versions of Client SDK and IBM Informix Connect
Server
Versions 2.7 and prior 2.8x 2.9x 3.0x
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.1 Client products Database server Database server Database server
first first first first

The following table describes database server versions and their corresponding
names.
Table 1-2. Database Server Version Numbers and Names
Database Server Database Server Name
Version Number
5.x IBM Informix OnLine and IBM Informix SE
7.2x IBM Informix OnLine Dynamic Server and IBM Informix SE
7.3x IBM Informix Dynamic Server
8.5x IBM Informix Extended Parallel Server (XPS)
9.1 through 9.13 IBM Informix Universal Server
9.14 IBM Informix Dynamic Server with Universal Data Option
9.2, 9.3, 9.4, 10.0, IBM Informix Dynamic Server
11.1

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 in the IBM Informix Library at
http://www.ibm.com/software/data/informix/pubs/library/.

Prior to the Client SDK, Version 2.01 release, clients and servers shared common
message files. In more recent 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 on the DSN Migration Utility in the release
notes for IBM Informix ODBC Driver.

Chapter 1. Preparing to Install Client SDK and IBM Informix Connect on UNIX and Linux Systems 1-3
Prepare the Environment
Prepare the environment for every shell within which you install or use IBM
Informix client products.

To find out if you need to apply patches to your computer, see the machine notes.

Creating the Group informix and User informix

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

Configure Your Database Server

Before you connect a client application to a database server, configure your
database server environment.

For more information, see your IBM Informix Administrator’s Guide and database
server installation guide.

Load Product Files

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:

1. Confirm that you are logged in as user root.
2. Access the installer directly from a CD.
3. To access the installer 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 installer in the current directory:
tar xvf filename

1-4 IBM Informix Client Products Installation Guide

 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 pathname of the cpio file that contains the
product files.

Chapter 1. Preparing to Install Client SDK and IBM Informix Connect on UNIX and Linux Systems 1-5
1-6 IBM Informix Client Products Installation Guide
Chapter 2. Installing Client SDK on UNIX and Linux Systems
In This Chapter
This chapter provides information to guide your installation of Client SDK and
IConnect on UNIX and Linux systems.

The following topics are discussed:

v “Installation Methods”
v “Client SDK and IConnect as Part of the Informix Dynamic Server Installation
Application” on page 2-2
v “Client SDK and IConnect with the Client Installation Application” on page 2-2
v “Installation Syntax” on page 2-2
v “Alternative Installation Methods” on page 2-5

Installation Methods
When you install client products on UNIX and Linux systems, you have several
options.

Your options are:

v Installing as part of the Informix Dynamic Server installation application
v Installing with the client installation application
v Installing using extraction with command-line script
v Installing by invoking the JAR file directly
v Installing with RPM Package Manager (Linux only)

Depending on the installation method you choose, you need differing amounts of
disk space, as describe in the following table.
Table 2-1. Installation Medium and Disk Space Required
Installation Medium and Method Products and Amount of Disk Space Required

Install from CD directly using the IConnect

installation application. Less than 135 MB
Client SDK
Less than 160 MB

Download the installation program IConnect

files to the installation machine. Less than 285 MB
Client SDK
Less than 310 MB

Using the extraction option and then IConnect

running command-line script. Less than 160 MB
Client SDK
Less than 185 MB

© Copyright IBM Corp. 1996, 2007 2-1

 Table 2-1. Installation Medium and Disk Space Required (continued)
Installation Medium and Method Products and Amount of Disk Space Required

Using the extraction option and then IConnect

running command-line script on 260-310 MB
Linux. (RPM files are copied in Client SDK
compressed form) 285-335 MB

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 above 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 IConnect as Part of the Informix Dynamic Server

Installation Application
You can install Client SDK or IConnect as part of the Informix Dynamic Server
installation application.

For information on this installation method, see the IBM Informix Dynamic Server
Installation Guide for UNIX and Linux or the Quick Beginnings for IBM Informix
Dynamic Server Express Edition.

Client SDK and IConnect with the Client Installation Application

This section describes how to install with the default (console) installation and GUI
installations.

For other methods, see “Alternative Installation Methods” on page 2-5.

Installation Syntax
The following syntax diagram illustrates the installation options.

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.

2-2 IBM Informix Client Products Installation Guide

 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.3.2 or
by the installation program higher.
logfilename Specifies a non-default log filename None
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 IConnect only
installclientsdk Install Client SDK 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 prior to 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 syntax diagram illustrates the installation options.

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 Client SDK or IBM Informix Connect in console mode:

1. As root, execute the command for the product you need to install, as shown in
“Installation Syntax” on page 2-2:
./installclientsdk
or
./installconn
The installation program begins in console mode.
2. Enter 1 to continue the installation procedure.
The Software License Agreement appears.

Chapter 2. Installing Client SDK on UNIX and Linux Systems 2-3

 3. Read the license agreement and accept the terms; then enter 1 to continue the
installation procedure.
4. Accept the default directory, or choose a different directory and enter 1 to
continue.
5. Choose Typical for the suggested setups or choose Custom for more
configuration options.
6. Enter 1 to continue the installation procedure.
The screen will show summary information including directory, components
installed, and total size.
7. 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 environment.

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 the Client SDK or IConnect in GUI mode:

1. As root, execute the command with for the product you need 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 program 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.

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:
- CSDK: $INFORMIXDIR/tmp/csdk-version-install.log
- IConnect: $INFORMIXDIR/tmp/iconnect-version-install.log
– For unsuccessful installations:
- CSDK: tempdir/informix/csdk-version-install.log
- IConnect: tempdir/informix/iconnect-version-install.log
v Product log files:
– CSDK: $INFORMIXDIR/tmp/csdklog.txt

2-4 IBM Informix Client Products Installation Guide

 – IConnect: $INFORMIXDIR/tmp/connlog.txt

Alternative Installation Methods

The following table compares four alternative methods for installing Client SDK
and IConnect. The table uses a Client SDK installation example for Format of
Command; for an IConnect installation, substitute the corresponding IConnect
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) that can be Unless you specify
mysilent.ini IConnect, with saved and reused as a -acceptlicense=yes on
product-specific template the command line, or set
command the -W lafiles.license
Accepted property to the
value of true, the
installation will not
continue.
Extraction with ./installclientsdk Use to install You use the extraction None
command-line -legacy Client SDK, or with command-line
script IConnect installation alternative
individually. when you want to
install the product to
redistribute it or when
you want to save space
or time on subsequent
installations.

In addition, you can

avoid using any JRE,
either local or bundled.
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
IConnect, with version of JRE 1.32 or
product-specific higher.
command
Using RPM rpm -iv --prefix Use to install You cannot perform a
Package $INFORMIXDIR Client SDK or silent installation with
Manager clientsdkcontent.rpm IConnect RPM. RPM requires that
(Linux only) individually you uninstall any
existing version of the
database server before
you install the new
version.

Installing in Silent Mode

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

Chapter 2. Installing Client SDK 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.
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.3.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 IConnect 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 prior to 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 IBM Informix 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 IConnect, 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)
Only either IConnect or the full Client
SDK can be installed at once. The cannot
both be installed into the same location.
-P iconnect.active= true (default) Indicates whether product or features is
selected for installation.
false
Only either IConnect or the full Client
SDK can be installed at once.
-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 on UNIX and Linux Systems 2-7

 3. As the root user, execute the silent installation of Client SDK or IConnect in the
following way:
installclientsdk -silent -options myclient.ini
or execute the silent installation of IConnect 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 IConnect 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.3.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 IConnect 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 prior to starting the extraction.

2-8 IBM Informix 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 uninstaller 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 IConnect 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 you had to run as the informix user.

Chapter 2. Installing Client SDK 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 IConnect .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.
Element Purpose Restrictions
relative_directory Specifies the path to the specified .jar file. If you None
execute the command from the directory where
the .jar file resides, do not specify a path.
logfile Specifies a non-default log filename 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.
Option Meaning
csdk.jar The installation application for Client SDK
conn.jar The installation application for IConnect
-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 prior to 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

Installing Client SDK or IConnect by Invoking the JAR File

You can install Client SDK or IConnect by invoking the JAR file directly.

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

2-10 IBM Informix Client Products Installation Guide

 1. 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 execute this command from the directory of the csdk.jar file.
2. Follow the procedure for installing with the application program. For more
information, see “Installing in Console Mode” on page 2-3.

Installing Client SDK or IConnect Using RPM Package

Manager (Linux)
Although you can use the installation application with both UNIX and Linux
systems, you can also manually install Client SDK and IConnect on Linux with
RPM Package Manager. This section describes how to install client products on
Linux operating systems when Linux RPM is enabled.

The default Linux location for IBM Informix products is /opt/informix. To use the
default, create an /opt/informix directory.

Restriction: You cannot perform a silent installation with RPM.

About Installing with RPM

The topic provides information on installing client products with RPM Package
Manager.

Installing client products with RPM Package Manager is a two-part process:

v Querying the Package Information
v Installing with Package Manager

Query the Package

To find out more about the product, including the complete release and update
number, use the RPM query option. The following table shows some examples. For
more options, see your RPM documentation.
Table 2-12. RPM Query Options
Command Purpose
rpm -qp * Queries the names of packages in the binary package files that
reside in the current directory
rpm -qpi *.rpm Queries detailed information about the binary package files (with
the filename extension .rpm) that reside in the current directory
rpm -qa Queries the names of the installed packages that are maintained in
the RPM database

The following table describes the command options that the preceding table uses.
For additional information on these options, see your RPM documentation.
Table 2-13. RPM Command Options
Option Explanation
a Queries all installed packages
i Displays package information, including name, version, and
description

Chapter 2. Installing Client SDK on UNIX and Linux Systems 2-11

 Table 2-13. RPM Command Options (continued)
Option Explanation
p packagefile Specifies an uninstalled RPM package packagefile where
packagefile might be a local file or the URL for a file that is
accessed through the Internet
q Specifies RPM query mode

Requirement: You must install the packages in the following order:

1. Message files
2. GLS
3. Client SDK or IBM Informix Connect

Installing a Package File

The steps below explain how to install a package file.

To install a package file:

1. Verify that you are logged in as root.
2. Mount the drive that contains the IBM Informix package files by using the
mount command.
3. Change the current directory to the location of the IBM Informix package files.
4. Optionally, check the package information as “About Installing with RPM” on
page 2-11 describes.
5. Load the contents of the IBM Informix package file under the directory that
INFORMIXDIR is set to, as the following example shows:
INFORMIXDIR=/opt/informix/LE
export INFORMIXDIR
In this example, INFORMIXDIR is set to /opt/informix/LE.
6. Install the package file by using the following command.
rpm -iv --force --prefix $INFORMIXDIR filename.rpm
7. Read and accept the terms of the license agreement.

2-12 IBM Informix Client Products Installation Guide

Chapter 3. Post-Installation Client Products Tasks on UNIX
and Linux
In This Chapter
This chapter discusses post-installation client products tasks on UNIX and Linux.

Package-Manager Failures (Linux)

The problems documented in this section might appear when you use the rpm
utility to load or unload an IBM Informix package.
v Problem. The command displays the following message:
ERROR: Failed to locate directory with write permissions.
Solution. Check that you are logged in as user root. Use the chmod command to
grant write permission on the current directory and then run the rpm command
again.
v Problem. The command displays one of the following messages:
ERROR: User informix must exist to install product.
ERROR: Group informix must exist to install product.
Solution. Follow the instructions in “Creating the Group informix and User
informix” on page 1-4 to create the necessary user or group.
v Problem. The command displays one of the following messages:
ERROR: You must be root to install product.
ERROR: You must be root to uninstall product.
Solution. Check that you are logged in as user root.
v Problem. The command displays the following message:
package product is already installed
ERROR: product.rpm cannot be installed
Solution. If you want to reinstall the product, uninstall the previous package.
v Problem. The rpm -e command displays the following message:
package product is not installed
Solution. You have probably misspelled the package name. Use the rpm -q
option to print the name, version, and release. Rerun the rpm -e command with
the correct specification for the package. For information about specifying a
package name, see “About Installing with RPM” on page 2-11
v Problem The command displays the following message:.
rpm: arguments to --relocate must begin with a /
Solution. Specify the absolute path, as the following example shows:
rpm -i --relocate /opt/informix=/$INFORMIXDIR filename.rpm

© Copyright IBM Corp. 1996, 2007 3-1

3-2 IBM Informix Client Products Installation Guide
Chapter 4. Uninstalling Client SDK and IConnect on UNIX and
Linux Systems
In This Chapter
This chapter discusses how to uninstall Client SDK and IConnect on UNIX and
Linux platforms.

Uninstalling Using the Uninstall Application

You can uninstall IBM Informix products on UNIX or Linux with the uninstall
program, in either console, graphical, or silent mode. Use the following procedures
to uninstall IBM Informix Client SDK and Connect.

Uninstalling in console (default) mode

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

To uninstall IBM Informix client products in GUI mode:
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 uninstall.

Uninstalling in silent mode

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

© Copyright IBM Corp. 1996, 2007 4-1

Uninstalling Using RPM (Linux)
To uninstall client products that you installed manually with RPM, follow the
procedures below.

You must query the package name before uninstalling and then specify that
package name when you run the uninstall command.

Note: If the same version of client product, or different versions, whose

subcomponents, such as GLS or messages, are installed on the same
machine, RPM might uninstall the wrong one.

To uninstall IBM Informix products on Linux using RPM:

1. Log in as root.
2. Run the command to query the package name.
3. Run the command to uninstall the package.
4. Repeat steps 2 and 3 for all product packages installed.
Table 4-1. Uninstalling with RPM
Command to Query
Product Package Package Name Command to Uninstall Package
Message files rpm -qf msg rpm -e msg -fullpackagename
GLS files rpm -qf msg rpm -e gls -fullpackagename
Client SDK rpm -qf bin/esql rpm -e csdk -fullpackagename
IConnect rpm -qf bin/esqlvers rpm -e iconn -fullpackagename

To discover which particular package or packages owns a file, run the rpm -qf
filename command.

For more information, see http://www.rpm.org or the rpm manual pages.

4-2 IBM Informix Client Products Installation Guide

Part 2. Installing Client Products on Microsoft Windows
Systems
This section discusses preparing to install IBM Informix client products on
Microsoft Windows systems, explains the installation processes, and discusses
post-installation tasks and how to uninstall.

© Copyright IBM Corp. 1996, 2007

IBM Informix Client Products Installation Guide
Chapter 5. Preparing to Install Client SDK on Windows
Systems
In This Chapter
This chapter discusses preparing to install IBM Informix Client Software
Developer’s Kit (Client SDK), Version 3.0, and IBM Informix Connect, Version 3.0,
on Windows systems.

For a comprehensive list of Client SDK components, see the Introduction.

Prepare to Install Client SDK and IBM Informix Connect

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 reregistration and the written consent of IBM.

Before you install Client SDK or IBM 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 IConnect on Windows systems, you must have

Administrator privileges.

System Requirements
The following list describes the system requirements for IBM Informix client
products for Microsoft Windows XP, Windows Server 2003 and Windows Vista
systems.
v Hardware: Pentium® 3 or higher microprocessor
v RAM: 256 megabytes
v Hard-disk storage: 75 megabytes

Database Server Requirements

You can use Client SDK, Version 3.0, and IBM Informix Connect, Version 3.0, 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.

© Copyright IBM Corp. 1996, 2007 5-1

 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.

Microsoft Driver Manager

Client SDK and IBM Informix Connect products include Microsoft Driver Manager,
Version 3.52, as a component of Microsoft Data Access Components (MDAC),
Version 2.7.

Find the Version Number of the Driver Manager

To find out what version of the Driver Manager is installed on your computer,
select Start > Settings > Control Panel > ODBC Data Sources to display the
ODBC Data Source Administrator window. If the window does not have an About
tab, your computer has a Driver Manager earlier than Version 3.0.

To find the version number of your Driver Manager:

1. Use Windows Explorer to locate your Windows system directory (SYSTEM32
directory on Windows 2000).
2. Select odbc32.dll and right click.
3. Click File Properties.
4. Click Version tab.
The Version page displays your Driver Manager version number.

Install the Driver Manager for Client SDK

If the version of MDAC installed on your computer is lower than Version 2.5, then
the Client SDK installation automatically updates it.

Install the Driver Manager for IBM Informix Connect

Use the Informix Setup utility to install Microsoft Driver Manager, Version 3.52.
When you run Setup, specify the Custom install option. You can only install
Microsoft Driver Manager, Version 3.52, by choosing MDAC, Version 2.5. You must
then reboot your computer.

To install an older version of Driver Manager than is currently installed on your

computer, first uninstall the newer version by using the appropriate uninstall
program.

Installation Location and Order

Before you install client products, verify that the installation location and the
installation order is correct.

Do not install Client SDK, Version 3.0, into a directory that contains a previous
version. Uninstall the previous version before you install Version 3.0 or follow the
instructions in “Common Installation Problems” on page 7-5.

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

5-2 IBM Informix Client Products Installation Guide

Install .NET Provider
Beginning with Client SDK, Version 2.9, the .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. IConnect only
requires the Microsoft .NET Framework Redistributable Package.

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

Chapter 5. Preparing to Install Client SDK on Windows Systems 5-3

5-4 IBM Informix Client Products Installation Guide
Chapter 6. Installing Client SDK on Windows Systems
In This Chapter
This chapter discusses installing IBM Informix Client Software Developer’s Kit
(Client SDK), Version 3.0, and IBM Informix Connect, Version 3.0, on Windows
systems.

Installing Client SDK

To install Client SDK on Windows systems, run the Windows installation program.
The Windows installation program allows you to install all components in a
default directory or you can select a different installation directory and choose
which components you want to install.

The IBM Informix Client SDK installation for Windows is based on the Microsoft
Windows Installer service. This service is built into Windows platforms. If this
service is not installed on your computer, the Client SDK installation program
installs it for you.

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 IConnect on Windows systems, you must have

Administrator privileges.

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 Dynamic Server 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. Follow the steps below 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. Read the readme.txt file in the root directory of the CD for the latest
installation information.
The installer starts automatically. The IBM Informix Client SDK Setup begins.
If the installer 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).

© Copyright IBM Corp. 1996, 2007 6-1

 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.
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 the Print.
The Customer Information window appears 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\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, unselect 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. Click Finish to complete the 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 choose 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.

6-2 IBM Informix Client Products Installation Guide

 The Welcome window opens.
7. Click Next.
The User Information window opens.
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:\INFORMIX. To choose another
directory, click Browse.
The Setup utility sets the INFORMIXDIR registry entry to the destination
directory you choose. IBM Informix software products are designed to be
installed in a single directory identified by this registry entry. If you install
IBM Informix products in different directories, only those in the directory
identified by the INFORMIXDIR registry entry can run.
11. Click Next.
The Setup Type window opens.
12. Select an installation type: Typical, Compact, 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 IBM Informix applications and
icons.
Accept the default (INFORMIX), choose 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. 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.

Chapter 6. Installing Client SDK on Windows Systems 6-3

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.

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
Microsoft Windows Installer help on the Microsoft Web site.

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 IConnect 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 IConnect
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\""

6-4 IBM Informix Client Products Installation Guide

Common msiexec Command Operations
The following table lists some common installer operations and their
corresponding command-line options.
Table 6-1. Common Installer 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 /ju ″.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 with upper case
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, which passes the e and w arguments to /l:
msiexec.exe /i ".msi file pathname" /Lew D:\install.log

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

Chapter 6. Installing Client SDK on Windows Systems 6-5

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

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.

6-6 IBM Informix Client Products Installation Guide

Chapter 7. Post-Installation Client Product Tasks on Windows
Systems
In This Chapter
This chapter discusses post-installation tasks for IBM Informix Client Software
Developer’s Kit (Client SDK), Version 3.0, and IBM Informix Connect, Version 3.0,
on Windows systems.

These tasks include:

v configuring
v solving problems
v modifying the installation
v repairing the installation

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,” below
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 need to 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
Informix Setnet32 window opens.
2. Click the Environment tab to display the Environment page, which has the
following elements:

© Copyright IBM Corp. 1996, 2007 7-1

 v 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
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, deselect 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 HostName

7-2 IBM Informix Client Products Installation Guide

 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.

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

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

 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
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, as well as 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.0, 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

7-4 IBM Informix Client Products Installation Guide

Configuring OLE DB Provider
To enable your 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.

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-

306.ibm.com/software/data/informix/support/contact.html.

If you receive your IBM Informix product materials from an Electronic Software
Download (ESD) vendor, consult the vendor documentation for information on
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 Microsoft Windows security error that occurs when the
Windows Installer 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 drive 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.
v Problem. You receive the following error message:
Error: file reading error
Solution. The installation program is unable to read the media. Try loading the
CD again. If the error persists, you might have corrupted hardware or media.
See your system administrator.
v Problem. You receive the following error message:
Invalid Processor: Error
Solution. Use a computer with an Intel® 80486 or higher microprocessor.
v Problem. You receive the following error message:
Invalid OS: Error

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

 Solution. Your client computer has an unsupported operating system. Use
Windows 2000.
v Problem. You receive the following error message:
Not enough disk space - Error
Solution. Make more space available on the disk on which you want to install the
product or choose a new disk location. For more information, see “System
Requirements” on page 5-1.
v Problem. You receive the following error message:
Call to GetFileInfo for <install directory> failed
Solution. Run the installation again. In the Choose Destination Location window,
click Browse. The directory that is displayed is the same as the one previously
displayed, except that the backslash (\) character is deleted from the end. Click
OK and proceed with the installation.

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.
10. Click Next.
The Ready to Modify the Program window opens.
11. Click Install to modify the installation.
The 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 corrupt 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

7-6 IBM Informix Client Products Installation Guide

6. Click Repair.
7. Click Next.
The Ready to Repair the Program window opens.
8. Click Install.
The Informix Client SDK Setup box appears.
9. Click Finish to complete the repair.

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

7-8 IBM Informix Client Products Installation Guide
Chapter 8. Uninstalling Client SDK on Windows Systems
In This Chapter
This chapter discusses uninstalling IBM Informix Client Software Developer’s Kit
(Client SDK), Version 3.0, and IBM Informix Connect, Version 3.0, on Windows
systems.

Uninstalling Client SDK completely removes the driver and all its components
from your computer.

To install a previous version of Client SDK in a directory that contains Version 3.0,
uninstall Version 3.0 before you proceed.

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 choose to 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 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.

Uninstall 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, 2007 8-1

8-2 IBM Informix Client Products Installation Guide
Part 3. Appendixes

© Copyright IBM Corp. 1996, 2007

IBM Informix 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.0, supports the following environment variables. For more
information about these environment variables, see their descriptions in the
respective publications.

Publication Reference and

Environment Variable Purpose Possible 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, 2007 A-1

 Publication Reference and
Environment Variable Purpose Possible 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 IBM Informix GLS User’s
product-specific message (.iem) files. Guide Default is \msg.
DBMONEY Specifies the end-user format for MONEY IBM Informix Guide to SQL:
values so that they can conform with various Reference IBM 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.
DBNLS Specifies whether an application can access IBM Informix ESQL/C Programmer’s
NLS features. Provided for backward Manual Default is n.
compatibility with NLS products.
DBPATH Identifies the database servers that contain IBM Informix Guide to SQL:
databases that the application accesses. Reference
DBSS2 Maximum size is four characters. Provided for IBM Informix ESQL/C Programmer’s
backward compatibility with ALS products. Manual Values: 0x00–0xffor 0–255
DBSS3 Maximum size is four characters. Provided for IBM Informix ESQL/C Programmer’s
backward compatibility with ALS products. Manual Values: 0x00–0xffor 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 IBM Informix Client Products Installation Guide

 Publication Reference and
Environment Variable Purpose Possible 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 not (n) to interpret IBM Informix Guide to SQL:
strings in double quotes 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_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 resides. 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
Environment Variable Purpose Possible 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 IBM Informix Client Products Installation Guide

Appendix B. Distribute Your IBM Informix Client Applications
(Windows)
In This Appendix
This appendix discusses the technical and legal requirements that you must
observe when you distribute applications that are created using IBM Informix
client APIs (such as IBM Informix ESQL/C and IBM Informix ODBC Driver) on
Windows platforms.

With your client application files, you might distribute and install IBM Informix
client runtime components that are required by your application.

To install these components, you can either:

v Require your customers to install the components separately
v Record the installation process and run the resulting script as part of your client
application’s installation program

By using prerecorded installation scripts to install and configure IBM Informix

client APIs , you can enable your customers to bypass the installation windows
that normally are displayed. Such an installation is referred to as a silent
installation.

Distribute IBM Informix Client Applications and Components

When you distribute a client application that you developed by using an IBM
Informix client API, you might decide to distribute Informix components that are
required by your application at runtime.

The following table lists the Informix components that your customer needs in
order to run your client application.
Table B-1. 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-DB2 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

Informix runtime components can be redistributed.

You can redistribute Informix runtime components in the following two ways:

© Copyright IBM Corp. 1996, 2007 B-1

 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)

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

To redistribute Informix client runtime components, run the Informix installation

program and use InstallShield to record the installation procedure. You invoke the
resulting installation script from your client application installation program.

When you package your client application for distribution to your users, you must
provide the user with the CD image of the Informix client runtime components. If
you created your client application by using Client SDK, you must include the
following two files, which are created when you record the installation:
v setup.iss (recorded install options)
v filename.nfx (recorded configuration with the filename of your choice)

For details about how to combine the installation of Informix client runtime
components with the installation of your client application, refer to “Creating the
Installation Script” on page B-6 and “Creating Your Client Application Installation
Program” on page B-7.

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 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. Refer to page A3.
You ship the required components with your client Redistribution agreement
application; your customer installs them. Refer to page A4.
You ship required components on the same CD as your client Manufacturing agreement
application; your customer installs them. Refer to page A4.
You ship required components on the same CD as your client Manufacturing agreement
application; your customers install them silently when they
install your application. Refer to page A5.
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. Refer to page A6. number of licensed users

For details about establishing a relationship with IBM, call IBM Sales at
1-800-331-1763.

B-2 IBM Informix Client Products Installation Guide

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

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

 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.

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 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 Where to find the IBM Informix Connect setup.exe file (either on its own CD or
in an IBM 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 IBM Informix Connect with the
application distribution.

B-4 IBM Informix Client Products Installation Guide

Category Comment
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 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 Informix. 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.

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

Also supply the customer with the license agreement.

Category Comment
Redistribution effort Must embed the IBM Informix Connect installation program into
the application installation program.
Ease of installation IBM Informix Connect is installed automatically for the customer.
Customer cost Technical support can be purchased.

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

 Category Comment
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.

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 IBM Informix Connect or a redistribution

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

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

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

Installing Informix C and C++ Client Runtime Components

This section describes how to install C and C++ client runtime components.

To package Informix 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 Informix client runtime components when your customers install your
client application.

B-6 IBM Informix Client Products Installation Guide

 To create an installation script, use the InstallShield Setup utility to record the
installation of the Informix 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 Informix client runtime components correctly.

To create the installation script:

1. Insert the Client SDK or IBM 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 IBM Informix Connect. Enter the options that you want
your customers to use with your client application.
For details about installing Client SDK, see “Installation Methods” on page 2-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 Informix client runtime components
v configure the Informix settings on your customer’s computer

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

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

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

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

When you prepare your installation media master, place all Informix files together
in the same directory. These files include the CD image of the 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 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 “Verifying the Results of Silent Installation.”

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

Verifying the Results of Silent Installation

When your client application installation program runs a silent installation script to
install 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.

B-8 IBM Informix Client Products Installation Guide

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 B-2. 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
Company=InstallShield

[ResponseResult]
ResultCode=0

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

B-10 IBM Informix Client Products Installation Guide
Appendix C. Accessibility
IBM strives to provide products with usable access for everyone, regardless of age
or ability.

Accessibility features for IBM Informix Dynamic Server

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
Dynamic Server. 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 IBM Informix Dynamic Server Information Center and its related
publications are accessibility-enabled for the IBM Home Page Reader. You
can operate all features 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. The syntax
diagrams in our manuals are available in dotted decimal format. For more
information about the dotted decimal format, go to “Dotted Decimal Syntax
Diagrams.”

You can view the publications for IBM Informix Dynamic Server in Adobe Portable
Document Format (PDF) using the Adobe Acrobat Reader.

IBM and Accessibility

See the IBM Accessibility Center at http://www.ibm.com/able for more information
about the commitment that IBM has 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.

© Copyright IBM Corp. 1996, 2007 C-1

 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
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, this identifies a reference that is

defined elsewhere. The string following the % symbol is the name of a syntax
fragment rather than a literal. For example, the line 2.1 %OP1 means that you
should refer to a separate syntax fragment OP1.

The following words and symbols are used next to the dotted decimal numbers:
? Specifies an optional syntax element. A dotted decimal number followed
by the ? symbol indicates that all the syntax elements with a
corresponding dotted decimal number, and any subordinate syntax
elements, are optional. If there is only one syntax element with a dotted
decimal number, the ? symbol is displayed on the same line as the syntax
element (for example, 5? NOTIFY). If there is more than one syntax element
with a dotted decimal number, the ? symbol is displayed on a line by
itself, followed by the syntax elements that are optional. For example, if
you hear the lines 5 ?, 5 NOTIFY, and 5 UPDATE, you know that syntax
elements NOTIFY and UPDATE are optional; that is, you can choose one or
none of them. The ? symbol is equivalent to a bypass line in a railroad
diagram.
! Specifies a default syntax element. A dotted decimal number followed by
the ! symbol and a syntax element indicates that the syntax element is the
default option for all syntax elements that share the same dotted decimal
number. Only one of the syntax elements that share the same dotted
decimal number can specify a ! symbol. For example, if you hear the lines

C-2 IBM Informix Client Products Installation Guide

 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.
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 could write HOST STATE, but you could not write
HOST HOST.
3. The * symbol is equivalent to a loop-back line in a railroad syntax
diagram.
+ Specifies a syntax element that must be included one or more times. A
dotted decimal number followed by the + symbol indicates that this syntax
element must be included one or more times. For example, if you hear the
line 6.1+ data-area, you must include at least one data area. If you hear
the lines 2+, 2 HOST, and 2 STATE, you know that you must include HOST,
STATE, or both. As for the * symbol, you can only repeat a particular item if
it is the only item with that dotted decimal number. The + symbol, like the
* symbol, is equivalent to a loop-back line in a railroad syntax diagram.

Appendix C. Accessibility C-3

C-4 IBM Informix Client Products Installation Guide
Notices
IBM may not offer the products, services, or features discussed in this document in
all 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 give 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:
IBM World Trade Asia Corporation Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, 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 Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

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

© Copyright IBM Corp. 1996, 2007 D-1

 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 information 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 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,
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. You may copy,
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 IBM’s application programming interfaces.

D-2 IBM Informix Client Products Installation Guide

 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
The following terms are used in one or more IBM Informix product publications
and the terms are trademarks of International Business Machines Corporation in
the United States, other countries, or both:

AIX MQSeries
C-ISAM NUMA-Q
Cloudscape OS/2
DataBlade OS/390
DB2 OS/400
DB2 Connect RedBack
DB2 Universal Database Red Brick
Distributed Relational Database Architecture RETAIN
Dynamic Connect SystemBuilder
IBM UniData
Informix UniVerse

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either
registered trademarks or trademarks of Adobe Systems Incorporated in the United
States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, 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 of Sun Microsystems,
Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo 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.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Other company, product, or service names may be trademarks or service marks of

others.

Notices D-3
D-4 IBM Informix Client Products Installation Guide
Index
Special characters DBANSIWARN environment variable A-1
DBAPICODE environment variable A-1
/opt/informix directory 2-11 DBASCIIBC environment variable A-1
.iem file extension A-2 DBCENTURY environment variable A-1
.NET Provider, installing 5-3 DBCONNECT environment variable A-1, A-2
DBCSCONV environment variable A-2
DBCSOVERRIDE environment variable A-2
A DBCSWIDTH environment variable A-2
accessibility C-1 DBDATE environment variable A-2
keyboard C-1 DBFLTMASK environment variable A-2
shortcut keys C-1 DBLANG environment variable A-2
Accessibility DBMONEY environment variable A-2
dotted decimal format of syntax diagrams C-1 DBMONEYSCALE environment variable A-2
syntax diagrams, reading in a screen reader C-1 DBNLS environment variable A-2
Advertising 6-6 DBPATH environment variable A-2
DBSS2 environment variable A-2
DBSS3 environment variable A-2
C DBTEMP environment variable A-2
DBTIME environment variable A-3
CC8BITLEVEL environment variable A-1 Default installation directory 2-11
Client Installation DELIMIDENT environment variable A-3
Windows 6-1 Delimited identifiers A-3
Client Runtime Components Disabilities, visual
installing B-6 reading syntax diagrams C-1
Client SDK disability C-1
distribution options, overview B-2 Disk space 2-1
Environment Variables A-1 Distribution options overview
installing 6-1, B-8 Client SDK B-2
installing silently 6-4 doledbp.sql script 7-5
installing using Windows program 6-1 Dotted decimal format of syntax diagrams C-1
Runtime components B-1
uninstalling 8-1
CLIENT_LOCALE environment variable A-1
coledbp.sql script 7-5 E
COLLCHAR environment variable A-1 Enterprise Replication 6-1
Command line, installing from 6-4 Environment configuration 7-1
Command-line mode installation environment variables 7-4
Client SDK 2-9 Environment variables
Informix Connect 2-9 CC8BITLEVEL A-1
Compatibility 2-2 CLIENT_LOCALE A-1
Configuring COLLCHAR A-1
Informix products 7-1 DB_LOCALE A-1
the environment 7-1 DBALSBC A-1
Connect, redistribution guidelines B-1 DBANSIWARN A-1
Connections A-3 DBAPICODE A-1
console mode, installation 2-4 DBASCIIBC A-1
cpio command 1-4 DBCENTURY A-1
DBCODESET A-1
DBCONNECT A-2
D DBCSCONV A-2
DBCSOVERRIDE A-2
Database locale, setting language features A-3 DBCSWIDTH A-2
Database Server requirements DBDATE A-2
Windows 5-1 DBFLTMASK A-2
Database servers DBLANG A-2
default A-3 DBMONEY A-2
identifying A-2 DBMONEYSCALE A-2
setting parameters in Setnet32 7-2 DBNLS A-2
DATE data type A-2 DBPATH A-2
DATETIME data type A-3 DBSS2 A-2
DB_LOCALE environment variable A-1 DBSS3 A-2
DBALSBC environment variable A-1 DBTEMP A-2

© Copyright IBM Corp. 1996, 2007 X-1

Environment variables (continued) Installation (continued)
DBTIME A-3 procedure 2-2
DELIMIDENT A-3 repairing 7-6
ESQLMF A-3 running scripts for 2-2
FET_BUF_SIZE A-3 silent 6-4
GL_DATE A-3 using Setup 6-1
GL_DATETIME A-3 Installation script, recording B-7
IFX_FLAT_USCQ A-3 installation, order 1-2
INFORMIXCONRETRY A-3 installclientsdk 2-3
INFORMIXCONTIME A-3 installconn 2-3
INFORMIXDIR A-3 installing, Client SDK
INFORMIXSERVER A-3 from command-line 6-4
INFORMIXSQLHOSTS A-3 Installing, Client SDK B-8
LANG A-3 extraction With command-line script 2-8
LC_COLLATE A-3 using Windows program 6-1
LC_CTYPE A-4
LC_MONETARY A-4
LC_NUMERIC A-4
LC_TIME A-4
L
LANG environment variable A-3
NODEFDAC A-4
Language compiler 5-2
OPTMSG A-4
LC_COLLATE environment variable A-3
OPTOFC A-4
LC_CTYPE environment variable A-4
setting 7-1
LC_MONETARY environment variable A-4
TMP A-4
LC_NUMERIC environment variable A-4
Environment Variables 7-4
LC_TIME environment variable A-4
Client SDK A-1
Linux installation 1-1, 2-11
Error log 2-4
Log files 2-4
ESQLMF environment variable A-3
creating 6-5
Logging 6-5

F
FET_BUF_SIZE environment variable
File extensions, .iem A-2
A-3 M
Message file A-2
Messages, optimized transfers A-4
Microsoft .NET Framework 5-3
G Microsoft Visual C++ compiler 5-2
GL_DATE environment variable A-3 MONEY data type A-2, A-4
GL_DATETIME environment variable A-3 msiexec command 6-4
group informix 1-4

N
H NCHAR data type A-3, A-4
HKEY_CURRENT_USER 7-1 NLS environment A-2, A-3, A-4
HKEY_LOCAL_MACHINE 7-1 NODEFDAC environment variable A-4
Host information, setting 7-3 NVARCHAR data type A-3, A-4
Host parameters 7-3

O
I ODBC Driver Manager
IBM Informix Connect installing 5-2
installing 6-2 OLE DB Provider 7-5
redistribution guidelines B-1 OPTMSG environment variable A-4
IFX_FLAT_USCQ environment variable A-3 OPTOFC environment variable A-4
INFORMIXCONRETRY environment variable A-3 Order of installation 5-2
INFORMIXCONTIME environment variable A-3 overriding information 7-4
INFORMIXSERVER environment variable A-3 Overriding Information 7-4
INFORMIXSQLHOSTS environment variable A-3
Install medium 2-1
Installation
Client runtime components B-6
P
Processor, storing temporary files A-2
determining directory location 1-1
Product configuration 7-1
language compiler 5-2
properties
order 5-2
silent ini file 2-6
order of 1-2
Protocols
problems 7-5
Windows 5-1

X-2 IBM Informix Client Products Installation Guide

Public properties
setting 6-5
W
Windows
database server requirements 5-1
installing Client SDK 6-1
R system requirements 5-1
Recording, installation script B-7 Windows Installer Service
RPM 2-11 command line options 6-6
printing package information 2-11 described 6-4
querying Informix binary packages 2-11 Windows Registry 7-2, 7-3
uninstalling packages 4-2
rpm command, examples 2-12
RPM Package Manager 1-1
Runtime components
Client SDK B-1

S
Screen reader
reading syntax diagrams C-1
Server parameters 7-2
services file 7-2
Setnet32 utility
product configuration 7-1
recording configuration B-7
silently configuring B-8
Setting environment variables 7-1
shortcut keys
keyboard C-1
Silent install 6-4
Silent installation
verifying B-8
silent mode, installation in 2-6
silent.ini file
properties 2-6
SQL scripts
coledbp.sql 7-5
doledbp.sql 7-5
Syntax diagrams
reading in a screen reader C-1
System requirements
Windows 5-1

T
tar command 1-4
TCP/IP protocol
Windows 5-1
TMP environment variable A-4
Transform file 6-6
TransformGenerator.exe 6-6
Troubleshooting
common installation problems 7-5

U
Uninstalling
command line 8-1
using RPM 4-2
Uninstalling Client SDK 8-1
user informix 1-4

V
Visual disabilities
reading syntax diagrams C-1

Index X-3
X-4 IBM Informix Client Products Installation Guide



Printed in USA

G229-6401-01