DB2 Connect EE Quick Beginnings

DB2 Connect EE Quick Beginnings
®
IBM DB2 Connect
™
™
Quick Beginnings for DB2 Connect
Enterprise Edition
Version 8
GC09-4833-00
®
IBM DB2 Connect
™
™
Quick Beginnings for DB2 Connect
Enterprise Edition
Version 8
GC09-4833-00
Before using this information and the product it supports, be sure to read the general information under Notices.
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 manual should not be interpreted as such.
You can order IBM publications online or through your local IBM representative.
v To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/order
v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at
www.ibm.com/planetwide
To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU
(426-4968).
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 1993-2002. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Part 1. Introduction to DB2 Connect 1
Installing DB2 Connect Enterprise Edition
(AIX) . . . . . . . . . . . . .
Chapter 1. About DB2 Connect . . . . . 3
DB2 Connect product offerings . . . . . . 3
Accessing host or iSeries DB2 data using DB2
Connect EE . . . . . . . . . . . . 5
Accessing DB2 data from remote clients. . . 12
Accessing DB2 data from the web using Java 12
Managing connections to databases using the
Configuration Assistant . . . . . . . . 15
Understanding the Administration Server . . 16
Administering instances and databases with
the DB2 administration tools . . . . . . 16
Developing applications using the DB2
Application Development Client . . . . . 18
Typical steps required to install and configure
DB2 Connect EE . . . . . . . . . . 19
Chapter 4. Installing DB2 Connect EE on
HP-UX. . . . . . . . . . . . . . 39
Installation requirements for DB2 Connect
Enterprise Edition (HP-UX) . . . . . . . 39
Memory requirements for DB2 Connect
Enterprise Edition (HP-UX) . . . . . . . 40
Disk requirements for DB2 Connect
Enterprise Edition (HP-UX) . . . . . . . 41
Recommended HP-UX kernel configuration
parameters . . . . . . . . . . . . 42
Mounting the CD-ROM on HP-UX . . . . 43
Installing DB2 Connect Enterprise Edition
(HP-UX) . . . . . . . . . . . . . 44
Part 2. Planning and Installation
21
Chapter 2. Installing DB2 Connect EE on
Windows . . . . . . . . . . . . . 23
Installation requirements for DB2 Connect
Enterprise Edition (Windows) . . . . . . 23
Memory requirements for DB2 Connect
Enterprise Edition (Windows) . . . . . . 24
Disk requirements for DB2 Connect
Enterprise Edition (Windows) . . . . . . 25
Installing DB2 Connect Enterprise Edition
(Windows) . . . . . . . . . . . . 26
Extending the directory schema (Windows
2000 and Windows .NET) . . . . . . . 28
Non-Administrator installation of DB2
Connect (Windows) . . . . . . . . . 29
Chapter 3. Installing DB2 Connect EE on
AIX . . . . . . . . . . . . . . . 31
Installation requirements for DB2 Connect
Enterprise Edition (AIX) . . . . . . . . 31
Memory requirements for DB2 Connect
Enterprise Edition (AIX) . . . . . . . . 32
Disk requirements for DB2 Connect
Enterprise Edition (AIX) . . . . . . . . 33
Mounting the CD-ROM on AIX . . . . . 34
© Copyright IBM Corp. 1993-2002
Chapter 5. Installing DB2 Connect EE on
Linux . . . . . . . . . . . . .
Installation requirements for DB2 Connect
Enterprise Edition (Linux) . . . . . .
Memory requirements for DB2 Connect
Enterprise Edition (Linux) . . . . . .
Disk requirements for DB2 Connect
Enterprise Edition (Linux) . . . . . .
Mounting the CD-ROM on Linux . . . .
Installing DB2 Connect Enterprise Edition
(Linux). . . . . . . . . . . . .
Preparing to install DB2 for Linux on S/390
. 35
. 47
. 47
. 48
. 49
. 50
. 50
52
Chapter 6. Installing DB2 Connect EE on
Solaris . . . . . . . . . . . . . 55
Installation requirements for DB2 Connect
Enterprise Edition (Solaris) . . . . . . . 55
Memory requirements for DB2 Connect
Enterprise Edition (Solaris) . . . . . . . 56
Disk requirements for DB2 Connect
Enterprise Edition (Solaris) . . . . . . . 57
Recommended Solaris kernel configuration
parameters . . . . . . . . . . . . 58
Mounting the CD-ROM on Solaris . . . . 59
Installing DB2 Connect Enterprise Edition
(Solaris) . . . . . . . . . . . . . 59
iii
Chapter 7. Migrating from previous
versions of DB2 Connect . . . .
.
.
. 63
Chapter 8. Applying the latest FixPak.
.
. 65
Chapter 9. DB2 Connect license activation
Installing your DB2 Connect license key using
the db2licm command . . . . . . . .
Installing your DB2 Connect license key using
the License Center . . . . . . . . . .
Setting the license type using the db2licm
command . . . . . . . . . . . . .
Setting the license type using the License
Center . . . . . . . . . . . . . .
67
67
68
69
69
Part 3. Preparing host and iSeries
databases for DB2 Connect
communications . . . . . . . . 71
Chapter 10. Preparing DB2 for OS/390 and
z/OS databases for DB2 Connect
communications . . . . . . . . . .
Preparing DB2 Universal Database for
OS/390 and z/OS for connections from DB2
Connect . . . . . . . . . . . . .
Configuring DB2 Universal Database for
OS/390 and z/OS . . . . . . . . . .
Configuring TCP/IP for DB2 Universal
Database for OS/390 and z/OS . . . . .
Configuring VTAM . . . . . . . . .
73
73
74
75
78
Chapter 11. Preparing DB2 UDB for iSeries
databases for DB2 Connect
communications . . . . . . . . . . 83
Preparing DB2 Universal Database for iSeries
for connections from DB2 Connect . . . . 83
Chapter 12. Preparing DB2 for VM & VSE
databases for DB2 Connect
communications . . . . . . . . . . 85
Preparing DB2 for VSE & VM for connections
from DB2 Connect . . . . . . . . . . 85
Part 4. Configuring access to host
and iSeries databases . . . . . . 87
Chapter 13. Using the Configuration
Assistant . . . . . . . . . .
iv
DB2 Connect EE Quick Beginnings
.
. 89
Configuring a connection to host or iSeries
database servers using the CA . . . . .
Configuration tasks . . . . . . . .
Configuring a database connection using
Discovery . . . . . . . . . . .
Configuring a database connection using
profile . . . . . . . . . . . .
Configuring a database connection using
the Configuration Assistant (CA) . . .
Testing a database connection . . . .
. 89
. 90
. 90
a
. 91
. 92
. 93
Chapter 14. Multisite update . . . . . .
Multisite Updates . . . . . . . . . .
Enabling Multisite Updates using the Control
Center . . . . . . . . . . . . . .
Testing Multisite Update using the Control
Center . . . . . . . . . . . . . .
Multisite update and sync point manager . .
95
95
96
97
98
Chapter 15. DB2 Connect Sysplex
support . . . . . . . . . . . . . 101
DB2 Connect Sysplex support. . . . . . 101
Considerations for S/390 and zSeries
SYSPLEX exploitation . . . . . . . . 101
Configuration requirements for Sysplex . . 103
DB2 Sysplex exploitation . . . . . . . 104
Part 5. Installing and configuring
clients . . . . . . . . . . . . 107
Chapter 16. DB2 client concepts .
DB2 clients . . . . . . . . .
DB2 Administration Client . . . .
DB2 Application Development Client
DB2 Run-Time Client . . . . .
. . . 109
. . . 109
. . . 109
. . . 110
. . . 110
Chapter 17. Installing clients . . . .
Client installation requirements . . . .
Installation requirements for DB2 clients
(Windows) . . . . . . . . . .
Installation requirements for DB2 clients
(AIX) . . . . . . . . . . . .
Installation requirements for DB2 clients
(HP-UX) . . . . . . . . . . .
Installation requirements for DB2 clients
(Linux) . . . . . . . . . . .
Installation requirements for DB2 clients
(Solaris) . . . . . . . . . . .
Disk requirements for DB2 clients . . .
. 113
. 113
. 113
. 114
. 115
. 116
. 117
. 119
Memory requirements for DB2 clients .
Installing a DB2 client on Windows
operating systems. . . . . . . .
Installing DB2 clients on UNIX . . .
.
. 120
.
.
. 120
. 122
Chapter 18. Configuring DB2 clients to
use DB2 Connect . . . . . . . . .
Configuration tasks . . . . . . . . .
Configuring a database connection using
Discovery . . . . . . . . . . .
Configuring a database connection using
a profile . . . . . . . . . . . .
Configuring a database connection using
the Configuration Assistant (CA). . . .
Testing a database connection . . . . .
Chapter 19. Using client and server
profiles . . . . . . . . . . . . .
Client profiles . . . . . . . . . . .
Creating client profiles using the export
function of the Configuration Assistant (CA) .
Configuring client profiles using the import
function of the Configuration Assistant (CA) .
Exporting and importing a profile . . . .
125
125
125
127
128
129
131
131
131
133
134
Part 6. Using DB2 Connect . . . 135
Chapter 20. Running your own
applications . . . . . . .
.
.
.
. 137
Chapter 21. Binding database utilities on
DB2 Connect . . . . . . . . . . . 139
Chapter 22. DB2 Connect and the CLI
environment . . . . . . . . . . . 141
Setting Up the CLI Environment . . . . . 141
Setting Up the UNIX ODBC Environment
142
Setting Up the Windows CLI Environment
144
Part 7. Appendixes . . . . . . . 147
Appendix A. Language Support . . . .
Changing the DB2 interface language
(Windows) . . . . . . . . . . . .
Changing the DB2 interface language
(UNIX) . . . . . . . . . . . . .
Supported DB2 interface languages, locales,
and code pages . . . . . . . . . .
149
149
150
150
Language identifiers (for running the
Setup wizard in another language) .
Bidirectional CCSID support . . .
Conversion of character data . . .
DB2
. .
. .
. .
Appendix B. Naming Rules . . . . .
Naming rules . . . . . . . . . .
DB2 object naming rules . . . . . .
Subconcepts. . . . . . . . . . .
Delimited identifiers and object names
User, userID and group naming rules .
Federated database object naming rules
Additional schema names information
Additional password information . .
Workstation naming rules . . . . .
Naming rules in an NLS environment .
Naming rules in a Unicode environment
. 155
. 156
. 158
.
.
.
.
.
.
.
.
Appendix C. DB2 Universal Database
technical information . . . . . . . .
Overview of DB2 Universal Database
technical information . . . . . . . .
Categories of DB2 technical information
Printing DB2 books from PDF files . . . .
Ordering printed DB2 books . . . . . .
Accessing online help . . . . . . . .
Finding topics by accessing the DB2
Information Center from a browser . . . .
Finding product information by accessing
the DB2 Information Center from the
administration tools . . . . . . . . .
Viewing technical documentation online
directly from the DB2 HTML Documentation
CD. . . . . . . . . . . . . . .
Updating the HTML documentation installed
on your machine . . . . . . . . . .
Copying files from the DB2 HTML
Documentation CD to a Web Server. . . .
Troubleshooting DB2 documentation search
with Netscape 4.x . . . . . . . . . .
Searching the DB2 documentation . . . .
Online DB2 troubleshooting information . .
Accessibility . . . . . . . . . . .
Keyboard Input and Navigation . . . .
Accessible Display . . . . . . . .
Alternative Alert Cues . . . . . . .
Compatibility with Assistive Technologies
Accessible Documentation . . . . . .
DB2 tutorials . . . . . . . . . . .
DB2 Information Center for topics . . . .
Contents
161
161
161
163
163
163
164
164
165
165
166
167
169
169
169
177
178
178
180
182
183
184
186
186
187
188
189
189
190
190
190
190
190
191
v
Appendix D. Notices . . . . . . . . 193
Trademarks . . . . . . . . . . . . 196
Index
vi
.
.
.
.
.
.
.
.
.
.
DB2 Connect EE Quick Beginnings
.
.
. 199
Contacting IBM . . . . . . . . . . 203
Product information . . . . . . . . . 203
Part 1. Introduction to DB2 Connect
The following section contains an overview of DB2 Connect, including
examples of different DB2 Connect environments. Topics discussed include:
v Available versions of DB2 Connect
v Suitability of each version for different business environments
v Administration and client tools that work with DB2 Connect
v How DB2 Connect relates to Java, web applications, and transaction
processing scenarios
Who Should Read This Section
v Managers exploring how to integrate DB2 Connect with present or planned
business operations
v Technical staff preparing to install DB2 Connect
© Copyright IBM Corp. 1993-2002
1
2
DB2 Connect EE Quick Beginnings
Chapter 1. About DB2 Connect
DB2 Connect provides connectivity to mainframe and midrange databases
from Windows, and UNIX-based platforms. You can connect to DB2 databases
on OS/390 and z/OS, iSeries, VSE, and VM. You can also connect to non-IBM
databases that comply with the Distributed Relational Database Architecture
(DRDA).
DB2 Connect product offerings
DB2 Connect has several connection solutions. DB2 Connect Personal Edition
provides direct connectivity to host and iSeries database series, while DB2
Connect Enterprise Edition provides indirect connectivity that allows clients to
access host and iSeries database servers through the DB2 Connect server. DB2
Connect Unlimited Edition provides a unique packaging solution that makes
product selection and licensing easier.
DB2 Connect Enterprise Edition
DB2 Connect Enterprise Edition is a connectivity server that
concentrates and manages connections from multiple desktop clients
and web applications to DB2 database servers running on host or
iSeries systems. IBM’s DB2 Universal Database (UDB) for iSeries, DB2
for OS/390 and z/OS, and DB2 for VSE & VM databases continue to
be the systems of choice for managing most critical data for the
world’s largest organizations. While these host and iSeries databases
manage the data, there is a great demand to integrate this data with
applications running on Windows and UNIX workstations.
DB2 Connect Enterprise Edition enables local and remote client
applications to create, update, control, and manage DB2 databases and
host systems using Structured Query Language (SQL), DB2 APIs
(Application Programming Interfaces), ODBC (Open Database
Connectivity), JDBC (Java Database Connectivity), SQLJ (Embedded
SQLJ for Java), or DB2 CLI (Call Level Interface). In addition, DB2
Connect supports Microsoft Windows data interfaces such as ActiveX
Data Objects (ADO), Remote Data Objects (RDO), and Object Linking
and Embedding (OLE) DB.
DB2 Connect Enterprise Edition is currently available for AIX, HP-UX,
Linux, Solaris, and Windows operating systems. These servers provide
support for applications running on UNIX (AIX, HP-UX, Linux, and
Solaris operating environment), and Windows workstations.
© Copyright IBM Corp. 1993-2002
3
DB2 Connect Enterprise Edition is often installed on an intermediate
server to connect DB2 clients to a host or iSeries database. It can also
be used on machines where multiple local users want to access the
host or iSeries servers directly.
For example, DB2 Connect Enterprise Edition may be installed on a
large machine with many local users. It may also be installed on a
web server, a machine that is running a Transaction Processor (TP)
monitor, or other 3-tier application servers with multiple local SQL
application processes and threads. In these cases, you can install DB2
Connect Enterprise Edition on the same machine for simplicity, or on
a separate machine to off-load CPU cycles.
DB2 Connect Enterprise Edition is most appropriate for environments
where:
v Host and iSeries database servers do not support native TCP/IP
connectivity and direct connectivity from desktop workstations via
SNA is not desirable.
v Web servers run web-based applications.
v Web servers run web-based application using data-aware Java
applications.
v A middle-tier application server is used.
v TP monitors, such as CICS, Encina, Microsoft Transaction Server
(MTS), Tuxedo, Component Broker, and MQSeries, are used.
DB2 Connect Personal Edition
DB2 Connect Personal Edition provides access from a single
workstation to DB2 databases residing on servers such as OS/390,
z/OS, OS/400, VM and VSE, as well as to DB2 Universal Database
servers on UNIX and Windows operating systems. DB2 Connect
Personal Edition provides the same rich set of APIs as DB2 Connect
Enterprise Edition.
This product is currently available for Linux and Windows operating
systems.
DB2 Connect Personal Edition is used to connect a single Windows
operating system, or Linux workstation, to a host or iSeries database.
DB2 Connect Personal Edition is best suited for environments where
native TCP/IP support is provided by the database servers, and the
application being deployed is a traditional 2-tier client-server
application.
For example, DB2 Connect Personal Edition is a good choice for
enabling traditional 2-tier VisualBasic and Microsoft Access
applications. Applications that require a mid-tier application server
need to use DB2 Connect Enterprise Edition.
4
DB2 Connect EE Quick Beginnings
DB2 Connect Unlimited Edition
DB2 Connect Unlimited Edition is a unique package offering that
allows complete flexibility of DB2 Connect deployment and simplifies
product selection and licensing. This product contains both DB2
Connect Personal Edition and DB2 Connect Enterprise Edition with
license terms and conditions that allow the unlimited deployment of
any DB2 Connect product. License charges are based on the size of
the S/390 or zSeries server that DB2 Connect users will be working
with.
This package offering is only available for OS/390 and z/OS systems,
and licensing is only valid for DB2 for OS/390 and z/OS data
sources.
Related concepts:
v “DB2 Connect” in the DB2 Connect User’s Guide
v “DB2 Connect and SQL statements” in the DB2 Connect User’s Guide
v “Thin clients” in the Installation and Configuration Supplement
Related tasks:
v “Response file installation of DB2 on UNIX” in the Installation and
Configuration Supplement
v “Response file installation of DB2 on Windows” in the Installation and
Configuration Supplement
Related reference:
v “Host databases” in the DB2 Connect User’s Guide
v “DB2 Connect administration utilities” in the DB2 Connect User’s Guide
Accessing host or iSeries DB2 data using DB2 Connect EE
A DB2® Connect server enables DB2 clients on a LAN access to data that is
stored on host or iSeries™ systems. DB2 Universal Database™ Enterprise
Server Edition includes the DB2 Connect™ Server Support component. All
references to DB2 Connect Enterprise Edition also apply to the DB2 Connect
Server Support component.
In organizations with large amounts of data, DB2 UDB for iSeries, DB2 UDB
for OS/390® and z/OS, or DB2 for VSE & VM are commonly used to manage
that data. Applications that run on any of the supported platforms can work
with this data transparently, as if a local database server managed it. DB2
Connect Enterprise Edition is required for supporting applications which
access host or iSeries data and exploit transaction monitors (for example,
Chapter 1. About DB2 Connect
5
IBM® TxSeries CICS® and Encina® Monitor, Microsoft® Transaction Server,
BEA Tuxedo) as well as applications that are implemented as Java™ applets.
In addition, you can use a wide range of off-the-shelf or custom-developed
database applications with DB2 Connect and its associated tools. For example,
you can use DB2 Connect products with:
v Spreadsheets, such as Lotus® 1-2-3® and Microsoft Excel, to analyze real-time
data without having the cost and complexity of data extract and import
procedures.
v Decision support tools, such as BusinessObjects, Brio and Impromptu, and
Crystal Reports, to provide real-time information.
v Database products, such as Lotus Approach® and Microsoft Access.
v Development tools, such as PowerSoft PowerBuilder, Microsoft Visual Basic,
and Borland Delphi, to create client/server solutions.
DB2 Connect Enterprise Edition is most appropriate for environments where:
v Host and iSeries database servers do not support native TCP/IP
connectivity, and direct connectivity from desktop workstations via SNA is
not desirable (see Figure 1 on page 8).
v Application is implemented using data-aware Java applets (see Figure 5 on
page 14).
v Web servers are used to implement web-based applications (see Figure 4 on
page 11 and Figure 5 on page 14).
v Middle-tier application server is employed.
v Transaction monitors such as IBM TxSeries CICS and Encina Monitor, IBM
Component Broker, IBM MQSeries, Microsoft Transaction Server (MTS), and
BEA Tuxedo are used. (See Figure 2 on page 9.)
DB2 Connect provides transparent access to host or iSeries data through a
standard architecture for managing distributed data. This standard is known
as Distributed Relational Database Architecture (DRDA). DRDA® allows your
applications to establish a fast connection to host and iSeries databases
without expensive host or iSeries components or proprietary gateways.
Although DB2 Connect is often installed on an intermediate server machine to
connect DB2 clients to a host or iSeries database, it is also installed on
machines where multiple local users want to access the host or iSeries servers
directly. For example, DB2 Connect may be installed on a large machine with
many local users.
DB2 Connect may also be installed on a Web server, Transaction Processor
(TP) monitor, or other 3-tier application server machines with multiple local
6
DB2 Connect EE Quick Beginnings
SQL application processes and threads. In these cases, you can choose to
install DB2 Connect on the same machine for simplicity, or on a separate
machine to off-load CPU cycles.
A DB2 Connect server enables multiple clients to connect to host or iSeries
data and can significantly reduce the effort that is required to establish and
maintain access to enterprise data. Figure 1 on page 8 illustrates IBM’s
solution for environments where a DB2 client makes an indirect connection to
a host or iSeries database server through DB2 Connect Enterprise Edition.
In the example, you could replace the DB2 Connect server with a DB2 server
that has the DB2 Connect Server Support component installed.
Chapter 1. About DB2 Connect
7
DB2
for VSE
DB2
for VM
DB2
for OS/390
and z/OS
DB2 UDB
for iSeries
S/390, S/370, zSeries
iSeries
APPC, TCP/IP***, MPTN
Coax*, Ethernet, Asynch Twinax**,
SDLC, Token-ring, X.25, ESCON
SNA Communications Support****
DB2 Connect Enterprise Edition
APPC, Named Pipes, NetBIOS,
TCP/IP
DB2
Run-Time Client
and applications
DB2
Administration Client
and applications
Not all protocols are supported for all platforms.
Legend
* For Host connections only
** For iSeries
*** TCP/IP connectivity requires DB2 for OS/390 V5R1,
DB2 for AS/400 V4R2, or DB2 for VM V6.1
**** SNA Comm Support is specific for each operating system and is
required only in cases where native TCP/IP connectivity is not available.
Figure 1. DB2 Connect Enterprise Edition
8
DB2 Connect EE Quick Beginnings
DB2
for VSE
DB2
for VM
DB2
for OS/390
and z/OS
DB2 for
iSeries
iSeries
S/390, S/370, zSeries
APPC, TCP/IP***, MPTN
Coax*, Ethernet, Asynch Twinax**,
SDLC, Token-ring, X.25, ESCON
Application n
Application
Business Logic
Application 2
TP Monitor
(eg. CICS, ENCINA, MTS)
Application 1
DB2 Connect Enterprise Edition
Legend
* For Host connections only
TP Monitor Client
** For iSeries
*** TCP/IP connectivity requires DB2 for OS/390 V5R1,
DB2 for AS/400 V4R2, or DB2 for VM V6.1
Not all protocols are supported for all platforms.
Figure 2. Transaction monitors working with DB2 Connect.
Chapter 1. About DB2 Connect
9
DB2
for VSE
DB2
for VM
DB2
for OS/390
and z/OS
DB2 for
iSeries
iSeries
S/390, S/370, zSeries
APPC, TCP/IP***, MPTN
Coax*, Ethernet, Asynch Twinax**,
SDLC, Token-ring, X.25, ESCON
Java Servlets, JSP,
Enterprise Java Beans
Application n
WebSphere
Application 2
Web
Server
Application 1
DB2 Connect Enterprise Edition
Legend
* For Host connections only
Web Browser
** For iSeries
*** TCP/IP connectivity requires DB2 for OS/390 V5R1
or later, DB2 for AS/400 V4R2 or later, or DB2 for
VM V6.1
Not all protocols are supported for all platforms.
Figure 3. WebSphere and Java server functionality in DB2 Connect
10
DB2 Connect EE Quick Beginnings
DB2
for VSE
DB2
for VM
DB2
for OS/390
and z/OS
DB2 for
iSeries
iSeries
S/390, S/370, zSeries
APPC, TCP/IP***, MPTN
Coax*, Ethernet, Asynch Twinax**,
SDLC, Token-ring, X.25, ESCON
ASPs,
COM Objects
Application n
ADO
Application 2
IIS &
MTS
Application 1
DB2 Connect Enterprise Edition
Legend
* For Host connections only
Web Browser
** For iSeries
*** TCP/IP connectivity requires DB2 for OS/390 V5R1,
DB2 for AS/400 V4R2, or DB2 for VM V6.1
Not all protocols are supported for all platforms.
Figure 4. DB2 Connect working with Microsoft Internet Information Server (IIS)
Related concepts:
v “Typical steps required to install and configure DB2 Connect EE” on page
19
Chapter 1. About DB2 Connect
11
Accessing DB2 data from remote clients
DB2® clients provide a run-time environment that enables client applications
to access one or more remote databases. With a DB2 Administration Client,
you can remotely administer DB2 or DB2 Connect™ servers. All applications
must access a database through a DB2 client. A Java™ applet can access a
remote database through a Java-enabled browser.
DB2 clients are supported on:
v UNIX® (AIX, HP-UX, Linux, and the Solaris Operating Environment)
v Windows® 98, Windows ME Windows NT, Windows 2000, Windows XP
(32-bit and 64-bit), and Windows .NET (32-bit and 64-bit) .
Related concepts:
v
v
v
v
“DB2 clients” on page 109
“DB2 Run-Time Client” on page 110
“DB2 Administration Client” on page 109
“DB2 Application Development Client” on page 110
Accessing DB2 data from the web using Java
Java™ Database Connectivity (JDBC) and Embedded SQL for Java (SQLj) are
provided with DB2® to allow you to create applications that access data in
DB2 databases from the Web.
Programming languages containing embedded SQL are called host languages.
Java differs from the traditional host languages C, COBOL, and FORTRAN, in
ways that significantly affect how it embeds SQL:
v SQLj and JDBC are open standards, enabling you to easily port SQLj or
JDBC applications from other standards-compliant database systems to DB2
Universal Database.
v All Java types representing composite data, and data of varying sizes, have
a distinguished value, null, which can be used to represent the SQL NULL
state, giving Java programs an alternative to NULL indicators that are a
fixture of other host languages.
v Java is designed to support programs that, by nature, are heterogeneously
portable (also called ″super portable″ or simply ″downloadable″). Along
with Java’s type system of classes and interfaces, this feature enables
component software. In particular, an SQLj translator written in Java can
call components that are specialized by database vendors in order to
leverage existing database functions such as authorization, schema
checking, type checking, transactional, and recovery capabilities, and to
generate code optimized for specific databases.
12
DB2 Connect EE Quick Beginnings
v Java is designed for binary portability in heterogeneous networks, which
promises to enable binary portability for database applications that use
static SQL.
v You can run JDBC applets inside a web page on any system with a
Java-enabled browser, regardless of the platform of your client. Your client
system requires no additional software beyond this browser. The client and
the server share the processing of JDBC and SQLj applets and applications.
The DB2 JDBC Applet server and the DB2 Connect™ server must reside on
the same machine as the Web server. The DB2 JDBC Applet server calls the
DB2 client to connect to local and remote databases. When the applet requests
a connection to a DB2 database, the JDBC client opens a TCP/IP connection to
the DB2 JDBC Applet on the machine where the Web server is running.
Chapter 1. About DB2 Connect
13
DB2
for VSE
DB2
for VM
DB2
for OS/390
and z/OS
DB2 for
iSeries
iSeries
S/390, S/370, zSeries
APPC, TCP/IP***, MPTN
Coax*, Ethernet, Asynch Twinax**,
SDLC, Token-ring, X.25, ESCON
DB2 JDBC
Applet Server
Application n
JDBC driver
Application 2
Web
Server
Application 1
DB2 Connect Enterprise Edition
Legend
* For Host connections only
** For iSeries
*** TCP/IP connectivity requires DB2 for OS/390 V5R1,
DB2 for AS/400 V4R2, or DB2 for VM V6.1
Java-enabled
Web Browser
Not all protocols are supported for all platforms.
Figure 5. JDBC and DB2 Connect
JDBC and SQLj applications can be run from any system that has a DB2 client
installed; a Web browser and a Web server are not required.
For more information on Java enablement, see the
http://www.ibm.com/software/data/db2/java/ web page.
For more information on the JDBC API, see the http://java.sun.com/ web
page.
14
DB2 Connect EE Quick Beginnings
Managing connections to databases using the Configuration Assistant
The Configuration Assistant (CA) helps you manage your database
connections to remote servers. This is the preferred method to set up any
client to server communications.
You can also use the command line processor to set up DB2® clients on any
platform.
With the CA, you can:
v Catalog databases so that they can be used by applications. Three methods
are available:
– Use a profile provided by a database administrator to automatically
define your connections. Client access is automatically set up for that
database.
– Search the network for available databases and select one. Client access
is automatically set up for for those databases defined in the profile. DB2
Connect™ Personal Edition cannot search for host or iSeries™ databases
except through a DB2 Connect Enterprise Edition server that has host or
iSeries databases defined.
– Manually configure a connection to a database by entering the required
connection parameters.
v Remove cataloged databases, or change the properties of a cataloged
database.
v Export and import client profiles that contain database and configuration
information for a client.
v Test connections to local or remote databases identified on your system.
v Bind applications to a database by selecting utilities or bind files from a list.
v Add, change, remove CLI/ODBC data sources, and configure CLI/ODBC
configuration settings.
v Tune the client configuration parameters on your system. Parameters are
logically grouped and suggested settings are provided on the interface as
parameters are selected.
v Update the database server password.
Related tasks:
v “Configuring a client to server connection using the Configuration Assistant
(CA)” in the Quick Beginnings for DB2 Servers
v Chapter 21, “Binding database utilities on DB2 Connect” on page 139
v “Configuring a connection to host or iSeries database servers using the CA”
on page 89
Chapter 1. About DB2 Connect
15
Understanding the Administration Server
The DB2 Administration Server (DAS) responds to requests from the DB2®
Administration Tools and the Configuration Assistant (CA). The DB2
Administration Tools, for example, allow you to start, stop, and set database
manager configuration parameters for servers. The Administration Server is
used by the CA to help users catalog databases on a client.
An Administration Server must reside on each server that you want to
administer and detect. The Administration Server is automatically created and
started for you; its default name on Windows is DB2DAS00 and on UNIX is
db2as. The setup program creates the Administration Server on the
instance-owning machine and automatically starts it at boot time. By default
the DAS instance is DB2AS, which is the default user ID that is created using
the DB2 Setup wizard.
Related concepts:
v “DB2 Administration Server” in the Administration Guide: Implementation
Related tasks:
v “Create a DB2 Administration Server” in the Administration Guide:
Implementation
Administering instances and databases with the DB2 administration tools
You can administer local or remote servers using the DB2® administration
tools. Use the Control Center to perform administration tasks such as
configuring DB2 instances and databases, backing up and recovering data,
scheduling jobs, and managing media, all from a graphical interface.
The Control Center has additional support for DB2 UDB for OS/390® and
z/OS. If you want to access DB2 for OS/390 and z/OS™ functions from the
Control Center:
1. Verify the following information with your systems administrator:
a. You have a DB2 UDB for OS/390 license (Version 6) or DB2 UDB for
OS/390 and z/OS (Version 7 or later).
b. You are using one of the following: DB2 Enterprise Server Edition, DB2
Connect Personal Edition, or DB2 Connect™ Enterprise Edition.
2. Apply the FMIDs for the DB2 Management Clients Package (a feature of
DB2 for OS/390 version 6 and DB2 for OS/390 and z/OS version 7 or
later) and DB2 Administration Server (DAS) for OS/390 and z/OS (only
available for DB2 for OS/390 and z/OS version 7 or later). If you are
managing a DB2 for OS/390 Version 6 server, some Control Center
16
DB2 Connect EE Quick Beginnings
functions , including System Console Interface, Cloning, and JCL Building
and Creation, are only available if the DB2 Administration Server is
installed in the same system where the DB2 for OS/390 Version 6
subsystem resides. DAS is an optional feature that is shipped with DB2 for
OS/390 and z/OS Version 7 server, but can also be used with DB2 UDB
for OS/390 Version 6 servers. Read the DB2 for OS/390 and z/OS, DB2
Management Clients Package, and DB2 Administration Server for OS/390
and z/OS program directories. The program directory identifies and
describes the contents of FMIDs for each tape or cartridge. The program
directory also provides the installation requirements and instructions.
3. Apply any additional service to DB2 UDB for OS/390 Version 6 or DB2
UDB for OS/390 and z/OS Version 7 or later as described in the program
directories.
4. IBM DB2 Universal Database Control Center Version 8 provides support to
help you manage DB2 databases on multiple platforms. When managing
DB2 UDB for OS/390 and z/OS subsystems, you need to install a set of
stored procedures, user defined functions, and batch programs for each
DB2 subsystem.
If you have DB2 UDB for OS/390 Version 6 installed, you need to install
the 390 enablement feature of DB2 UDB for OS/390 Version 6 (JDB661D).
If you have DB2 UDB for OS/390 and z/OS Version 7 installed, you need
to install the 390 enablement feature of DB2 UDB for OS/390 and z/OS
Version 7 (JDB771D). If you want to fully exploit all the DB2 UDB Control
Center Version 8 functions for OS/390 and z/OS, including Cloning and
JCL building and creation, you need to install the DB2 Administration
Server (DAS) for OS/390 and z/OS Version 8 (HDA8810 or HAH8810)
which ships as a feature of DB2 for OS/390 and z/OS Version 7.The DB2
Administration Server only needs to be installed once per system.
If you are also managing a DB2 UDB for OS/390 Version 6 on this system,
then you can use the DB2 UDB Control Center Version 8 functions that are
supported by DB2 UDB for OS/390 Version 6. For information on how to
install these products, please refer to the product’s program directory:
v JDB661D : Program Directory for IBM DB2 UDB for OS/390 DB2
Management Tools package (GI10-8193-02)
v JDB771D : Program Directory for IBM DB2 UDB Server for OS/390 and
z/OS DB2 Management Clients package (GI10-8218-00)
v HDA8810 (or HAH8810)
5. Ensure that you enabled the stored procedures address space.
6. Ensure that the DB2 Administration Server is started.
Managing communications on the server:
The Control Center allows you to view, update, and reset server protocol
settings. These functions are accessed by clicking with the right mouse button
Chapter 1. About DB2 Connect
17
on an instance and selecting the Setup communications option from the
pop-up menu. By default, the setup program automatically detects and
configures most communication protocols that it detects on your system.
The Control Center allows you to maintain or edit server protocol settings in
the database manager configuration file.
v Configure database manager parameters by clicking with the right mouse
button on an instance and selecting the Configure option from the pop-up
menu.
v Export database information in a profile that can be used to configure
clients by clicking with the right mouse button on a system and selecting
the Export Server Profile option from the pop-up menu.
Viewing SQL access plans using Visual Explain:
Note: You cannot use Visual Explain to generate access plans on host or
iSeries™ databases.
Visual Explain helps database administrators and application developers to:
v View the access plan chosen by the database manager’s optimizer for a
given SQL statement.
v Tune SQL statements for better performance.
v Design application programs and databases.
v View all the details of an access plan, including the statistics in the system
catalogs.
v Decide whether or not to add an index to a table.
v Identify the source of problems by analyzing the access plan or
performance of SQL statements.
v Use the portable snapshot function to view snapshots from any remote DB2
server.
v Display access plans for queries on all supported DB2 configurations.
Developing applications using the DB2 Application Development Client
The DB2 Application Development Client is a collection of tools that are
designed to meet the needs of database application developers. It includes
libraries, header files, documented APIs, and sample programs to build
character-based, multimedia, or object-oriented applications.
A platform-specific version of the DB2 Application Development Client is
available on each server CD-ROM. In addition, the Developer Edition package
contains the Application Development Clients for multiple supported
operating systems. The Personal Developer’s Edition package contains the
18
DB2 Connect EE Quick Beginnings
Application Development CD-ROMs for Windows and Linux. The Universal
Developer’s Edition package contains the Application Development CD-ROMs
for all supported operating systems.
Through a DB2 client, these applications can access all servers and, by using
the DB2 Connect product (or the DB2 Connect functionality supplied with
DB2 Enterprise Server Edition), they can also access DB2 UDB for iSeries, DB2
for OS/390 and z/OS, and DB2 for VSE & VM database servers.
The DB2 Application Development Client allows you to develop applications
that use the following interfaces:
v Embedded SQL
v Call Level Interface (CLI) development environment (which is compatible
with ODBC from Microsoft)
v Java Database Connectivity (JDBC)
v Embedded SQL for Java (SQLj)
v DB2 Application Programming Interfaces (APIs) that use administrative
functions to manage a DB2 database.
Related concepts:
v “DB2 Developer's Edition Products” in the Application Development Guide:
Programming Client Applications
Related reference:
v “DB2 Application Development Client” in the Application Development Guide:
Building and Running Applications
Typical steps required to install and configure DB2 Connect EE
Setting up DB2® Connect is a multi-step process. DB2 Connect™ Enterprise
Edition is often installed with hundreds or thousands of clients connecting to
host or iSeries™ database servers. For this reason, we recommend a test
installation, outlined below. After the test configuration has proven stable, you
can use it as the template for an unattended installation of DB2 Connect and
your clients across your organization.
The typical steps to installing and configuring DB2 Connect Enterprise Edition
are as follows:
1. Determine how you want to use DB2 Connect in your network.
2. Verify that you have the correct hardware and software prerequisites on
both your workstation and the host database server.
3. Verify that your host or iSeries database server is configured to accept
connections from DB2 Connect servers.
Chapter 1. About DB2 Connect
19
4. Install your DB2 Connect software. You will use this workstation to
configure and verify your host and iSeries connections.
5. After installation, establish the connection between DB2 Connect and
your host or iSeries database system. DB2 Connect can locate and
configure all TCP/IP and most SNA connections for you. You can use the
Configuration Assistant (CA) to configure host or iSeries databases.
6. Bind the programs and utilities provided with DB2 Connect to your host
or iSeries database.
7. Test the connection.
8. (Optional) Enable the Multisite Update feature.
9. If you are planning to use WebSphere, transaction monitors, or your own
application server software, install these products or applications. For
information on installing WebSphere® consult the documentation
provided with these products as part of the DB2 Connect Enterprise
Edition product package. For other products consult the installation
documentation provided with the product.
10. Install and configure a DB2 client. Use this workstation to test
connectivity from the DB2 client to host and iSeries database servers, as
well as to test applications that use this connectivity.
11. Use the Configuration Assistant to connect the client to the host or iSeries
system through DB2 Connect.
12. Install DB2 clients on all end-user workstations that will use applications
that connect to host and iSeries database servers.
13. You are now ready to use DB2 Connect with all your applications.
Workstations that will be used for application development should have
the DB2 Application Development Client installed.
14. If you want to use your workstation to administer DB2 UDB for OS/390®
and z/OS™ or DB2 Universal Database for UNIX, Windows® NT,
Windows 2000, Windows XP and Windows .NET servers, install the DB2
Administration Client.
Related concepts:
v “DB2 clients” on page 109
Related tasks:
v “Enabling Multisite Updates using the Control Center” on page 96
v Chapter 21, “Binding database utilities on DB2 Connect” on page 139
v “Configuring a connection to host or iSeries database servers using the CA”
on page 89
20
DB2 Connect EE Quick Beginnings
Part 2. Planning and Installation
Use this section to plan every step of your installation. Prerequisite software
and patch levels, operating system, and communications protocol
requirements are all provided in simple tables. You can verify that your
system meets the requirements for your planned DB2 Connect
implementation, then move on to the installation procedure.
If you are planning to migrate from a previous version of DB2 Connect, see
Chapter 7, “Migrating from previous versions of DB2 Connect” on page 63.
To manually install your DB2 Connect product, see the Installation and
Configuration Supplement for instructions on manually installing DB2 products.
Who Should Read This Section
v Technical personnel installing and configuring a DB2 Connect system
© Copyright IBM Corp. 1993-2002
21
22
DB2 Connect EE Quick Beginnings
Chapter 2. Installing DB2 Connect EE on Windows
Installation requirements for DB2 Connect Enterprise Edition (Windows)
To install DB2 Connect Enterprise Edition, the following requirements must be
met:
Hardware requirements
For DB2 products running on Intel and AMD systems, a Pentium or
Athlon CPU is required.
Operating system requirements
One of:
v Windows NT Version 4 with Service Pack 6a or higher
v Windows 2000
v Windows .NET (32-bit and 64-bit)
Software requirements
Java Runtime Environment (JRE) Version 1.3.1 is required to run
DB2’s Java-based tools, such as the Control Center, and is installed by
the DB2 Setup wizard when needed.
Communication requirements
v You can use APPC, TCP/IP, and MPTN (APPC over TCP/IP)
v For SNA (APPC) connectivity, one of the following communications
products is required:
Note: You should consider switching to TCP/IP as SNA may no
longer be supported in future releases of DB2 Connect. SNA
requires significant configuration knowledge and the
configuration process itself can prove to be error prone.
TCP/IP is simple to configure, has lower maintenance costs,
and provides superior performance.
– Windows NT:
- IBM Communications Server Version 6.1.1 or later.
- IBM Personal Communications Version 5 CSD3 or later.
– Windows 2000:
- IBM Communications Server Version 6.1.1 or later.
- IBM Personal Communications Version 5 CSD3 or later.
– Microsoft SNA Server Version 3 Service Pack 3 or later.
© Copyright IBM Corp. 1993-2002
23
Windows .NET 64-bit does not support SNA.
Notes:
1. If you plan to use the Tivoli Storage Manager facilities to backup
and restore your databases, you require the Tivoli Storage
Manager Client Version 3 or later.
2. If you plan to use the Simple Network Management Protocol
(SNMP) subagent, you require DPI 2.0 provided by IBM
SystemView Agent. Windows .NET 64-bit does not support SNMP.
Related concepts:
v “Non-Administrator installation of DB2 Connect (Windows)” on page 29
Related tasks:
v “Extending the directory schema (Windows 2000 and Windows .NET)” on
page 28
v “Installing DB2 Connect Enterprise Edition (Windows)” on page 26
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (Windows)” on
page 24
v “Disk requirements for DB2 Connect Enterprise Edition (Windows)” on
page 25
Memory requirements for DB2 Connect Enterprise Edition (Windows)
The amount of memory required to run DB2 Connect Enterprise Edition
depends on the components you install. The following table provides
recommended memory requirements for DB2 Connect Enterprise Edition
installed with and without graphical tools such as the Control Center and
Configuration Assistant.
Table 1. DB2 Connect Enterprise Edition memory requirements
Type of installation
Recommended memory (RAM)
DB2 Connect Enterprise Edition without
graphical tools
64 MB
DB2 Connect Enterprise Edition with
graphical tools
128 MB
When determining memory requirements, be aware of the following:
24
DB2 Connect EE Quick Beginnings
v These memory requirements are for a base of 5 concurrent client
connections. You will need an additional 16 MB of RAM per 5 client
connections.
v The memory requirements documented above do not account for non-DB2
software that may be running on your system.
v Specific performance requirements may determine the affect of memory
needed.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (Windows)” on page 26
Related reference:
v “Installation requirements for DB2 Connect Enterprise Edition (Windows)”
on page 23
v “Disk requirements for DB2 Connect Enterprise Edition (Windows)” on
page 25
Disk requirements for DB2 Connect Enterprise Edition (Windows)
The disk requirements for DB2 Connect Enterprise Edition depend on the type
of installation and the components you install. The DB2 Setup wizard
provides typical, compact, and custom installation types. The following table
lists the approximate disk space requirement for each installation type.
Table 2. DB2 Connect Enterprise Edition disk requirements
Installation type
Required disk space
Typical
150 MB
Compact
80 MB
Custom
80 MB to 200 MB
Typical installation
DB2 Connect Enterprise Edition is installed with most features and
functionality, using a typical configuration. This installation includes
graphical tools such as the Control Center and Configuration
Assistant.
Compact installation
Only the basic DB2 Connect Enterprise Edition features and functions
are installed. This installation does not include graphical tools.
Custom installation
A custom installation allows you to select the features you want to
install.
Chapter 2. Installing DB2 Connect EE on Windows
25
The DB2 Setup wizard will provide a disk space estimate for the installation
options you select.
Remember to include a disk space allowance for required software,
communication products, and documentation. In DB2 Version 8, HTML and
PDF documentation is provided on separate CD-ROMs.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (Windows)” on page 26
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (Windows)” on
page 24
v “Installation requirements for DB2 Connect Enterprise Edition (Windows)”
on page 23
Installing DB2 Connect Enterprise Edition (Windows)
This task describes how to install DB2 Connect Enterprise Edition on
Windows operating systems.
Prerequisites:
Before you launch the DB2 Setup wizard:
v Ensure that your system meets:
– Memory requirements
– Hardware, distribution and software requirements
– Disk requirements
v If you are planning to use LDAP on Windows 2000 or Windows .NET
(32-bit and 64-bit), you must extend the directory schema.
v It is recommended that you use an Administrator account to perform the
installation. The Administrator account must belong to the local
administrator’s group on the Windows computer where you are installing
your DB2 product and should have the following advanced user rights:
–
–
–
–
Act as part of the operating system
Create token object
Increase quotas
Replace a process level token
You can perform the installation without advanced user rights, but the
setup program may be unable to validate accounts.
26
DB2 Connect EE Quick Beginnings
v If you want to install DB2 Connect with a non-Administrator account, see
the non-Administrator installation of DB2 Connect.
Procedure:
To install DB2 Connect Enterprise Edition:
1. Log on to the system as a user with administrator authority.
2. Close all programs so the installation program can update files as
required.
3. Insert the CD-ROM into the drive. The auto-run feature automatically
starts the DB2 Setup wizard. The DB2 Setup wizard will determine the
system language and launch the setup program for that language. If you
want to run the setup program in a different language, or the setup
program failed to auto-start, you can run the DB2 Setup wizard manually.
4. The DB2 Launchpad opens.
From this window, you can view the installation prerequisites and the
release notes, or you can proceed directly to the installation.
5. Once you have initiated the installation, proceed by following the setup
program’s prompts. Online help is available to guide you through the
remaining steps. To invoke the online help, click Help or press F1. You can
click Cancel at any time to exit the installation.
For information on errors encountered during installation, see the db2.log file.
The db2.log file stores general information and error messages resulting from
Chapter 2. Installing DB2 Connect EE on Windows
27
the install and uninstall activities. By default, the db2.log file is located in the
x:\db2log directory, where x: represents the drive on which your operating
system is installed.
Manually launching the DB2 Setup wizard:
To invoke the DB2 Setup wizard manually:
1. Click Start and select the Run option.
2. In the Open field, enter the following command:
x:\setup /i language
where:
v x: represents your CD-ROM drive
v language represents the territory code for your language (for example,
EN for English).
3. Click OK.
Related tasks:
v “Extending the directory schema (Windows 2000 and Windows .NET)” on
page 28
v Chapter 8, “Applying the latest FixPak” on page 65
v “Installing your DB2 Connect license key using the License Center” on page
68
v “Setting the license type using the License Center” on page 69
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (Windows)” on
page 24
v “Installation requirements for DB2 Connect Enterprise Edition (Windows)”
on page 23
v “Disk requirements for DB2 Connect Enterprise Edition (Windows)” on
page 25
Extending the directory schema (Windows 2000 and Windows .NET)
Extending the directory schema is part of the larger task of Installing DB2
(Windows).
If you plan to use LDAP with Windows 2000 or Windows .NET, you must
extend the directory schema to contain DB2 object classes and attribute
definitions. You must do this once before you install DB2.
28
DB2 Connect EE Quick Beginnings
Prerequisites:
Your Windows user account must have Schema Administration authority.
Procedure:
To extend the directory schema, logon to a domain controller and execute the
db2schex.exe program from the installation CD with Schema Administration
authority. You can execute this program with Schema Administration
authority, without logging off and logging on again, as follows:
runas /user:MyDomain\Administrator x:\db2\common\db2schex.exe
where x: represents the CD-ROM letter. When db2schex.exe completes, you
can continue with the installation.
Your next step is Starting the DB2 Setup wizard (Windows).
Related reference:
v “Installation requirements for DB2 servers (Windows)” in the Quick
Beginnings for DB2 Servers
Non-Administrator installation of DB2 Connect (Windows)
For a non-Administrator’s installation, which is only available on Windows®
NT, Windows 2000 Professional, and Windows XP, the account you are logged
on as must belong to a group with more authority than the Guests group. For
example, you can log on as a user account that belongs to the Users group or
the Power Users group.
Some information about DB2® Connect that must appear in the registry must
be entered in the HKEY_CURRENT_USER folder in the registry. Although
many items will be stored under the HKEY_LOCAL_MACHINE folder in the
registry for non-Administrator installations of DB2 Connect, the environment
settings must be changed in HKEY_CURRENT_USER.
System shortcuts must be changed to user shortcuts for the non-Administrator
install. Moreover, since services are required to install any of the DB2
Connect™ products, but cannot be created without administrative authority,
services that would be automatically started are run as processes when a
non-administrator installs.
The following are installation situations you might encounter in an
environment where both administrator and non-administrator installations
exist:
Chapter 2. Installing DB2 Connect EE on Windows
29
v A non-Administrator has installed DB2 Connect, and then an Administrator
attempts to install DB2 Connect on the same machine. The Administrator
will get a message that the product is already installed. The Administrator
does have the authority to uninstall and reinstall the product to get around
this issue. These products cannot co-exist on Windows platforms because
there is only a single registry and you can not have DB2 installed multiple
times.
v A non-administrator has installed DB2 Connect, and then a second
non-Administrator attempts to install DB2 Connect on the same machine. In
this scenario, the installation will fail, and return an error message that the
user must be an Administrator to install the product.
v An Administrator has installed DB2 Connect, and then a non-Administrator
attempts to install DB2 Connect on the same machine. In this scenario, the
install will fail, and return an error message that the user must be an
Administrator to install the product. An Administrator always has the
authority to uninstall or reinstall.
Related tasks:
v “Installing DB2 Connect Personal Edition (Windows)” in the Quick
Beginnings for DB2 Connect Personal Edition
v “Installing DB2 Connect Enterprise Edition (Windows)” on page 26
30
DB2 Connect EE Quick Beginnings
Chapter 3. Installing DB2 Connect EE on AIX
Installation requirements for DB2 Connect Enterprise Edition (AIX)
To install DB2 Connect Enterprise Edition, the following requirements must be
met:
Hardware requirements
v IBM RISC/6000
v eServer pSeries
Operating system requirements
DB2 Connect Enterprise Edition is available on:
v AIX 4.3.3.0 Maintenance level AIX 4330-09 (32-bit)
v AIX 5L Maintenance level AIX 5100-01 (32-bit)
v AIX 5L Maintenance level AIX 5100-01 (64-bit)
Software requirements
Java Runtime Environment (JRE) Version 1.3.1 is required to run
DB2’s Java-based tools, such as the Control Center.
Communication requirements
You can use APPC, TCP/IP, and MPTN (APPC over TCP/IP)
v For TCP/IP connectivity, no additional software is required.
v For SNA (APPC) connectivity, one of the following communication
products is required:
Note: You should consider switching to TCP/IP as SNA may no
longer be supported in future releases of DB2 Connect. SNA
requires significant configuration knowledge and the
configuration process itself can prove to be error prone.
TCP/IP is simple to configure, has lower maintenance costs,
and provides superior performance.
– IBM eNetwork Communications Server for AIX Version 5.0.3 or
later.
– Bull DPX/20 SNA/20
Notes:
1. If you plan to use the Tivoli Storage Manager facilities to backup
and restore your databases, you require the Tivoli Storage
Manager Client Version 3 or later.
© Copyright IBM Corp. 1993-2002
31
2. If you plan to use the Simple Network Management Protocol
(SNMP) subagent, you require DPI 2.0 provided by IBM
SystemView Agent.
3. For LDAP (Lightweight Directory Access Protocol) support, you
require an IBM SecureWay Directory Client V3.1.1 running on AIX
Version 4.3.3 or higher.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (AIX)” on page 35
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (AIX)” on page
32
v “Disk requirements for DB2 Connect Enterprise Edition (AIX)” on page 33
Memory requirements for DB2 Connect Enterprise Edition (AIX)
The amount of memory required to run DB2 Connect Enterprise Edition
depends on the components you install. The following table provides
recommended memory requirements for DB2 Connect Enterprise Edition
installed with and without graphical tools such as the Control Center and
Configuration Assistant.
Table 3. DB2 Connect Enterprise Edition memory requirements on AIX
Type of installation
Recommended memory (RAM)
DB2 Connect Enterprise Edition without
graphical tools
64 MB
DB2 Connect Enterprise Edition with
graphical tools
128 MB
When determining memory requirements, be aware of the following:
v These memory requirements are for a base of 5 concurrent client
connections. You will need an additional 16 MB of RAM per 5 client
connections.
v These memory requirements do not account for non-DB2 software that may
be running on your system.
v Specific performance requirements may determine the amount of memory
required.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (AIX)” on page 35
32
DB2 Connect EE Quick Beginnings
Related reference:
v “Installation requirements for DB2 Connect Enterprise Edition (AIX)” on
page 31
v “Disk requirements for DB2 Connect Enterprise Edition (AIX)” on page 33
Disk requirements for DB2 Connect Enterprise Edition (AIX)
The disk requirements for DB2 Connect Enterprise Edition depend on the type
of installation and the components you install. The DB2 Setup wizard
provides typical, compact, and custom installation types. The following table
provides an approximate disk space requirement for each installation type.
Table 4. DB2 Connect Enterprise Edition disk requirements on AIX
Installation type
Required disk space
Typical
150 MB
Compact
80 MB
Custom
80 MB to 200 MB
Typical installation
DB2 Connect Enterprise Edition installed with a typical configuration
has most features and functionality. This installation includes
graphical tools such as the Control Center and Configuration
Assistant.
Compact installation
Only the basic DB2 Connect Enterprise Edition features and functions
are installed. Does not include graphical tools.
Custom installation
A custom installation allows you to select the features and functions
you want to install.
The DB2 Setup wizard will provide a disk space estimate for the installation
options you select.
Remember to include disk space allowance for required software,
communication products, and documentation. In DB2 Version 8, HTML and
PDF documentation is provided on separate CD-ROMs.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (AIX)” on page 35
Related reference:
Chapter 3. Installing DB2 Connect EE on AIX
33
v “Memory requirements for DB2 Connect Enterprise Edition (AIX)” on page
32
v “Installation requirements for DB2 Connect Enterprise Edition (AIX)” on
page 31
Mounting the CD-ROM on AIX
Prerequisites:
Root authority is required to perform this task.
Procedure:
To mount the CD-ROM on AIX using the System Management Interface Tool
(SMIT), perform the following steps:
1. Log in as a user with root authority.
2. Insert the CD-ROM in the drive.
3. Create a CD-ROM mount point by entering the mkdir -p /cdrom
command, where cdrom represents the CD-ROM mount point directory.
4. Allocate a CD-ROM file system using SMIT by entering the smit storage
command.
5. After SMIT starts, select File Systems —> Add / Change / Show / Delete
File Systems —> CDROM File Systems —> Add CDROM File System.
6. In the Add a File System window:
v Enter a device name for your CD-ROM file system in the DEVICE
Name field. Device names for CD-ROM file systems must be unique. If
there is a duplicate device name, you may need to delete a
previously-defined CD-ROM file system or use another name for your
directory. In our example, we will use /dev/cd0 as the device name.
v Enter the CD-ROM mount point directory in the MOUNT POINT
window. In our example, the mount point directory is /cdrom.
v In the Mount AUTOMATICALLY at system restart field, select yes to
enable automatic mounting of the file system.
v Click OK to close the window, then click Cancel three times to exit
SMIT.
7. Next, mount the CD-ROM file system by entering the smit mountfs
command.
8. In the Mount a File System window:
v Enter the device name for this CD-ROM file system in the FILE
SYSTEM name field. In our example, the device name is /dev/cd0.
34
DB2 Connect EE Quick Beginnings
v Enter the CD-ROM mount point in the Directory over which to mount
field. In our example, the mount point is /cdrom.
v Enter cdrfs in the Type of Filesystem field. To view the other kinds of
file systems you can mount, click List.
v In the Mount as READ-ONLY system field, select yes.
v Accept the remaining default values and click OK to close the window.
Your CD-ROM file system is now mounted. To view the contents of the
CD-ROM, place the disk in the drive and enter the cd /cdrom command
where cdrom is the CD-ROM mount point directory.
Installing DB2 Connect Enterprise Edition (AIX)
We recommend that you use the DB2 Setup wizard to install a DB2 product
on AIX. The DB2 Installer program is a Java-based installation tool that
automates the installation and configuration of any DB2 product. If you prefer
not to use this utility, you can install a DB2 product manually using the
db2_install script or rpm command.
Prerequisites:
Before you begin your installation:
v Ensure that your system meets:
– Memory requirements
– Hardware, distribution and software requirements
– Disk requirements
v Log on to the system as a user with root authority.
v The DB2 product CD-ROM must be mounted on your system. See
Mounting the CD-ROM on AIX.
Procedure:
To install DB2 Connect Enterprise Edition on AIX:
1. Change to the directory where the CD-ROM is mounted:
cd /cdrom
where /cdrom represents mount point of the CD-ROM.
Chapter 3. Installing DB2 Connect EE on AIX
35
2. Enter the ./db2setup command to start the DB2 Setup wizard. After a few
moments, the IBM DB2 Setup Launchpad opens.
From this window, you can view the installation prerequisites and the
release notes or you can proceed directly to the installation.
Once you have initiated the installation, proceed through the DB2 Setup
wizard installation panels and make your selections. Installation help is
available to guide you through the DB2 Setup wizard. To invoke the
installation help, click Help or press F1. You can click Cancel at any time
to exit the installation. DB2 files will only be copied to your system once
you have clicked Finish on the last DB2 Setup wizard installation panel.
When you have completed your installation, DB2 Connect Enterprise
Edition will be installed in /usr/opt/db2_08_01.
Related tasks:
v “Mounting the CD-ROM on AIX” on page 34
v Chapter 8, “Applying the latest FixPak” on page 65
v “Installing your DB2 Connect license key using the License Center” on page
68
v “Setting the license type using the License Center” on page 69
Related reference:
36
DB2 Connect EE Quick Beginnings
v “Memory requirements for DB2 Connect Enterprise Edition (AIX)” on page
32
v “Installation requirements for DB2 Connect Enterprise Edition (AIX)” on
page 31
v “Disk requirements for DB2 Connect Enterprise Edition (AIX)” on page 33
Chapter 3. Installing DB2 Connect EE on AIX
37
38
DB2 Connect EE Quick Beginnings
Chapter 4. Installing DB2 Connect EE on HP-UX
Installation requirements for DB2 Connect Enterprise Edition (HP-UX)
To install a DB2 Connect Enterprise Edition, the following operating system,
software, and communication requirements must be met:
Hardware requirements
HP 9000 Series 700 or 800 system
Operating system requirements
DB2 Connect Enterprise Edition can run on:
v HP-UX 11.0 with September 2001 QPK1100 bundle and patch
PHSS_24303
v HP-UX 11i with December 2001 GOLDBASE11i and December 2001
GOLDAPPS11i bundles.
Software requirements
Java Runtime Environment (JRE) Version 1.3.1 is required to run
DB2’s Java-based tools, such as the Control Center.
Communication requirements
You can use APPC, TCP/IP, and MPTN (APPC over TCP/IP)
v For TCP/IP connectivity, no additional software is required.
v For SNA (APPC) connectivity, you require either SNAplus2 Link
R6.11.00.00 or SNAplus2 API R6.11.00.00 is required. You should
consider switching to TCP/IP as SNA may no longer be supported
in future releases of DB2 Connect. SNA requires significant
configuration knowledge and the configuration process itself can
prove to be error prone. TCP/IP is simple to configure, has lower
maintenance costs, and provides superior performance.
Notes:
1. If you plan to use the Tivoli Storage Manager facilities for backup
and restore of your databases, you require the Tivoli Storage
Manager Client Version 3 or later.
2. If you plan to use the Simple Network Management Protocol
(SNMP) subagent, you require DPI 2.0 provided by IBM
SystemView Agent.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (HP-UX)” on page 44
© Copyright IBM Corp. 1993-2002
39
Related reference:
v “Recommended HP-UX kernel configuration parameters” on page 42
v “Memory requirements for DB2 Connect Enterprise Edition (HP-UX)” on
page 40
v “Disk requirements for DB2 Connect Enterprise Edition (HP-UX)” on page
41
Memory requirements for DB2 Connect Enterprise Edition (HP-UX)
The amount of memory required to run DB2 Connect Enterprise Edition
depends on the components you install. The following table provides
recommended memory requirements for DB2 Connect Enterprise Edition
installed with and without graphical tools such as the Control Center and
Configuration Assistant.
Table 5. DB2 Connect Enterprise Edition memory requirements on HP-UX
Type of installation
Recommended memory (RAM)
DB2 Connect Enterprise Edition without
graphical tools
64 MB
DB2 Connect Enterprise Edition with
graphical tools
128 MB
When determining memory requirements, be aware of the following:
v These memory requirements are for a base of 5 concurrent client
connections. You will need an additional 16 MB of RAM per 5 client
connections.
v These memory requirements do not account for non-DB2 software that may
be running on your system.
v Specific performance requirements may determine the amount of memory
required.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (HP-UX)” on page 44
Related reference:
v “Installation requirements for DB2 Connect Enterprise Edition (HP-UX)” on
page 39
v “Disk requirements for DB2 Connect Enterprise Edition (HP-UX)” on page
41
40
DB2 Connect EE Quick Beginnings
Disk requirements for DB2 Connect Enterprise Edition (HP-UX)
The disk requirements for DB2 Connect Enterprise Edition depend on the type
of installation and the components you install. The DB2 Setup wizard
provides typical, compact, and custom installation types. The following table
lists the approximate disk space requirement for each installation type.
Table 6. DB2 Connect Enterprise Edition disk requirements on HP-UX
Installation type
Required disk space
Typical
150 MB
Compact
80 MB
Custom
80 MB to 200 MB
Typical installation
DB2 Connect Enterprise Edition is installed with most features and
functionality, using a typical configuration. This installation includes
graphical tools such as the Control Center and Configuration
Assistant.
Compact installation
Only the basic DB2 Connect Enterprise Edition features and functions
are installed. This installation does not include graphical tools.
Custom installation
A custom installation allows you to select the features you want to
install.
The DB2 Setup wizard will provide a disk space estimate for the installation
options you select.
Remember to include disk space allowance for required software,
communication products, and documentation. In DB2 Version 8, HTML and
PDF documentation is provided on separate CD-ROMs.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (HP-UX)” on page 44
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (HP-UX)” on
page 40
v “Installation requirements for DB2 Connect Enterprise Edition (HP-UX)” on
page 39
Chapter 4. Installing DB2 Connect EE on HP-UX
41
Recommended HP-UX kernel configuration parameters
Table 7. HP-UX Kernel Configuration Parameters (Recommended Values)
Kernel
Parameter
Physical Memory
64MB - 128MB
128MB 256MB
256MB 512MB
maxuprc
256
384
512
1 500
maxfiles
256
256
256
256
nproc
512
768
1 024
2 048
nflocks
2 048
4 096
8 192
8 192
ninode
512
1 024
2 048
2 048
nfile
(4 * ninode)
(4 * ninode)
(4 * ninode)
(4 * ninode)
msgseg
8 192
16 384
32 767 (1)
32 767 (1)
msgmnb
65 535
65 535
65 535
65 535
msgmax
65 535
65 535
65 535
65 535
msgtql
256
512
1 024
2 048
msgmap
130
258
258
2 050
msgmni
128
256
256
1 024
msgssz
16
16
16
16
semmni
128
256
512
2 048
semmap
130
258
514
2 050
semmns
256
512
1 024
4 096
semmnu
256
512
1 024
1 024
shmmax
67 108 864
134 217 728 (2)
268 435 456 (2)
268 435 456 (2)
shmmni
300
300
300
1 000
Notes:
1. The msgseg parameter must be set no higher than 32 767.
42
512MB+
DB2 Connect EE Quick Beginnings
2. The shmmax parameter should be set to 134 217 728 or 90% of the physical
memory (in bytes), whichever is higher. For example, if you have 196 MB
of physical memory in your system, set shmmax to 184 968 806
(196*1024*1024*0.9).
3. To maintain the interdependency among kernel parameters, change
parameters in the same sequence in which they appear in the preceding
table.
Related tasks:
v “Modifying kernel parameters (HP-UX)” in the Quick Beginnings for DB2
Servers
Mounting the CD-ROM on HP-UX
Because DB2 Version 8.1 for HP-UX contains several files with long file
names, the mount command may fail. The following steps will enable you to
successfully mount your DB2 for HP-UX product CD-ROM.
Prerequisites:
Root authority is required to perform this task.
Procedure:
To mount your DB2 for HP-UX product CD-ROM:
1. Log in as a user with root authority.
2. In the /etc directory, add the following line to the pfs_fstab file:
/dev/dsk/c0t2d0 mount_point pfs-rrip ro,hard
where mount_point represents the mount point of the CD-ROM.
3. Start the pfs daemon by entering the following commands (if they are not
already running):
/usr/sbin/pfs_mountd &
/usr/sbin/pfsd 4 &
4. Insert the CD-ROM in the drive and enter the following commands:
mkdir /cdrom
/usr/sbin/pfs_mount /cdrom
where /cdrom represents the mount point of the CD-ROM.
5. Log out.
Chapter 4. Installing DB2 Connect EE on HP-UX
43
Your CD-ROM file system is now mounted. To view the contents of the
CD-ROM, place the CD in the drive and enter the cd /cdrom command where
cdrom is the CD-ROM mount point directory.
Installing DB2 Connect Enterprise Edition (HP-UX)
We recommend that you use the DB2 Setup wizard to install a DB2 product
on HP-UX. The DB2 Installer program is a Java-based installation tool that
automates the installation and configuration of any DB2 product. If you prefer
not to use this utility, you can install a DB2 product manually using the
db2_install script or rpm command.
Prerequisites:
Before begin your installation:
v Ensure that your system meets:
– Memory requirements
– Hardware, distribution and software requirements
– Disk requirements
v Log on to the system as a user with root authority.
v The DB2 product CD-ROM must be mounted on your system. See
Mounting the CD-ROM on HP-UX.
Procedure:
To install DB2 Connect Enterprise Edition on HP-UX:
1. Change to the directory where the CD-ROM is mounted by entering the
following command:
cd /cdrom
where /cdrom represents the mount point of the CD-ROM.
44
DB2 Connect EE Quick Beginnings
2. Enter the ./db2setup command to start the DB2 Setup wizard. After a few
moments, the IBM DB2 Setup Launchpad opens.
From this window, you can view the installation prerequisites and the
release notes or you can proceed directly to the installation.
Once you have initiated the installation, proceed through the DB2 Setup
wizard installation panels and make your selections. Installation help is
available to guide you through the DB2 Setup wizard. To invoke the
installation help, click Help or press F1. You can click Cancel at any time
to exit the installation. DB2 files will only be copied to your system once
you have clicked Finish on the last DB2 Setup wizard installation panel.
When you have completed your installation, DB2 Connect Enterprise
Edition will be installed in /opt/IBM/db2/V8.1.
Related tasks:
v “Mounting the CD-ROM on HP-UX” on page 43
v Chapter 8, “Applying the latest FixPak” on page 65
v “Installing your DB2 Connect license key using the License Center” on page
68
v “Setting the license type using the License Center” on page 69
Related reference:
Chapter 4. Installing DB2 Connect EE on HP-UX
45
v “Recommended HP-UX kernel configuration parameters” on page 42
v “Memory requirements for DB2 Connect Enterprise Edition (HP-UX)” on
page 40
v “Installation requirements for DB2 Connect Enterprise Edition (HP-UX)” on
page 39
v “Disk requirements for DB2 Connect Enterprise Edition (HP-UX)” on page
41
46
DB2 Connect EE Quick Beginnings
Chapter 5. Installing DB2 Connect EE on Linux
Installation requirements for DB2 Connect Enterprise Edition (Linux)
To install a DB2 Connect Enterprise Edition, the following operating system,
software, and communication requirements must be met:
Hardware requirements
Your processor can be:
v x86 compatible (for example, Intel, AMD, or Cyrix)
v Intel Itanium processor (IA64) for the 64 bit version of Linux
v S/390 9672 Generation 5 or higher, Multiprise 3000
v eServer zSeries
Distribution requirements
For 32-bit installations, you require a recent Linux operating system
distribution with:
v kernel level 2.4.9 or higher
v glibc 2.2.4 or higher
v pdksh 5.2 or higher
v rpm 4.0 or greater
You require one of the following Linux operating system distributions
for 64-bit and zSeries installation:
v Red Hat Linux 7.2
v SuSE Linux SLES-7
Software requirements
v IBM Developer Kit for Linux, Java 2 Technology Edition, Version
1.3.1. This is an optional component, but is required to use the DB2
Control Center to administer your databases using a graphical user
interface and create or run Java applications, including stored
procedures and user-defined functions. The DB2 Setup wizard will
install the IBM JDK for you if an existing JDK is not detected. Only
the IBM JDK is supported.
v For 64-bit Linux, gcc 3.0.2 and the gcc3 libstdc++ runtime libraries
is required for IBM JDK
Communication requirements
For TCP/IP connectivity, no additional software is required.
Related tasks:
© Copyright IBM Corp. 1993-2002
47
v “Installing DB2 Connect Enterprise Edition (Linux)” on page 50
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (Linux)” on
page 48
v “Disk requirements for DB2 Connect Enterprise Edition (Linux)” on page 49
Memory requirements for DB2 Connect Enterprise Edition (Linux)
The amount of memory required to run DB2 Connect Enterprise Edition
depends on the components you install. The following table provides
recommended memory requirements for DB2 Connect Enterprise Edition
installed with and without graphical tools such as the Control Center and
Configuration Assistant.
Table 8. DB2 Connect Enterprise Edition memory requirements on Linux
Type of installation
Recommended memory (RAM)
DB2 Connect Enterprise Edition without
graphical tools
64 MB
DB2 Connect Enterprise Edition with
graphical tools
128 MB
When determining memory requirements, be aware of the following:
v These memory requirements are for a base of 5 concurrent client
connections. You will need an additional 16 MB of RAM per 5 client
connections.
v These memory requirements do not account for non-DB2 software that may
be running on your system.
v Specific performance requirements may determine the amount of memory
required.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (Linux)” on page 50
Related reference:
v “Installation requirements for DB2 Connect Enterprise Edition (Linux)” on
page 47
v “Disk requirements for DB2 Connect Enterprise Edition (Linux)” on page 49
48
DB2 Connect EE Quick Beginnings
Disk requirements for DB2 Connect Enterprise Edition (Linux)
The disk requirements for DB2 Connect Enterprise Edition depend on the type
of installation and the components you install. The DB2 Setup wizard
provides typical, compact, and custom installation types. The following table
provides an approximate disk space requirement for each installation type.
Table 9. DB2 Connect Enterprise Edition disk requirements on Linux
Installation type
Required disk space
Typical
150 MB
Compact
80 MB
Custom
80 MB to 200 MB
Typical installation
DB2 Connect Enterprise Edition is installed with most features and
functionality, using a typical configuration. This installation includes
graphical tools such as the Control Center and Configuration
Assistant.
Compact installation
Only the basic DB2 Connect Enterprise Edition features and functions
are installed. This installation does not include graphical tools.
Custom installation
A custom installation allows you to select the features you want to
install.
The DB2 Setup wizard will provide a disk space estimate for the installation
options you select.
Remember to include disk space allowance for required software,
communication products, and documentation. In DB2 Version 8, HTML and
PDF documentation is provided on separate CD-ROMs.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (Linux)” on page 50
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (Linux)” on
page 48
v “Installation requirements for DB2 Connect Enterprise Edition (Linux)” on
page 47
Chapter 5. Installing DB2 Connect EE on Linux
49
Mounting the CD-ROM on Linux
Prerequisites:
Root authority is required to perform this task.
Procedure:
To mount the CD-ROM on Linux:
1. Log in as a user with root authority.
2. Insert the CD-ROM in the drive and enter the following command:
mount -t iso9660 -o ro /dev/cdrom /cdrom
where /cdrom represents the mount point of the CD-ROM.
3. Log out.
Your CD-ROM file system is now mounted. To view the contents of the
CD-ROM, place the disk in the drive and enter the cd /cdrom command
where cdrom is the CD-ROM mount point directory.
Installing DB2 Connect Enterprise Edition (Linux)
We recommend that you use the DB2 Setup wizard to install a DB2 product
on Linux. The DB2 Setup wizard is a Java-based installation tool that
automates the installation and configuration of any DB2 products. If you
prefer not to use this utility, you can install a DB2 product manually using the
db2_install script or rpm command.
Prerequisites:
Before you begin your installation:
v Ensure that your system meets:
– Memory requirements
– Hardware, distribution and software requirements
– Disk requirements
v Log on to the system as a user with root authority.
v The DB2 product CD-ROM must be mounted on your system. See
Mounting the CD-ROM on Linux.
Procedure:
To install DB2 Connect Enterprise Edition on Linux:
50
DB2 Connect EE Quick Beginnings
1. Change to the directory where the CD-ROM is mounted by entering the
following command:
cd /cdrom
where /cdrom represents the mount point of the CD-ROM.
2. Enter the ./db2setup command to start the DB2 Setup wizard. After a few
moments, the IBM DB2 Setup Launchpad opens.
From this window, you can view the installation prerequisites and the
release notes or you can proceed directly to the installation.
Once you have initiated the installation, proceed through the DB2 Setup
wizard installation panels and make your selections. Installation help is
available to guide you through the DB2 Setup wizard. To invoke the
installation help, click Help or press F1. You can click Cancel at any time
to exit the installation. DB2 files will only be copied to your system once
you have clicked Finish on the last DB2 Setup wizard installation panel.
When you have completed your installation, DB2 Connect Enterprise
Edition will be installed in /opt/IBM/db2/V8.1.
Related tasks:
v “Mounting the CD-ROM on Linux” on page 50
v Chapter 8, “Applying the latest FixPak” on page 65
Chapter 5. Installing DB2 Connect EE on Linux
51
v “Installing your DB2 Connect license key using the License Center” on page
68
v “Setting the license type using the License Center” on page 69
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (Linux)” on
page 48
v “Installation requirements for DB2 Connect Enterprise Edition (Linux)” on
page 47
v “Disk requirements for DB2 Connect Enterprise Edition (Linux)” on page 49
Preparing to install DB2 for Linux on S/390
To install DB2 on an S/390 machine that is running Linux, you will have to
make the installation image accessible to the S/390 machine. You can use FTP
to send the installation image to the S/390 machine or you can NFS mount
the CD-ROM.
Prerequisites:
If you have DB2 beta code installed, you must remove it before installing
DB2. Migration from beta code is not supported.
Procedure:
Using FTP
Create a tar file of the contents of DB2 installation CD-ROM. Put this
tar file on your FTP server.
From the S/390 machine running Linux:
1. Enter the ftp yourserver.com command, where yourserver.com
represents the FTP server where the installation image resides.
2. Enter your user ID and password.
3. Enter the following commands:
bin
get filename.tar
where filename represents the appropriate product package name.
4. Untar the installation image by entering the tar -xvf filename .tar
command
Using an NFS mount
To use the DB2 product CD-ROM on a UNIX-based operating system:
52
DB2 Connect EE Quick Beginnings
1. Mount the appropriate CD-ROM on a UNIX-based operating
system.
2. Export the directory where you mounted the CD-ROM. For
example, if you mounted the CD-ROM under /cdrom , then export
the /cdrom directory.
3. On the S/390 machine running Linux, NFS mount this directory
using the following command:
mount -t nfs -o ro nfsservername :/cdrom /local_directory_name
where:
v nfsservername represents the name of the NFS server
v cdrom represents the name of the directory on the NFS server
v local_directory_name represents the name of the local directory
4. From the S/390 machine running Linux, change to the directory
where the CD-ROM is mounted. You can do this by entering the
cd /local_directory_name command, where local_directory_name
represents the mount point of your product CD-ROM.
Related tasks:
v “Installing DB2 Personal Edition using the DB2 Setup wizard (Linux)” in
the Quick Beginnings for DB2 Personal Edition
Chapter 5. Installing DB2 Connect EE on Linux
53
54
DB2 Connect EE Quick Beginnings
Chapter 6. Installing DB2 Connect EE on Solaris
Installation requirements for DB2 Connect Enterprise Edition (Solaris)
To install a DB2 Connect Enterprise Edition, the following operating system,
software, and communication requirements must be met:
Hardware requirements
Solaris UltraSPARC-based computer
Operating system requirements
DB2 Connect Enterprise Edition is supported on the following Solaris
Operating Environment versions:
v Solaris 7 (32-bit) patch 106327-8
v Solaris 7 (64-bit) patch 106300-09
v Solaris 7 ″Recommended & Security Patches″ + 107226-17 +
107153-01
v Solaris 8 (32-bit) patch 108434-01 + 108528-12
v Solaris 8 (64-bit) patch 108435-01 + 108528-12
v Solaris 8 ″Recommended & Security Patches″ + 108921-12 +
108940-24
v Solaris 9 (32-bit)
v Solaris 9 (64-bit)
Software requirements
Java Runtime Environment (JRE) Version 1.3.1 is required to run
DB2’s Java-based tools, such as the Control Center.
Communication requirements
You can use APPC or TCP/IP
v For TCP/IP connectivity, no additional software is required.
v For APPC (SNA) connectivity, you require SunLink SNA 9.1 or later,
and the following communication products:
– SunLink P2P LU6.2 9.0 or later
– SunLink PU2.1 9.0 or later
– SunLink P2P CPI–C 9.0 or later
Note: You should consider switching to TCP/IP as SNA may no
longer be supported in future releases of DB2 Connect. SNA
requires significant configuration knowledge and the
configuration process itself can prove to be error prone.
© Copyright IBM Corp. 1993-2002
55
TCP/IP is simple to configure, has lower maintenance costs,
and provides superior performance.
Notes:
1. If you plan to use the Tivoli Storage Manager facilities for the
backup and restore of your databases, you require the Tivoli
Storage Manager Client Version 3 or later.
2. DB2 Connect is supported on Sun Cluster 2.2 if:
v The protocol to the host is TCP/IP (not SNA)
v Two-phase commit is not used. This restriction is relaxed if the
user configures the SPM log to be on a shared disk (this can be
done through the spm_log_path database manager configuration
parameter), and the failover machine has an identical TCP/IP
configuration (the same host name, IP address, and so on).
Related tasks:
v “Installing DB2 Connect Enterprise Edition (Solaris)” on page 59
Related reference:
v “Recommended Solaris kernel configuration parameters” on page 58
v “Memory requirements for DB2 Connect Enterprise Edition (Solaris)” on
page 56
v “Disk requirements for DB2 Connect Enterprise Edition (Solaris)” on page
57
Memory requirements for DB2 Connect Enterprise Edition (Solaris)
The amount of memory required to run DB2 Connect Enterprise Edition
depends on the components you install. The following table provides
recommended memory requirements for DB2 Connect Enterprise Edition
installed with and without graphical tools such as the Control Center and
Configuration Assistant.
Table 10. DB2 Connect Enterprise Edition memory requirements on Solaris
Type of installation
Recommended memory (RAM)
DB2 Connect Enterprise Edition without
graphical tools
64 MB
DB2 Connect Enterprise Edition with
graphical tools
128 MB
When determining memory requirements, be aware of the following:
56
DB2 Connect EE Quick Beginnings
v These memory requirements are for a base of 5 concurrent client
connections. You will need an additional 16 MB of RAM per 5 client
connections.
v These memory requirements do not account for non-DB2 software that may
be running on your system.
v Specific performance requirements may determine the amount of memory
required.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (Solaris)” on page 59
Related reference:
v “Installation requirements for DB2 Connect Enterprise Edition (Solaris)” on
page 55
v “Disk requirements for DB2 Connect Enterprise Edition (Solaris)” on page
57
Disk requirements for DB2 Connect Enterprise Edition (Solaris)
The disk requirements for DB2 Connect Enterprise Edition depend on the type
of installation and the components you install. The DB2 Setup wizard
provides typical, compact, and custom installation types. The following table
provides an approximate disk space requirement for each installation type.
Table 11. DB2 Connect Enterprise Edition disk requirements on Solaris
Installation type
Required disk space
Typical
150 MB
Compact
80 MB
Custom
80 MB to 200 MB
Typical installation
DB2 Connect Enterprise Edition is installed with most features and
functionality, using a typical configuration. This installation includes
graphical tools such as the Control Center and Configuration
Assistant.
Compact installation
Only the basic DB2 Connect Enterprise Edition features and functions
are installed. This installation does not include graphical tools.
Custom installation
A custom installation allows you to select the features you want to
install.
Chapter 6. Installing DB2 Connect EE on Solaris
57
The DB2 Setup wizard will provide a disk space estimate for the installation
options you select.
Remember to include disk space allowance for required software,
communication products, and documentation. In DB2 Version 8, HTML and
PDF documentation is provided on separate CD-ROMs.
Related tasks:
v “Installing DB2 Connect Enterprise Edition (Solaris)” on page 59
Related reference:
v “Memory requirements for DB2 Connect Enterprise Edition (Solaris)” on
page 56
v “Installation requirements for DB2 Connect Enterprise Edition (Solaris)” on
page 55
Recommended Solaris kernel configuration parameters
Setting kernel configuration parameters before installation: Use the sample
files:
Sample files for updating the kernel configuration parameters are
provided on the DB2 product CD-ROM in the /db2/install/samples
directory. The names for these files are as follows:
kernel.param.128MB
for systems with 128MB–256MB of physical memory
kernel.param.256MB
for systems with 256MB–512MB of physical memory
kernel.param.512MB
for systems with 512MB–1GB of physical memory
Refining kernel parameter settings after installation
After installation, the db2osconf utility can be used to recommend
more accurate kernel parameters based on the size and configuration
of your system. If your system has more than 1GB of RAM, use the
values from the kernel.param.512MB file for the installation, and then
run the db2osconf utility to provide more accurate values. NOTE: the
db2osconf utility does not change the /etc/system file and the system
must be restarted in order for any changes to the /etc/system file take
place.
Related concepts:
v “db2osconf - Utility for Kernel Parameter Values” in the Command Reference
58
DB2 Connect EE Quick Beginnings
Related tasks:
v “Modifying kernel parameters (Solaris)” in the Quick Beginnings for DB2
Servers
Mounting the CD-ROM on Solaris
Prerequisites:
If you are mounting the CD-ROM drive from a remote system using NFS, the
CD-ROM file system on the remote machine must be exported with root
access. You must also mount that file system with root access on the local
machine.
Procedure:
To
1.
2.
3.
mount the CD-ROM on Solaris:
Log in as a user with root authority.
Insert the CD-ROM into the drive.
If the Volume Manager is not running on your system, enter the following
commands to mount the CD-ROM:
mkdir -p /cdrom/unnamed_cdrom
mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom/unnamed_cdrom
where /cdrom/unnamed_cdrom represents the CD-ROM mount directory
and /dev/dsk/c0t6d0s2 represents the CD-ROM drive device.
If the Volume Manager (vold) is running on your system, the CD-ROM is
automatically mounted as:
/cdrom/unnamed_cdrom
4. Log out.
Your CD-ROM file system is now mounted. To view the contents of the
CD-ROM, place the disk in the drive and enter the cd /cdrom command
where cdrom is the CD-ROM mount point directory.
Installing DB2 Connect Enterprise Edition (Solaris)
We recommend that you use the DB2 Setup wizard to install a DB2 product
on Solaris. The DB2 Installer program is a Java-based installation tool that
automates the installation and configuration of any DB2 products. If you
prefer not to use this utility, you can install a DB2 product manually using the
db2_install script or rpm command.
Chapter 6. Installing DB2 Connect EE on Solaris
59
Prerequisites:
Before you begin your installation:
v Ensure that your system meets:
– Memory requirements
– Hardware, distribution and software requirements
– Disk requirements
v Log on to the system as a user with root authority.
v The DB2 product CD-ROM must be mounted on your system. See
Mounting the CD-ROM on Solaris.
v You need to have a filesystem with 2 GB of free space to contain the tar.Z
file and the uncompressed installation image (in addition to the software
disk requirements).
Procedure:
To install DB2 Connect Enterprise Edition on Solaris:
1. Change to the directory where the CD-ROM is mounted by entering the
following command:
cd /cdrom
where /cdrom represents mount point of the CD-ROM.
2. Copy product.tar.Z, where product represents the product you are
licensed to install, to a temporary filesystem.
3. Enter the zcat product.tar.Z | tar -xf - ; ./product/db2setup command to
start the DB2 Setup wizard. For example, if the product name for DB2
Connect Enterprise Edition is conee, then enter the following command:
zcat conee.tar.Z | tar -xf - ; ./conee/db2setup.
60
DB2 Connect EE Quick Beginnings
After a moment, the IBM DB2 Setup Launchpad opens.
From this window, you can view the installation prerequisites and the
release notes or you can proceed directly to the installation.
Once you have initiated the installation, proceed through the DB2 Setup
wizard installation panels and make your selections. Installation help is
available to guide you through the DB2 Setup wizard. To invoke the
installation help, click Help or press F1. You can click Cancel at any time
to end the installation. DB2 files will only be copied to your system once
you have clicked Finish on the last DB2 Setup wizard installation panel.
When you have completed your installation, DB2 Connect Enterprise
Edition will be installed in /opt/IBM/db2/V8.1.
Related tasks:
v “Mounting the CD-ROM on Solaris” on page 59
v Chapter 8, “Applying the latest FixPak” on page 65
v “Installing your DB2 Connect license key using the License Center” on page
68
v “Setting the license type using the License Center” on page 69
Related reference:
v “Recommended Solaris kernel configuration parameters” on page 58
Chapter 6. Installing DB2 Connect EE on Solaris
61
v “Memory requirements for DB2 Connect Enterprise Edition (Solaris)” on
page 56
v “Installation requirements for DB2 Connect Enterprise Edition (Solaris)” on
page 55
v “Disk requirements for DB2 Connect Enterprise Edition (Solaris)” on page
57
62
DB2 Connect EE Quick Beginnings
Chapter 7. Migrating from previous versions of DB2
Connect
DB2 Connect Version 8 supports the migration of DB2 databases and instances
created with DB2 Version 6 and Version 7. If you are migrating from one of
these versions to DB2 Connect Version 8, you should prepare your databases
and instances before installing DB2.
Since DB2 Connect Enterprise Edition (EE) is a host database connectivity
server, the only databases that may exist within a DB2 Connect EE server
instance is a DB2 transaction manager database. This database is used by DB2
to store transaction state information for DB2 coordinated transactions.
You should migrate the DB2 Connect instance to avoid dropping and
recreating your instances, because these instances will need to be recataloged
on all the remote nodes and databases. If you drop and recreate your instance
you will also have to recatalog and NODE, DCS, or DB catalogs that existed
prior to the instance will be dropped.
Related concepts:
v “Migration recommendations” in the Quick Beginnings for DB2 Servers
Related tasks:
v “Backing up databases before DB2 migration” in the Quick Beginnings for
DB2 Servers
v “Verifying that your databases are ready for migration” in the Quick
Beginnings for DB2 Servers
v “Migrating databases” in the Quick Beginnings for DB2 Servers
v “Migrating Explain tables” in the Quick Beginnings for DB2 Servers
v “Migrating instances (UNIX)” in the Quick Beginnings for DB2 Servers
v “Migrating DB2 (Windows)” in the Quick Beginnings for DB2 Servers
v “Migrating DB2 (UNIX)” in the Quick Beginnings for DB2 Servers
Related reference:
v “Migration restrictions” in the Quick Beginnings for DB2 Servers
© Copyright IBM Corp. 1993-2002
63
64
DB2 Connect EE Quick Beginnings
Chapter 8. Applying the latest FixPak
Applying the latest FixPak is optionally part of the larger task of Installing DB2.
A DB2 FixPak contains updates and fixes for bugs (Authorized Program
Analysis Reports, or ″APARs″) found during testing at IBM, as well as fixes
for bugs reported by customers. Every FixPak is accompanied by a document,
called APARLIST.TXT, that describes the bug fixes it contains.
FixPaks are cumulative. This means that the latest FixPak for any given
version of DB2 contains all of the updates from previous FixPaks for the same
version of DB2. We recommend that you keep your DB2 environment running
at the latest FixPak level to ensure problem-free operation.
When installing a FixPak on a partitioned ESE system, all participating
computers must have the same FixPak installed while the system is offline
before bring the system online.
Prerequisites:
Each FixPak may have specific prerequisites. See the FixPak README that
accompanies the FixPak for more information.
Procedure:
1. Download the latest DB2 FixPak from the IBM DB2 UDB and DB2
Connect Online Support Web site at
http://www.ibm.com/software/data/db2/udb/winos2unix/support.
2. Each FixPak contains a set of Release Notes and a README. The
README provides instructions for installing the FixPak.
Your next step is Verifying the installation using the command line processor (CLP).
© Copyright IBM Corp. 1993-2002
65
66
DB2 Connect EE Quick Beginnings
Chapter 9. DB2 Connect license activation
The installation programs for DB2 Connect Enterprise Edition, and DB2
Connect Unlimited Edition do not install the product licenses. After
installation, these products will operate in the Try-and-Buy mode for a period
of 90 days since their license files have not been activated. After the 90-day
period, the product that you installed will stop functioning unless you
activate the proper license.
To activate a license for your product you can use either the DB2 License
Center or the db2licm command.
Installing your DB2 Connect license key using the db2licm command
You can use the db2licm command to add the license key instead of using the
License Center.
Procedure:
To add your license key using the db2licm command:
v On Windows: db2licm -a x:\db2\license\license_filename, where x:
represents the CD-ROM drive that contains the DB2 Connect product CD.
v On UNIX: db2licm -a db2/license/license_filename
where license_filename represents:
db2conee.lic
DB2 Connect Enterprise Edition
db2conpe.lic
DB2 Connect Personal Edition
db2conue.lic
DB2 Connect Unlimited Edition
Related tasks:
v “Installing your DB2 Connect license key using the License Center” on page
68
v “Setting the license type using the db2licm command” on page 69
v “Setting the license type using the License Center” on page 69
© Copyright IBM Corp. 1993-2002
67
Installing your DB2 Connect license key using the License Center
You can install your license key using the License Center.
Procedure:
To install your license key using the License Center:
1. Start the DB2 Control Center and select License Center from the Tools
menu.
2. Select the system for which you are installing a license. The Installed
Products field will display the name of the product that you have
installed.
3. Select Add from the License menu.
4. In the Add License window, select the From a file radio button and select
a license file:
v On Windows servers: x:\db2\license\license_filename where x:
represents the CD-ROM drive containing DB2 Connect product CD.
v On UNIX servers: /db2/license/license_filename
where license_filename represents:
db2conee.lic
DB2 Connect Enterprise Edition
db2conpe.lic
DB2 Connect Personal Edition
db2conue.lic
DB2 Connect Unlimited Edition
5. Click Apply to add the license key.
Related tasks:
v “Installing your DB2 Connect license key using the db2licm command” on
page 67
v “Setting the license type using the db2licm command” on page 69
v “Setting the license type using the License Center” on page 69
68
DB2 Connect EE Quick Beginnings
Setting the license type using the db2licm command
You can use the db2licm command to set your license type instead of using
the License Center.
Procedure:
To set your license type using the db2licm command:
v For DB2 Connect Unlimited Edition:
Enter the following command:
db2licm -p db2conee measured
v For DB2 Connect Enterprise Edition:
If you purchased Concurrent User licenses, enter the following commands:
db2licm -p db2conee concurrent
db2licm -u N
where N represents the number of concurrent user licenses that you have
purchased.
If you purchased Registered User licenses, enter the following command:
db2licm -p db2conee registered
Related tasks:
v “Installing your DB2 Connect license key using the db2licm command” on
page 67
v “Installing your DB2 Connect license key using the License Center” on page
68
v “Setting the license type using the License Center” on page 69
Setting the license type using the License Center
You can set your license type using the License Center.
Procedure:
To set your license type:
v For DB2 Connect Unlimited Edition:
In the License Center, select Change from the License menu. In the Change
License window, select the Measured usage check box. Click OK to close
the Change License window and return to the License Center.
v For DB2 Connect Enterprise Edition:
Chapter 9. DB2 Connect license activation
69
In the License Center, select Change from the License menu. In the Change
License window, select the type of license that you have purchased.
– If you purchased a Concurrent Users license, select Concurrent DB2
Connect users and enter the number of user licenses that you have
purchased.
Note: DB2 Connect Enterprise Edition provides a license for one user.
Additional DB2 Connect User licenses must be purchased
separately.
– If you purchased a Registered Users license, select Registered DB2
Connect users and click OK to close the Change License window and
return to the License Center. Click on the Users tab and add every user
ID for which you purchased a license.
Related tasks:
v “Installing your DB2 Connect license key using the db2licm command” on
page 67
v “Installing your DB2 Connect license key using the License Center” on page
68
v “Setting the license type using the db2licm command” on page 69
70
DB2 Connect EE Quick Beginnings
Part 3. Preparing host and iSeries databases for DB2
Connect communications
These topics describe the steps required to configure host and iSeries database
servers to accept connections from DB2 Connect workstations. These steps
must be performed by users who have the necessary system privileges and
special expertise, such as your network, system, or DB2 administrator.
For more information on configuring host and iSeries database servers, refer
to the following publications:
v The DB2 for OS/390 and z/OS Installation Guide Version 7 (GC26-9936-01)
contains the most complete and up-to-date information for DB2 Universal
Database for OS/390 and z/OS.
v Distributed Relational Database Cross Platform Connectivity and Applications
contains useful post-configuration information.
v AS/400 Distributed Database Programming
The sample values used in this section match those used elsewhere in this
book. When you follow the instructions provided you must substitute your
own values for elements such as network name, Logical Unit (LU) name, and
mode name.
© Copyright IBM Corp. 1993-2002
71
72
DB2 Connect EE Quick Beginnings
Chapter 10. Preparing DB2 for OS/390 and z/OS databases
for DB2 Connect communications
Preparing DB2 Universal Database for OS/390 and z/OS for connections from
DB2 Connect
Your VTAM administrator and your host system administrator must configure
VTAM and OS/390 or z/OS to prepare DB2 Universal Database for OS/390
and z/OS to receive inbound connection requests from your DB2 Connect
workstation.
This topic provides:
v Examples of VTAM definitions required at your DB2 Universal Database for
OS/390 and z/OS host for use with DB2 Connect SNA connections. These
should be compared with current definitions.
v Instructions for establishing TCP/IP network connections between DB2
Connect and DB2 Universal Database for OS/390 and z/OS.
v DB2 host configuration steps. Many details of these steps changed with the
introduction of DB2 UDB for OS/390 Version 5.1. Most of these steps apply
to SNA users, but some also apply to users who will connect to DB2
Universal Database for OS/390 and z/OS via TCP/IP.
If you anticipate that DB2 for OS/390 or z/OS will participate in a multisite
update transaction (two-phase commit) then refer to the Enabling Multisite
Updates topic.
Procedure:
To prepare DB2 Universal Database for OS/390 and z/OS to receive
connection requests from DB2 Connect, you need to configure your protocol:
v Configuring DB2 Universal Database for OS/390 and z/OS
v Configuring TCP/IP for DB2 Universal Database for OS/390 and z/OS
v Configuring VTAM
Related tasks:
v “Configuring DB2 Universal Database for OS/390 and z/OS” on page 74
v “Configuring TCP/IP for DB2 Universal Database for OS/390 and z/OS”
on page 75
v “Configuring VTAM” on page 78
v “Enabling Multisite Updates using the Control Center” on page 96
© Copyright IBM Corp. 1993-2002
73
Configuring DB2 Universal Database for OS/390 and z/OS
Before you can use DB2 Connect, your DB2 Universal Database for OS/390
and z/OS Administrator must configure DB2 Universal Database for OS/390
and z/OS to permit connections from DB2 Connect workstations. This section
indicates the minimum updates required to permit a DB2 Connect client to
make a connection to the DB2 Universal Database for OS/390 and z/OS
database server. For more detailed examples, refer to the DB2 for OS/390 and
z/OS Installation Guide.
Recommended APARs:
DB2 for OS/390 and z/OS Version 7: Apply the fixes for APARs PQ50016 and
PQ50017.
Updating SYSIBM.LUNAMES:
This section contains examples of commands to update these tables for DB2
Universal Database for OS/390 and z/OS. Work with your DB2 administrator
to determine the updates required for your DB2 Universal Database for
OS/390 and z/OS system. For more information on the DB2 Universal
Database for OS/390 and z/OS communications database tables, refer to the
DB2 Universal Database for OS/390 and z/OS SQL Reference.
To permit database connection requests to be accepted from any incoming
DB2 Connect LU, just insert a blank row. Use an SQL similar to the following:
INSERT INTO SYSIBM.LUNAMES (LUNAME) VALUES (’
’)
Alternatively, if you want to restrict access by LU name, you can use an SQL
command similar to the following to update this table:
INSERT INTO SYSIBM.LUNAMES (LUNAME,
SECURITY_OUT,
ENCRYPTPSWDS,
USERNAMES)
VALUES(’NYX1GW01’,’P’,’N’,’O’);
Result:
Table 12. Result set from update to table
74
COLUMN
EXAMPLE
REMARK
======
=======
======
LUNAME
NYX1GW01
Name of the DB2 Connect LU
SECURITY_OUT
P
ENCRYPTPSWDS
N
DB2 Connect EE Quick Beginnings
Table 12. Result set from update to table (continued)
COLUMN
EXAMPLE
USERNAMES
O
REMARK
Configuring TCP/IP for DB2 Universal Database for OS/390 and z/OS
This topic describes how to configure TCP/IP communications between your
DB2 Connect workstation and DB2 UDB for OS/390 Version 5.1 or later. The
instructions assume the following conditions:
v You are connecting to a single host database via TCP/IP. Multiple host
connections will be handled in exactly the same way, although the port
number and service number required in each case may be different.
v The target database resides on DB2 UDB for OS/390 Version 5.1 or later.
v All the necessary software prerequisites are installed.
v DB2 clients have been set up as required.
Prerequisite OS/390 software for TCP/IP support:
OS/390 V2R3+ is the minimum operating system level required for TCP/IP
support. OS/390 V2R5+ is the recommended operating system level, and the
best performer. All versions of z/OS support TCP/IP.
The following informational APARs for DB2 for OS/390 are regularly updated
with information about PTFs to install for various OS/390 components,
particularly TCP/IP for OS/390. If you use TCP/IP connectivity with DB2 for
OS/390, it is extremely important that you review and apply PTFs and APAR
fixes described in the following DB2 for OS/390 information APARs:
v II11164
v II11263
v II10962
Collecting information:
Before you can use DB2 Connect over a TCP/IP connection, you must collect
information about both the host database server and the DB2 Connect server.
For each host server that you are connecting to via TCP/IP, you must have
the following information:
v The location of the TCP/IP services and hosts files at the DB2 Connect
workstation:
On UNIX
/etc/
Chapter 10. Preparing DB2 for OS/390 and z/OS databases for DB2 Connect communications
75
On Windows NT, Windows 2000, Windows XP and Windows .NET
Usually %SystemRoot%\system32\drivers\etc\, where
%SystemRoot% represents the Windows install path directory.
On Windows 98 and Windows ME
Usually x:\windows\, where x: represents the Windows install path
directory.
You may want to add the host information to a domain name server to avoid
maintaining this file on multiple systems.
v The locations of the equivalent files at the target DB2 Universal Database
for OS/390 and z/OS host.
v The TCP/IP port number defined to DB2 Universal Database for OS/390 and
z/OS.
Note: The associated service name information is not exchanged between the
DB2 Connect workstation and DB2 Universal Database for OS/390
and z/OS.
Port number 446 has been registered as the default for communication from
a DB2 Connect workstation.
v The TCP/IP addresses and host names for both the host and the DB2
Connect workstation.
v The LOCATION NAME of the DB2 for OS/390 database server.
v The user ID and password to be used when issuing CONNECT requests to
the database at the host or iSeries server.
Refer to your local network administrator and your DB2 for OS/390 and
z/OS administrator for help getting this information. Use one copy of the
example work sheet, Table 13, to plan each TCP/IP connection between DB2
Connect and a host database server.
Table 13. Example Worksheet for Planning TCP/IP Connections to DB2 Universal
Database for OS/390 and z/OS
Ref.
Description
Sample Value
Your Value
User Information
TCP-1
User name
A.D.B.User
TCP-2
Contact info
(123)-456-7890
TCP-5
User ID
ADBUSER
TCP-6
Database type
db2390
TCP-7
Connection type (must
be TCPIP).
TCPIP
Network Elements at the Host
76
TCP-8
Host name
MVSHOST
TCP-9
Host IP address
9.21.152.100
DB2 Connect EE Quick Beginnings
TCPIP
Table 13. Example Worksheet for Planning TCP/IP Connections to DB2 Universal
Database for OS/390 and z/OS (continued)
Ref.
Description
Sample Value
TCP-10
Service name
db2inst1c
TCP-11
Port number
446
TCP-12
LOCATION NAME
NEW_YORK3
TCP-13
User ID
TCP-14
Password
Your Value
446
Network Elements at the DB2 Connect Workstation
TCP-18
Host name
mcook02
TCP-19
IP address
9.21.27.179
TCP-20
Service name
db2inst1c
TCP-21
Port number
446
446
DB2 Directory Entries at the DB2 Connect Workstation)
TCP-30
Node name
MVSIPNOD
TCP-31
Database name
nyc3
TCP-32
Database alias
mvsipdb1
TCP-33
DCS database name
nyc3
Notes:
1. To obtain the host’s IP address TCP-9, enter at the host:
TSO NETSTAT HOME
2. To obtain the port number TCP-11, look for DSNL004I in the DB2 master address space or
system log.
Configuring the TCP/IP connection:
Use these steps in this section to complete the configuration and make the
connection.
Complete the worksheet:
Complete a copy of the example worksheet for each TCP/IP host:
1. Fill in the values to be used for the host name and IP address of the DB2
Universal Database for OS/390 and z/OS host (items 8 and 9).
2. Fill in the values to be used for the host name and IP address of the DB2
Connect workstation (items 18 and 19).
3. Determine the port number or service name to be used for the connection
(items 10 and 11, or 20 and 21).
4. Determine the LOCATION NAME of the DB2 for OS/390 and z/OS
database server to which you wish to connect.
Chapter 10. Preparing DB2 for OS/390 and z/OS databases for DB2 Connect communications
77
5. Determine the values to be used for user ID and PASSWORD when
connecting to the host database.
Update the DB2 Universal Database for OS/390 and z/OS host:
At
1.
2.
3.
your zSeries server:
Verify the host address or the host name.
Verify the port number or the service name.
Update the services file with the correct port number and service name if
necessary.
4. Update the hosts file (or the Domain Name Server used by the DB2
Universal Database for OS/390 and z/OS system) with the host name and
IP address of the DB2 Connect workstation if necessary.
5. Ensure the new definitions are active before attempting to test the
connection. Refer to your host network administrator or change control
staff if necessary.
6. Check with the DB2 Universal Database for OS/390 and z/OS
administrator that you have a valid user ID, password, and database
LOCATION NAME.
7. PING the DB2 Connect server, using the correct port number if that option
is supported by TCP/IP on the host system. For example:
ping remote_host_name -p port_number
Configuring VTAM
To configure VTAM, your VTAM Administrator needs to determine the names
and options to be used on your system. The following definitions must be
provided to enable the DB2 Connect workstation to connect to the host:
v The VTAM APPL definition for DB2 Universal Database for OS/390 and
z/OS. The APPL name, or LU name, for the DB2 subsystem is NYM2DB2 in
these examples.
v The VTAM PU and LU definitions for DB2 Connect. The PU and LU
definitions for the DB2 Connect workstation are NYX1 and NYX1GW01
respectively in these examples.
v The VTAM log mode definition for DB2. The log mode entry to be used for
the connection is IBMRDB in these examples.
The sample VTAM definitions are provided in the sections that follow. These
samples use parameters that match the parameters used elsewhere in this
book.
Sample Network Element Names (VTAM):
78
DB2 Connect EE Quick Beginnings
The following example shows the sample VTAM definitions used to configure
a host database server.
DB2 Connect Server:
- Network ID
- Local Node Name
- Local Node ID
- LU Name
HOST:
: SPIFNET
: NYX1
: 05D27509
(PU name)
- LU Alias
: SPIFNET.NYX1GW01
(the same LU is used
for DB2 Connect,
for DB2 Universal Database,
and for the SPM)
: NYX1GW01
- Network ID
- Node Name
: SPIFNET
: NYX
- LU Name
: SPIFNET.NYM2DB2
- LU Alias
: NYM2DB2
- LAN Destination Address : 400009451902 (NCP TIC address)
MODE DEFINITION:
- Mode Name
: IBMRDB
DB2 for OS/390:
- Location
: NEW_YORK3
SECURITY:
- Security Type
- Authentication Type
: Program
: DCS
Sample VTAM APPL Definition for OS/390 or z/OS:
The following example shows the sample VTAM application major node
definitions. In most cases, such a definition will already exist with a different
LU name. Otherwise, this application major node must be defined, and DB2
Universal Database for OS/390 and z/OS must be customized to use the LU
name defined. This name is the Partner LU name required by DB2 Connect.
Chapter 10. Preparing DB2 for OS/390 and z/OS databases for DB2 Connect communications
79
----+----1----+----2----+----3----+----4----+----5----+----6----+----7-DB2APPLS VBUILD TYPE=APPL
NYM2DB2
APPL
APPC=YES,
AUTH=(ACQ),
AUTOSES=1,
DLOGMOD=IBMRDB,
DMINWNL=512,
DMINWNR=512,
DSESSLIM=2048,
EAS=6000,
MODETAB=RDBMODES,
PARSESS=YES,
PRTCT=SFLU,
MODETAB=RDBMODES,
SECACPT=ALREADYV,
SRBEXIT=YES,
VERIFY=NONE,
VPACING=8
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Note: Continuations must begin in column 16, with continuation marks in
column 72.
Sample VTAM PU and LU Definitions for DB2 Connect:
If your security policies allow it, enable DYNPU and DYNLU in VTAM to allow
any PU and LU access through VTAM. Contact your VTAM administrator for
more information.
The following example shows the sample VTAM switched major node
definitions. Follow this example to enable a specific LU or PU.
If you already use SNA applications on the DB2 Connect workstation, then a
PU definition already exists. However, an independent LU definition might
not exist. The independent LU definition required for DB2 Connect must have
LOCADDR=0 specified.
80
DB2 Connect EE Quick Beginnings
----+----1----+----2----+----3----+----4----+----5----+----6----+----7-SWITCHED MAJOR NODE DEFINITION FOR PU NYX1 and
INDEPENDENT LU NYX1GW01
LOC300
NYX1
VBUILD TYPE=LOCAL
ADDR=01,IDBLK=071,IDNUM=27509,ANS=CONT,DISCNT=NO,
IRETRY=YES,ISTATUS=ACTIVE,MAXDATA=4302,MAXOUT=7,
MAXPATH=1,PUTYPE=2,SECNET=NO,MODETAB=RDBMODES
SSCPFM=USSSCS,PACING=0,VPACING=2
NYX1GW01
LOCADDR=000,MODETAB=RDBMODES,DLOGMODE=IBMRDB
OTHERLU
LOCADDR=002
X
X
X
Sample VTAM Log Mode Definition for DB2:
The following example shows the sample VTAM logon mode table definition
for the IBMRDB and SNASVCMG modes. This example specifies a 4K RUSIZE,
which may not be suitable for your environment, for example, if you are
using Ethernet, which has a maximum Frame Size of 1536 bytes. Your VTAM
administrator should check these values and advise you which mode table
entry name and RUSIZE to specify for DB2 Connect. You must define the
SNASVCMG logon mode when using APPC.
Chapter 10. Preparing DB2 for OS/390 and z/OS databases for DB2 Connect communications
81
----+----1----+----2----+----3----+----4----+----5----+----6----+----7--RDBMODES MODTAB
IBMRDB
82
MODEENT LOGMODE=IBMRDB,
DRDA DEFAULT MODE
TYPE=0,
NEGOTIABLE BIND
PSNDPAC=X’01’,
PRIMARY SEND PACING COUNT
SSNDPAC=X’01’,
SECONDARY SEND PACING COUNT
SRCVPAC=X’00’,
SECONDARY RECEIVE PACING COUNT
RUSIZES=X’8989’,
RUSIZES IN-4K
OUT-4K
FMPROF=X’13’,
LU6.2 FM PROFILE
TSPROF=X’07’,
LU6.2 TS PROFILE
PRIPROT=X’B0’,
LU6.2 PRIMARY PROTOCOLS
SECPROT=X’B0’,
LU6.2 SECONDARY PROTOCOLS
COMPROT=X’D0B1’,
LU6.2 COMMON PROTOCOLS
PSERVIC=X’060200000000000000122F00’
LU6.2 LU TYPE
*
*
*
*
*
*
*
*
*
*
*
SNASVCMG MODEENT LOGMODE=SNASVCMG, DRDA DEFAULT MODE
PSNDPAC=X’00’,
PRIMARY SEND PACING COUNT
SSNDPAC=X’02’,
SECONDARY SEND PACING COUNT
SRCVPAC=X’00’,
SECONDARY RECEIVE PACING COUNT
RUSIZES=X’8585’,
RUSIZES IN-1K
OUT-1K
FMPROF=X’13’,
LU6.2 FM PROFILE
TSPROF=X’07’,
LU6.2 TS PROFILE
PRIPROT=X’B0’,
LU6.2 PRIMARY PROTOCOLS
SECPROT=X’B0’,
LU6.2 SECONDARY PROTOCOLS
COMPROT=X’D0B1’,
LU6.2 COMMON PROTOCOLS
PSERVIC=X’060200000000000000000300’
LU6.2 LU TYPE
*
*
*
*
*
*
*
*
*
*
DB2 Connect EE Quick Beginnings
Chapter 11. Preparing DB2 UDB for iSeries databases for
DB2 Connect communications
Preparing DB2 Universal Database for iSeries for connections from DB2
Connect
DB2 Connect gives remote system applications access to data on your DB2
UDB for iSeries system.
Procedure:
To set up the connection, you need to know the following:
1. The local network name. You can get this information by entering DSPNETA.
2. The local adapter address. You can get this information by entering
WRKLIND (*trlan).
3. The mode name. You can get a list of mode names by entering WRKMODD. If
the mode IBMRDB has been defined on your iSeries system, you should
use it.
4. The local control point name. You can get this information by entering
DSPNETA.
5. The remote transaction program name. The default is X'07'6DB
(X'07F6C4C2'). The default is always used by DB2 UDB for iSeries. If
entering a hexadecimal number is not convenient, an alias is QCNTEDDM.
6. The relational database name. You can get this information by entering
DSPRDBDIRE. This will display a list. The line containing *LOCAL in the
Remote Location column identifies the RDBNAME which must be defined
to the client. If there is no *LOCAL entry, you can add one, or use the
system name obtained from the DSPNETA command on the server.
Here is an example:
Table 14. Display Relational Database Directory Entries
Display Relational Database Directory Entries
Position to . . . . . .
Type options, press Enter.
5=Display details
6=Print details
Option
_
© Copyright IBM Corp. 1993-2002
Relational
Remote
Database
Location Text
____________________
83
Table 14. Display Relational Database Directory Entries (continued)
_
DLHX
RCHAS2FA
_
JORMT2FA
JORMT2FA
_
JORMT4FD
JORMT4FD
_
JOSNAR7B
RCHASR7B
_
RCHASR7B
*LOCAL
_
RCHASR7C
RCHASR7C
_
R7BDH3SNA
RCH2PDH3
_
RCHASDH3
RCHASDH3
When you have obtained these parameters from your iSeries server, enter
your values into the worksheet that follows:
Table 15. Configuration parameters from iSeries
Item Parameter
Example
A-1 Local network name
SPIFNET
A-2 Local adapter address
400009451902
A-3 Mode name
IBMRDB
A-4 Local control point name
SYD2101A
A-5 Remote transaction program
X'07F6C4C2'(default)
A-6 Relational database name
NEW_YORK3
Your value
For more information, refer to the DRDA Connectivity Guide.
84
DB2 Connect EE Quick Beginnings
Chapter 12. Preparing DB2 for VM & VSE databases for
DB2 Connect communications
Preparing DB2 for VSE & VM for connections from DB2 Connect
For information about how to set up DB2 for VSE & VM as an application
server, refer to the DRDA Connectivity Guide.
Related concepts:
v “DB2 for VM” in the Connectivity Supplement
v “DB2 for VSE” in the Connectivity Supplement
Related tasks:
v “Preparing the application requester or application server for DRDA
communications (VM)” in the Connectivity Supplement
© Copyright IBM Corp. 1993-2002
85
86
DB2 Connect EE Quick Beginnings
Part 4. Configuring access to host and iSeries
databases
After DB2 Connect is installed and the database server is configured to accept
communications, you need to establish and fine-tune the connection between
the two systems. This section describes how to use the Configuration
Assistant (CA) to find, connect, and bind to a database server.
Who Should Read This Section
v Network or system administrators
v Technical personnel installing and configuring a DB2 Connect system
© Copyright IBM Corp. 1993-2002
87
88
DB2 Connect EE Quick Beginnings
Chapter 13. Using the Configuration Assistant
Configuring a connection to host or iSeries database servers using the CA
This task describes how to connect DB2 Connect Personal Edition (PE) or DB2
Connect Enterprise Edition to a remote database host or iSeries database
server using the Configuration Assistant (CA). The Configuration Assistant is
a DB2 GUI tool that can be used to configure database connections and other
database settings.
The Configuration Assistant (CA) was referred to as the Client Configuration
Assistant (CCA) in previous releases of DB2.
Prerequisites:
v The Configuration Assistant must be installed on DB2 Connect workstation.
In DB2 version 8, the Configuration Assistant is available as part of the DB2
Administration Client and DB2 Application Development Client.
v The remote server must be configured to accept inbound client requests. By
default, the server installation program detects and configures most
protocols on the server for inbound client connections.
Procedure:
To configure a connection to a database using the CA, select one of the
following methods:
v Connecting to a database using discovery
v Connecting to a database using a profile
v Connecting to a database manually using the CA
Related tasks:
v “Configuring a database connection using Discovery” on page 90
v “Configuring a database connection using a profile” on page 91
v “Configuring a database connection using the Configuration Assistant
(CA)” on page 92
© Copyright IBM Corp. 1993-2002
89
Configuration tasks
Configuring a database connection using Discovery
You can use the Discovery feature of the Configuration Assistant to search a
network for databases.
Prerequisites:
Before you configure a connection to a database using Discovery:
v Ensure that you have a valid DB2 user ID.
v If adding a database to a system that has a DB2 Server or DB2 Connect
server product installed, ensure that you have a user ID with SYSADM or
SYSCTRL authority for the instance.
Restrictions:
A DB2 Administration Server (DAS) must be running and enabled for the
Discovery feature of the CA to return information about DB2 systems.
Procedure:
To add a database to your system using Discovery:
1. Log on to the system with a valid DB2 user ID.
2. Start the CA. The CA can be started from the Start menu on Windows or
using the db2ca command on both Windows and UNIX systems.
3. On the CA menu bar, under Selected, choose Add a database using
wizard.
4. Select the Search the network radio button and click Next.
5. Double-click on the folder beside Known Systems to list all the systems
known to your client.
6. Click the [+] sign beside a system to get a list of the instances and
databases on it. Select the database that you want to add, click the Next
push button,
7. Enter a local database alias name in the Database alias field and
optionally enter a comment that describes this database in the Comment
field.
8. If you are planning to use ODBC, register this database as an ODBC data
source. ODBC must be installed to perform this operation.
9. Click Finish. You are now able to use the database you added. Click Close
to exit the CA.
Related tasks:
90
DB2 Connect EE Quick Beginnings
v “Configuring a database connection using the Configuration Assistant
(CA)” on page 92
v “Configuring a database connection using a profile” on page 91
v “Testing a database connection” on page 93
Configuring a database connection using a profile
A server profile contains information about server instances on a system, and
databases within each server instance. A client profile contains database
information that was cataloged on another client system. Use the steps in the
following task to connect to a database using a profile.
Prerequisites:
Before you connect to a database through the CA using a profile:
v Ensure that you have a valid DB2 user ID.
v If adding a database to a system that has a DB2 Server or DB2 Connect
server product installed, ensure that you have a user ID with SYSADM or
SYSCTRL authority for the instance.
Procedure:
To connect to a database using a profile:
1. Log on to the system with a valid DB2 user ID.
2. Start the CA. The CA can be started from the Start menu on Windows or
using the db2ca command on both Windows and UNIX systems.
3. On the CA menu bar, under Selected, choose Add a database using
wizard.
4. Select the Use a profile radio button and click Next.
5. Click the ... push button and select a profile. Select a remote database from
the object tree that is displayed from the profile, and if the database
selected is a gateway connection, select a connection route to the database.
Click the Next push button.
6. Enter a local database alias name in the Database alias field and
optionally enter a comment that describes this database in the Comment
field. Click Next.
7. If you are planning to use ODBC, register this database as an ODBC data
source. ODBC must be installed to perform this operation.
8. Click Finish. You are now able to use this database. Select the Exit menu
action to exit the CA.
Related tasks:
Chapter 13. Using the Configuration Assistant
91
v “Creating client profiles using the export function of the Configuration
Assistant (CA)” on page 131
v “Testing a database connection” on page 93
Configuring a database connection using the Configuration Assistant
(CA)
If you have the information for the database you want to connect to and the
server upon which it resides, you can manually enter all of the configuration
information. This method is analogous to entering commands via the
command line processor, however, the parameters are presented graphically.
Prerequisites:
Before you configure a connection to a database using the CA:
v Ensure that you have a valid DB2 user ID.
v If adding a database to a system that has a DB2 Server or DB2 Connect
server product installed, ensure that you have a user ID with SYSADM or
SYSCTRL authority for the instance.
Procedure:
To add a database to your system manually using the CA:
1. Log on to the system with a valid DB2 user ID.
2. Start the CA. The CA can be started from the Start menu on Windows or
using the db2ca command on both Windows and UNIX systems.
3. On the CA menu bar, under Selected, choose Add a database using
wizard.
4. Select the Manually configure a connection to a database radio button
and click Next.
5. If you are using Lightweight Directory Access Protocol (LDAP), select the
radio button that corresponds to the location where you would like your
DB2 directories to be maintained. Click Next.
6. Select the radio button that corresponds to the protocol that you want to
use from the Protocol list.
If DB2 Connect is installed on your machine and you select TCP/IP or
APPC, you have the option to select The database physically resides on
a host or OS/400 system. If you select this check box, you will have the
option of selecting the type of connection that you want to make to the
host or OS/400 database:
v To make a connection through a DB2 Connect gateway, select the
Connect to the server via the gateway radio button.
92
DB2 Connect EE Quick Beginnings
v To make a direct connection, select the Connect directly to the server
radio button.
Click Next.
7. Enter the required communication protocol parameters and click Next.
8. Enter the database alias name of the remote database that you want to
add in the Database name field and a local database alias name in the
Database alias field.
If you are adding a host or OS/400 database, type the Location name for
an OS/390 or z/OS database, the RDB name for an OS/400 database, or
the DBNAME for a VSE or VM database in the Database name field.
Optionally add a comment that describes this database in the Comment
field.
Click Next.
9. If you are planning to use ODBC, register this database as an ODBC data
source. ODBC must be installed to perform this operation.
10. Click Finish. You are now able to use this database. Select the Exit menu
action to close the CA.
Related tasks:
v “Configuring a database connection using Discovery” on page 90
v “Configuring a database connection using a profile” on page 91
v “Testing a database connection” on page 93
Testing a database connection
After configuring the database, the database connection should be tested.
Procedure:
To test a database connection:
1. Start the CA.
2. Highlight the database in the details view and invoke the Test Connection
menu action. The Test Connection window opens.
3. Select the type of connection that you would like to test (CLI is the
default). Enter a valid user ID and password for the remote database and
click Test Connection. If the connection is successful, a message
confirming the connection appears on the Results page.
If the connection test failed, you will receive a help message. To change
any settings you may have incorrectly specified, select the database in the
details view and invoke the Change Database menu action.
Related tasks:
Chapter 13. Using the Configuration Assistant
93
v “Configuring a database connection using Discovery” on page 90
v “Configuring a database connection using the Configuration Assistant
(CA)” on page 92
v “Configuring a database connection using a profile” on page 91
94
DB2 Connect EE Quick Beginnings
Chapter 14. Multisite update
Multisite Updates
Multisite update, also known as distributed unit of work (DUOW) and
two-phase commit, is a function that enables your applications to update data
in multiple remote database servers with guaranteed integrity. For example, a
banking transaction that involves the transfer of money from one account to
another in a different database server.
In such a transaction, it is critical that updates which implement debit
operations on one account do not get committed unless updates required to
process credits to the other account are committed as well. The multisite
update considerations apply when data representing these accounts is
managed by two different database servers.
DB2® products provide comprehensive support for multisite updates. This
support is available for applications developed using regular SQL as well as
applications that use transaction processing monitors (TP monitors) that
implement the X/Open XA interface specification. Examples of such TP
monitors products include IBM® TxSeries (CICS and Encina), IBM Message
and Queuing Series, IBM Component Broker Series, IBM San Francisco Project
as well as Microsoft® Transaction Server (MTS), BEA Tuxedo and several
others. There are different setup requirements depending on whether native
SQL multisite update or TP monitor multisite update is used.
Both the native SQL and TP monitor multisite update programs must be
precompiled with the CONNECT 2 SYNCPOINT TWOPHASE options. Both can use
the SQL Connect statement to indicate which database they want to be used
for the SQL statements that follow. If there is no TP monitor to tell DB2 it is
going to coordinate the transaction (as indicated by DB2 receiving the xa_open
calls from the TP monitor to establish a database connection), then the DB2
software will be used to coordinate the transaction.
When using TP monitor multisite update, the application must request
commit or rollback by using the TP monitor’s API, for example CICS®
SYNCPOINT, Encina® Abort(), MTS SetAbort(). When using native SQL
multisite update, the normal SQL COMMIT and ROLLBACK must be used.
TP monitor multisite update can coordinate a transaction that accesses both
DB2 and non-DB2 resource managers such as Oracle, Informix™ or SQLServer.
Native SQL multisite update is used with DB2 servers only.
© Copyright IBM Corp. 1993-2002
95
For a multisite update transaction to work, each of the databases participating
in a distributed transaction must be capable of supporting distributed unit of
work. Currently, the following DB2 servers provided DUOW support that
enabled them to participate in distributed transactions:
v DB2 UDB for UNIX® and Windows® Version 5 or later
v DB2 for OS/390® Version 5.1
v DB2 UDB for OS/390 Version 6.1 or later
v DB2 for z/OS™ Version 7
v DB2 UDB for iSeries™ Version 4 or later
v DB2 Server for VM and VSE V5.1 or later (SNA only)
A distributed transaction can update any mix of supported database servers.
For example, your application can update several tables in DB2 UDB on
Windows NT or Windows 2000, a DB2 for OS/390 and z/OS database, and a
DB2 UDB for iSeries database, all within a single transaction.
Related concepts:
v “Remote unit of work” in the DB2 Connect User’s Guide
v “Distributed requests” in the DB2 Connect User’s Guide
v “Multisite update and sync point manager” on page 98
Related tasks:
v “Enabling Multisite Updates using the Control Center” on page 96
v “Testing Multisite Update using the Control Center” on page 97
Enabling Multisite Updates using the Control Center
You can use the Control Center to provide multisite updates.
Procedure:
To
1.
2.
3.
enable multistie updates:
Launch the Multisite Update Wizard. From the Control Center.
Click the [+] sign to expand the tree view.
With the right mouse button, select the instance that you wish to
configure. A pop-up menu opens.
4. Select Multisite Update —> Configure menu item.
5. The Multisite Update Wizard provides a notebook-type interface. Each
page of the wizard will prompt you for certain information about your
configuration.
96
DB2 Connect EE Quick Beginnings
a. Specify a Transaction Processor (TP) monitor. This field will show the
defaults for the TP monitor you have enabled. If you do not want to
use a TP monitor, select Do Not Use a TP Monitor. Click Next.
b. Specify the communications protocols you will use. Click Next.
c. Specify a Transaction Manager database. This panel defaults to the first
database you connect to (1ST_CONN). You can leave this default or
select another catalogued database. Click Next.
d. Specify the types of database servers involved in the update, and also
whether or not TCP/IP is to be used exclusively.
e. Specify the sync point manager settings. This page will only appear if
the settings on the previous page indicate that you need to use DB2’s
sync point manager in a multisite update scenario.
Related concepts:
v “Multisite Updates” on page 95
Related tasks:
v “Testing Multisite Update using the Control Center” on page 97
Testing Multisite Update using the Control Center
You can test your multisite update setup using the Control center.
Procedure:
To test multisite update:
1. Select the instance with the right mouse button and choose the Multisite
Update —> Test menu option from the pop-up menu. The Test Multisite
Update window opens.
2. Select the databases you want to test from the available databases in the
Available Databases list box. You can use the arrow buttons (> and >>) in
the middle to move selections to and from the Selected databases list box.
You can also change the selected userid and password by directly editing
them in the Selected databases list box.
3. When you have finished your selection, click OK. The Multisite Update
Test Result window opens.
4. The Multisite Update Test Result window shows which of the databases
you selected succeeded or failed the update test. The window will show
SQL codes and error messages for those that failed. Click Close to close
the window.
5. Click Close to close the Test Multisite Update window.
Chapter 14. Multisite update
97
Related concepts:
v “Multisite Updates” on page 95
Related tasks:
v “Enabling Multisite Updates using the Control Center” on page 96
Multisite update and sync point manager
Host and iSeries™ database servers require DB2® Connect to participate in a
distributed transaction originating from Windows, UNIX, and web
applications. In addition, many of the multisite update scenarios that involve
host and iSeries database servers require that the sync point manager (SPM)
component be configured. When a DB2 instance is created, the DB2 SPM is
automatically configured with default settings.
The need for SPM is dictated by the choice of protocol (SNA or TCP/IP) and
use of a TP monitor. The following table provides a summary of scenarios that
require the use of SPM. The table also shows if DB2 Connect™ is required for
any access to the host or iSeries from Intel or UNIX® machines. For multisite
updates, the SPM component of DB2 Connect is required if the access is via
SNA or if you are using a TP monitor.
Table 16. Multisite update scenarios that require SPM – TCP/IP
Transaction
Processor Monitor
Used?
Sync Point
Manager Needed?
Product Required
(Choose One)
Host and iSeries
Database
Supported
Yes
Yes
v DB2 Connect EE
v DB2 for OS/390®
V5.1
v DB2 UDB ESE
v DB2 UDB for
OS/390 V6.1 or
later
v DB2 UDB for
z/OS™ V7 or
later
No
No
v DB2 Connect PE
v DB2 Connect EE
v DB2 UDB ESE
v DB2 for OS/390
V5.1
v DB2 UDB for
OS/390 V6.1 or
later
v DB2 UDB for
z/OS V7 or later
98
DB2 Connect EE Quick Beginnings
Table 17. Multisite update scenarios that require SPM – SNA
Transaction
Processor Monitor
Used?
Sync Point
Manager Needed?
Product Required
(Choose One)
Host and iSeries
Database
Supported
Yes
Yes
v DB2 Connect EE*
v DB2 for OS/390
V5.1
v DB2 UDB ESE*
Note: *AIX,
Windows® NT, and
Windows 2000
platforms only.
v DB2 UDB for
OS/390 V6.1 or
later
v DB2 UDB for
z/OS V7 or later
v DB2 for AS/400®
V3.1 or later
v DB2 UDB for
iSeries V4 or later
v DB2 Server for
VM or VSE V5.1
or later
No
Yes
v DB2 Connect EE*
v DB2 UDB ESE*
Note: *AIX,
Windows NT, and
Windows 2000
platforms only.
v DB2 for OS/390
V5.1
v DB2 UDB for
OS/390 V6.1 or
later
v DB2 UDB for
z/OS V7
v DB2 for AS/400
V3.1 or later
v DB2 UDB for
iSeries V4 or later
v DB2 Server for
VM and VSE
V5.1 or later
Note: A distributed transaction can update any mix of supported database
servers. For example, your application can update several tables in DB2
UDB on Windows, a DB2 for OS/390 database and a DB2 UDB for
iSeries database all within a single transaction.
Related concepts:
v “Multisite Updates” on page 95
Chapter 14. Multisite update
99
100
DB2 Connect EE Quick Beginnings
Chapter 15. DB2 Connect Sysplex support
DB2 Connect Sysplex support
A Sysplex is a collection of zSeries™ servers that cooperate, using hardware
and software, to process work. The Sysplex coordinates the cooperation by
increasing the number of processors working together, which increases the
amount of work that can be processed. In addition to an increase in
processing capability, a Sysplex can provide flexibility in mixing levels of
hardware and software, and in dynamically adding systems.
Sysplex permits DB2 Connect to seamlessly transfer an incoming connection
from one remote database server to a designated backup server in the event
that the first server fails. DB2 Connect support for Sysplex is enabled by
default, however each DCS database catalog entry must be configured to
enable Sysplex support.
Note: If the DB2 Connect concentrator is not active, then active connections
are not transferred between hosts in the event of server failure; if a
server fails all existing connections to that server are lost. If the
concentrator is active, then only connections with in-flight transactions
to the particular Sysplex member that goes down will be lost. Other
connections will be maintained and the next transaction will be sent to
a remaining member.
Related concepts:
v “Configuration requirements for Sysplex” on page 103
v “Considerations for S/390 and zSeries SYSPLEX exploitation” on page 101
v “DB2 Sysplex exploitation” on page 104
Considerations for S/390 and zSeries SYSPLEX exploitation
DB2 Connect Enterprise Edition servers provide load balancing and
fault-tolerance when routing connections to multiple Sysplexes. When
connected to a DB2® for OS/390® and z/OS™ database server running in a
data sharing environment, DB2 Connect will spread the workload amongst
the different DB2 subsystems comprising the data sharing group, based on the
system load information provided by the Workload Manager (WLM). This
support requires DB2 for OS/390 Version 6 or later.
© Copyright IBM Corp. 1993-2002
101
DB2 Connect™ receives a prioritized list of Sysplex members from the WLM.
Each Sysplex returns weighted priority information for each connection
address. This list is then used by the DB2 Connect server to handle the
incoming CONNECT requests by distributing them among the Sysplex
members with the highest assigned priorities. For load balancing, the list of
Sysplex weighted priority information is obtained during each connection. If
the DB2 Connect connection concentrator is enabled, this list is also used
when determining where to send each transaction.
Note: OS/390 and z/OS DDF configuration does not need to be changed to
take advantage of the DB2 Connect Sysplex exploitation.
DB2 Connect Enterprise Edition servers also provide fault-tolerance by
attempting to connect to an alternate sysplex machine in the event of a
connection failure. An error will only be returned to the application if all
known connections have failed. Since for SNA addresses there is no
equivalent to Domain Name Server (DNS) lookup, to ensure that a connection
can be made the first time after a db2start, DB2 Connect writes the addresses
returned for SNA to the file db2con.ini, and this file is read on db2start. This
provides a means to recover if the cataloged node is down.
In the event of failure to connect to a particular SNA address, the following
message is written to the administration notification log:
DIA4805E A connection cannot be established to the DRDA® application server
at SNA address "%1" due to unknown symbolic destination name "%2".
A new profile (or registry) variable DB2SYSPLEX_SERVER has been created to
enable this feature. If DB2SYSPLEX_SERVER is not present or is set to a non-zero
value, then Sysplex exploitation is enabled. If DB2SYSPLEX_SERVER is set to zero,
then Sysplex exploitation is disabled. Setting DB2SYSPLEX_SERVER to a value of
zero disables the Sysplex exploitation for the server regardless of how the
DCS database catalog entry has been specified.
The db2 registry variable DB2CONNECT_IN_APP_PROCESS can be used to allow
clients running on the same machine as the DB2 Connect Enterprise Edition
server to exploit the Sysplex support.
With the addition of the concentrator, DB2 Connect now has the ability to
balance the workload at transaction boundaries. The DB2 Connect
concentrator must be enabled for this to work. Depending on the version of
DB2 on the host, different granularity of load balancing will be achieved. If
load balancing is running against DB2 for OS/390 Version 6.1 or later, DB2
Connect will receive updated status from the WLM on each transaction.
However, long running connections can be used with OS/390 Version 6.1 and
Sysplex support.
102
DB2 Connect EE Quick Beginnings
Related concepts:
v “DB2 Connect Sysplex support” on page 101
v “Configuration requirements for Sysplex” on page 103
v “DB2 Sysplex exploitation” on page 104
Configuration requirements for Sysplex
v On a DB2 Connect Enterprise Edition server, Sysplex exploitation is enabled
by default, but it can be turned off by setting the DB2SYSPLEX_SERVER profile
variable to the value zero.
v Sysplex exploitation will not be used for a given database unless the DCS
directory entry for that database contains Sysplex (not case-sensitive) in the
6th positional parameter.
v For APPC connections, these additional considerations apply:
1. A Partner LU definition must exist for each LU that is a DB2® for
OS/390® and z/OS™ participant in the Sysplex.
2. Matching CPIC symbolic destination name profiles must be defined for
each participant, each having the same name as the related LU.
Therefore, in this scenario, the SNA subsystem that the DB2 Connect server
uses must contain a Partner LU profile for NETB.LUB and NETC.LUC
referenced from a CPIC symbolic destination profile called LUB and LUC
respectively.
v For the scenario described below, only the primary DB2 for OS/390 and
z/OS database (LOCATION_NAME_B) need be defined in the catalog on the
DB2 Connect server, as follows:
db2 catalog appc node nodeb remote lub security program
db2 catalog dcs database dbb as location_name_b parms ’,,,,,sysplex’
db2 catalog database dbb as aliasb at node nodeb authentication dcs
No DB2 directory entries need be defined in the catalog on the DB2
Connect server to reach the database LOCATION_NAME_C, since it is a
secondary participant in the Sysplex. However, the symbolic destination
name luc must reference the Partner LU definition for NETB.LUC since an
APPC connection is being used.
Related concepts:
v “DB2 Connect Sysplex support” on page 101
v “Considerations for S/390 and zSeries SYSPLEX exploitation” on page 101
v “DB2 Sysplex exploitation” on page 104
Chapter 15. DB2 Connect Sysplex support
103
DB2 Sysplex exploitation
In a typical scenario, the DB2 Connect Enterprise Edition server machine A
would be in conversation with a Sysplex containing two DB2® for OS/390®
and z/OS™ servers, say machines B and C:
Sysplex machine B
Sysplex machine C
LOCATION_NAME_B
LOCATION_NAME_C
LU Address=NETB.LUB
LU Address=NETC.LUC
Suppose that in this scenario an application now issues:
db2 connect to aliasb user xxxxxxx using xxxxxxxx
The connection to database LOCATION_NAME_B is established. Because Sysplex
exploitation is enabled both for the DB2 Connect server and the DCS directory
entry, DB2 for OS/390 and z/OS identifies the network addresses to DB2
Connect for each Sysplex participant (NETB.LUB and NETC.LUC. DRDA4
protocols and message flows are used to return this information). Once an
initial connection has been made, the returned list of addresses is cached at
the DB2 Connect server. The list is either a list of SNA LU names (as in this
example), or a list of IP addresses. The list cannot contain a mixture of these
address types. For example, if the initial CONNECT is issued for an APPC node,
only SNA addresses are returned, and if the initial CONNECT is issued for a
TCP/IP node, then only IP addresses are returned.
Priority information used for load balancing and fault tolerance:
The list of addresses provided by DB2 for OS/390 and z/OS also includes
priority information, including the number of connections for each network
address. The list is refreshed whenever a new connection is made by DB2
Connect. This additional information is used for load balancing purposes, as
well as for fault tolerance.
Cached Address List used by DB2 Connect:
If the database connection to ALIASB fails, then an error message SQL30081N
is issued, and the connection will be dropped. If a further connection request
is received for ALIASB, DB2 Connect does the following:
1. It tries the highest priority machine from the cached list of addresses
based on the priority information that was returned by DB2 for OS/390
and z/OS. This strategy is always used by DB2 Connect, and it is by this
means that load balancing is achieved.
104
DB2 Connect EE Quick Beginnings
2. If this connection attempt fails, then the other addresses in the list are
tried, in descending order of priority, as returned by DB2 for OS/390 and
z/OS. This is how DB2 Connect exploits the Sysplex information to
achieve fault tolerance.
3. If all other attempts to connect fail, then DB2 Connect will retry the
connection to ALIASB using the address contained in the cataloged node
directory.
Related concepts:
v “DB2 Connect Sysplex support” on page 101
v “Configuration requirements for Sysplex” on page 103
v “Considerations for S/390 and zSeries SYSPLEX exploitation” on page 101
Chapter 15. DB2 Connect Sysplex support
105
106
DB2 Connect EE Quick Beginnings
Part 5. Installing and configuring clients
Your client applications must be properly configured so that they can
communicate with host– or iSeries-based databases through DB2 Connect.
This section shows how to install your DB2 client software and configure it to
use DB2 Connect.
Who Should Read This Section
v Network or system administrators
v Anyone wishing to use a DB2 database client on a PC
© Copyright IBM Corp. 1993-2002
107
108
DB2 Connect EE Quick Beginnings
Chapter 16. DB2 client concepts
DB2 clients
There are three types of DB2® clients:
v Run-Time Client
v Administration Client
v Application Development Client
DB2 clients can connect to DB2 servers two releases later or one release earlier
than the client’s release level, as well as to servers at the same release level.
This means that a DB2 Version 6 client can connect to DB2 servers at versions
5, 6, 7, and 8.
A database cannot be created on a DB2 client. You must access databases that
reside on a DB2 server.
Related concepts:
v “DB2 Run-Time Client” on page 110
v “DB2 Administration Client” on page 109
v “DB2 Application Development Client” on page 110
Related tasks:
v “Installing a DB2 client on Windows operating systems” on page 120
v “Installing DB2 clients on UNIX” on page 122
DB2 Administration Client
A DB2® Administration Client provides the ability for workstations from a
variety of platforms to access and administer DB2 databases. The DB2
Administration Client has all the features of the DB2 Run-Time Client and
also includes all the DB2 administration tools and support for Thin Clients.
DB2 Administration Clients are available for the following platforms: AIX,
HP-UX, Linux, the Solaris Operating Environment, and Windows® operating
systems.
Related concepts:
v “DB2 clients” on page 109
v “DB2 Run-Time Client” on page 110
© Copyright IBM Corp. 1993-2002
109
v “DB2 Application Development Client” on page 110
Related tasks:
v “Installing a DB2 client on Windows operating systems” on page 120
v “Installing DB2 clients on UNIX” on page 122
DB2 Application Development Client
The DB2® Application Development Client is a collection of graphical and
non-graphical tools and components for developing character-based,
multimedia, and object-oriented applications. Special features include the
Development Center and sample applications for all supported programming
languages. The Application Development Client also includes the tools and
components provided as part of the DB2 Administration Client product.
DB2 Application Development clients are available for the following
platforms: AIX, HP-UX, Linux, the Solaris Operating Environment, and
Windows® operating systems.
Related concepts:
v “DB2 clients” on page 109
v “DB2 Run-Time Client” on page 110
v “DB2 Administration Client” on page 109
Related tasks:
v “Installing a DB2 client on Windows operating systems” on page 120
v “Installing DB2 clients on UNIX” on page 122
DB2 Run-Time Client
The DB2® Run-Time Client is a light-weight client that provides the
functionality required for an application to access DB2 Universal Database™
servers and DB2 Connect servers. Functionality includes communication
protocol support and support for application interfaces such as JDBC, SQLj,
ODBC, CLI, and OLE DB. As a result of the removal of most of the previous
Run-Time Client GUI facilities, the Version 8 Run-Time Client now has
diminished disk requirements.
Note: The Configuration Assistant is not packaged with the Windows®
Run-Time Client. The only available GUI is the CLI/ODBC
administration GUI.
110
DB2 Connect EE Quick Beginnings
DB2 Run-Time Clients are available for the following platforms: AIX, HP-UX,
Linux, the Solaris Operating Environment, and Windows operating systems.
Related concepts:
v “DB2 clients” on page 109
v “DB2 Administration Client” on page 109
v “DB2 Application Development Client” on page 110
Related tasks:
v “Installing a DB2 client on Windows operating systems” on page 120
v “Installing DB2 clients on UNIX” on page 122
Chapter 16. DB2 client concepts
111
112
DB2 Connect EE Quick Beginnings
Chapter 17. Installing clients
Client installation requirements
Installation requirements for DB2 clients (Windows)
The following list provides operating system requirements, software
requirements, and communication requirements for your DB2 client on
Windows.
Operating system requirements
One of the following:
v
v
v
v
Windows 98
Windows ME
Windows NT Version 4.0 with Service Pack 6a or later
Windows NT Server 4.0, Terminal Server Edition (only supports the
DB2 Run-Time Client) with Service Pack 6 or later for Terminal
Server
v Windows 2000
v Windows XP (32-bit and 64-bit editions)
v Windows .NET servers (32-bit and 64-bit editions)
Software requirements
v The Java Runtime Environment (JRE) Version 1.3.1 is required to
run DB2 graphical tools, such as the Control Center. If the JRE is
not already installed, it will be installed for use by DB2. The DB2
JAVA GUI tools are not provided with the DB2 Version 8 Run-Time
Client.
v If you plan to use LDAP (Lightweight Directory Access Protocol),
you require either a Microsoft LDAP client or an IBM SecureWay
LDAP client V3.1.1 or later. Microsoft LDAP client is included with
the operating system for Windows ME, Windows 2000, Windows
XP, and Windows .NET.
v If you plan to use the Tivoli Storage Manager facilities for backup
and restore of your databases, you require the Tivoli Storage
Manager Client Version 3 or later.
v If you have the IBM Antivirus program installed on your operating
system, it must be disabled or uninstalled to complete a DB2
installation.
Communication requirements
© Copyright IBM Corp. 1993-2002
113
v Named Pipes, NetBIOS, or TCP/IP.
v The Windows base operating system provides Named Pipes,
NetBIOS, and TCP/IP connectivity.
v For APPC connectivity on Windows 32-bit systems, you require one
of the following products:
– IBM eNetwork Communications Server for Windows Version
6.1.1 or later.
– Windows 2000: IBM eNetwork Personal Communications for
Windows Version 5.0 CSD3 or later.
– Windows XP: IBM eNetwork Personal Communications for
Windows Version 5.5 (plus APAR IC32490 required for all
language versions, and APAR IC32539 required for Korean
version only) The APARs are now available and can be accessed
using the Product Update Tool available in the IBM eNetwork
Personal Communications product.
– Windows NT: IBM eNetwork Personal Communications for
Windows Version 5.0 CSD3 or later.
– Microsoft SNA Server Version 3 Service Pack 3 or later.
– Wall Data Rumba.
Note: APPC will not be supported on Windows 64-bit operating
systems.
Related concepts:
v “DB2 clients” on page 109
v “DB2 Run-Time Client” on page 110
v “DB2 Administration Client” on page 109
v “DB2 Application Development Client” on page 110
Related tasks:
v “Installing a DB2 client on Windows operating systems” on page 120
Related reference:
v “Memory requirements for DB2 clients” on page 120
v “Disk requirements for DB2 clients” on page 119
Installation requirements for DB2 clients (AIX)
The following list provides hardware requirements, operating system
requirements, software requirements, and communication requirements for
your DB2 client on AIX.
114
DB2 Connect EE Quick Beginnings
Hardware requirements
RISC System/6000
Operating system requirements
AIX Version 4.3.3.78 or later
Software requirements
v For LDAP (Lightweight Directory Access Protocol) support, you
require an IBM SecureWay Directory Client V3.1.1 running on AIX
V4.3.3.78 or later.
v The Java Runtime Environment (JRE) Version 1.3.1 is required to
run DB2 graphical tools, such as the Control Center. The DB2 JAVA
GUI tools are not provided with the DB2 Version 8 Run-Time
Client.
v If you are installing the Application Development Client you may
require the Java Developer’s Kit. During the installation process, if
the JDK is not already installed, it will be installed. The same is
applicable for JRE.
Communication requirements
v APPC or TCP/IP
v For APPC connectivity, you require IBM eNetwork Communications
Server Version 6.1 for AIX.
v The AIX base operating system provides TCP/IP connectivity, if
selected during install.
Related concepts:
v “DB2 clients” on page 109
v “DB2 Run-Time Client” on page 110
v “DB2 Administration Client” on page 109
v “DB2 Application Development Client” on page 110
Related tasks:
v “Installing DB2 clients on UNIX” on page 122
Related reference:
v “Memory requirements for DB2 clients” on page 120
v “Disk requirements for DB2 clients” on page 119
Installation requirements for DB2 clients (HP-UX)
The following list provides hardware requirements, operating system
requirements, software requirements, and communication requirements for
your DB2 client on HP-UX.
Chapter 17. Installing clients
115
Restrictions:
A system reboot is required if the kernel configuration parameters have been
updated. The kernel configuration parameters are set in /etc/system and if
these parameters require modification to accommodate the DB2 client, a
reboot will be necessary to make the changes to /etc/system effective.
Note: The parameters must be set in advance of the DB2 client install.
Hardware requirements
HP 9000 Series 700 or 800 system
Operating system requirements
v HP-UX 11.0 32-bit with general release bundle + PHSS-24303
v HP-UX 11.0 64-bit with general release bundle + PHSS-24303
v HP-UX 11i 32-bit with June 2001 general release bundle
v HP-UX 11i 64-bit with June 2001 general release bundle
Software requirements
v The Java Runtime Environment (JRE) Version 1.3.1 is required to
run DB2 graphical tools, such as the Control Center. The DB2 JAVA
GUI tools are not provided with the DB2 Version 8 Run-Time
Client.
v If you are installing the Application Development Client you may
require the Java Developer’s Kit. During the installation process, if
the JDK is not already installed, it will be installed. The same is
applicable for JRE.
Communication requirements
v APPC or TCP/IP
v TCP/IP is provided with the HP-UX base operating system.
v For APPC connectivity, you require both SNAPlus2 Link R6.11.00.00
and SNAPlus2 API R6.11.00.00
Related tasks:
v “Modifying kernel parameters (HP-UX)” in the Quick Beginnings for DB2
Servers
Installation requirements for DB2 clients (Linux)
The following list provides operating system requirements, software
requirements, and communication requirements for your DB2 client on Linux.
Restrictions:
116
DB2 Connect EE Quick Beginnings
A system reboot is required if the kernel configuration parameters have been
updated. The kernel configuration parameters are set in /etc/system and if
these parameters require modification to accommodate the DB2 client, a
reboot will be necessary to make the changes to /etc/system effective.
Note: The parameters must be set in advance of the DB2 client install.
Operating system requirements
For Intel 32–bit architecture you require:
v kernel level 2.4.9 or higher
v glibc 2.2.4
For Intel 64–bit architecture you require one of the following:
v Red Hat Linux 7.2; OR
v SuSE Linux SLES-7
For z-Series architecture you require one of the following:
v Red Hat Linux 7.2; OR
v SuSE Linux SLES-7
Software requirements
v The Java Runtime Environment (JRE) Version 1.3.1 is required to
run DB2 graphical tools, such as the Control Center. The DB2 JAVA
GUI tools are not provided with the DB2 Version 8 Run-Time
Client.
v If you are installing the Application Development Client you may
require the Java Developer’s Kit. During the installation process, if
the JDK is not already installed, it will be installed. The same is
applicable for JRE on all platforms, except for Linux where the JDK
cannot be installed over the JRE.
Communication requirements
v TCP/IP (The Linux base operating system provides TCP/IP
connectivity, if selected during installation).
Related tasks:
v “Modifying kernel parameters (Linux)” in the Quick Beginnings for DB2
Servers
Installation requirements for DB2 clients (Solaris)
The following list provides hardware requirements, operating system
requirements, software requirements, and communication requirements for
your DB2 client on Solaris Operating Environment.
Chapter 17. Installing clients
117
Restrictions:
A system reboot is required if the kernel configuration parameters have been
updated. The kernel configuration parameters are set in /etc/system and if
these parameters require modification to accommodate the DB2 client, a
reboot will be necessary to make the changes to /etc/system effective.
Note: The parameters must be set in advance of the DB2 client install.
Hardware requirements
Solaris SPARC-based computer
Operating system requirements
v Solaris Version 2.7 or later
Note: Solaris Version 2.7 is required for 64-bit.
v The following patches are required for the Solaris operating
environment Version 2.7:
– Solaris 7 (32-bit) patch 106327-8
– Solaris 7 (64-bit) patch 106300-09
– Solaris 8 (32-bit) patch 108434-01 + 106528-12
– Solaris 8 (64-bit) patches 108435-01 + 108528-12
Software requirements
v For 32-bit Solaris, the Java Runtime Environment (JRE) Version 1.3.1
is required to run DB2 graphical tools, such as the Control Center.
The DB2 JAVA GUI tools are not provided with the DB2 Version 8
Run-Time Client.
v For 64-bit Solaris, the Java Runtime Environment (JRE) Version 1.4.0
is required to run DB2 graphical tools, such as the Control Center.
The DB2 JAVA GUI tools will not be provided with the DB2 Version
8 Run-Time Client.
v If you are installing the Application Development Client you may
require the Java Developer’s Kit. The JDK will be available with the
electronically downloaded version of DB2. For installation using
CDs, the JDK will be included on a separate CD. This is also
applicable for the JRE.
Communication requirements
v APPC or TCP/IP.
v For APPC connectivity, you require DCL SNA.
v The Solaris base operating system provides TCP/IP connectivity.
Related tasks:
118
DB2 Connect EE Quick Beginnings
v “Modifying kernel parameters (Solaris)” in the Quick Beginnings for DB2
Servers
Disk requirements for DB2 clients
The actual fixed disk requirements of your installation may vary depending
on your file system and the client components you install. Ensure that you
have included a disk space allowance for your application development tools
and communication products.
The following tables provide minimum disk space requirements for DB2
clients on Windows and UNIX–based operating systems. When you install a
DB2 client using the DB2 Setup wizard, size estimates are dynamically
provided by the installation program based on installation type and
component selection.
Table 18. DB2 Clients for Windows — recommended minimum disk space
DB2 Clients for Windows
Recommended minimum disk space
(MB)
DB2 Run-Time Client
20 to 30 MB
DB2 Administration Client
80 to 110 MB
DB2 Application Development Client
325 MB, including the JDK
Table 19. DB2 Clients for UNIX — recommended minimum disk space
DB2 Clients for UNIX
Recommended minimum disk space
(MB)
DB2 Run-Time Client
50 to 60 MB
Note: An additional 20 MB may be
needed for the instance creation in the
/home directory.
DB2 Administration Client
125 MB, not including the JRE
Note: An additional 20 MB may be
needed for the instance creation in the
/home directory.
DB2 Application Development Client
130 to 160 MB, not including the JDK
Note: An additional 20 MB may be
needed for the instance creation in the
/home directory.
Related concepts:
v “DB2 clients” on page 109
Chapter 17. Installing clients
119
Related tasks:
v “Installing a DB2 client on Windows operating systems” on page 120
v “Installing DB2 clients on UNIX” on page 122
Memory requirements for DB2 clients
The following list outlines the recommended minimum memory requirements
for the different types of DB2 clients:
v The amount of memory required for the DB2 Run-Time client depends on
the operating system and the database applications that you are running. In
most cases, it should be sufficient to use the minimum memory
requirements of the operating system as the minimum requirement for
running the DB2 Run-Time client.
v To run graphical tools on an Administration or Application Development
client, you will require an additional amount of 64 MB of RAM. For
example, to run graphical tools on an Administration Client machine
running Windows 2000 Professional, you would need a minimum of 64 MB
of RAM for the operating system plus an additional amount of 64 MB of
RAM for the tools.
Note: Performance may be affected if less than the recommended minimum
memory requirements are used.
Related concepts:
v “DB2 clients” on page 109
Related tasks:
v “Installing a DB2 client on Windows operating systems” on page 120
v “Installing DB2 clients on UNIX” on page 122
Installing a DB2 client on Windows operating systems
This task describes how to install a DB2 client on a Windows operating
system.
Prerequisites:
Before you install your DB2 client:
v Ensure that your system meets all of the memory, disk space, and
installation requirements.
v Ensure that you have a user account to perform the installation:
120
DB2 Connect EE Quick Beginnings
Windows 98, Windows ME
Any valid Windows 98 user account.
Windows Terminal Server, Windows NT, Windows 2000, Windows XP,
and Windows .NET
A user account that belongs to a group with more authority than
the Guests group, such as the Users group.
Note: To perform an installation on Windows 2000 servers and
Windows .NET as part of the Users group, the registry
permissions have to be modified to allow Users write access
to the HKEY_LOCAL_MACHINE\Software registry branch. In the
default Windows 2000 and Windows .NET environment,
members of the Users group only have read access to the
HKEY_LOCAL_MACHINE\Software registry branch.
Procedure:
To install a DB2 client:
1. Log on to the system with the user account that you want to use to
perform the installation.
2. Shut down any other programs so that the DB2 Setup wizard can update
files as required.
3. Insert the appropriate CD-ROM into the drive. The auto-run feature
automatically starts the DB2 Setup wizard. The DB2 Setup wizard will
determine the system language, and launch the setup program for that
language. You can run the DB2 Setup wizard in a language other than the
default system language by manually invoking the DB2 Setup wizard and
specifying a language code.
4. Choose Install Products once the DB2 Launchpad opens.
5. Proceed by following the DB2 Setup wizard’s prompts. Online help is
available to guide you through the remaining steps.
After installing your DB2 client, you should configure it to access a remote
DB2 server.
Related tasks:
v “Configuring a client to server connection using the Configuration Assistant
(CA)” in the Quick Beginnings for DB2 Servers
v “Configuring remote access to a server database” in the Installation and
Configuration Supplement
v “Starting the DB2 Setup wizard for a DB2 server installation (Windows)” in
the Quick Beginnings for DB2 Servers
Chapter 17. Installing clients
121
Related reference:
v “Language identifiers (for running the DB2 Setup wizard in another
language)” on page 155
Installing DB2 clients on UNIX
This task provides steps for installing a DB2 client on UNIX.
Prerequisites:
Before you begin installing a DB2 client on UNIX:
v Ensure that your system meets all of the memory, hardware, and software
requirements to install your DB2 product.
v Installing a DB2 client in the Solaris Operating Environment or on HP-UX
requires that you update your kernel configuration parameters and restart
your system.
Procedure:
After updating your kernel configuration parameters and rebooting your
system (required for Solaris and HP-UX), you can install your DB2 client.
To install a DB2 client on UNIX:
1. Log in as a user with root authority.
2. Insert and mount the appropriate CD-ROM.
3. Change to the directory where the CD-ROM is mounted by entering the
cd /cdrom command where /cdrom is the CD-ROM mount point.
4. Enter the ./db2setup command. At this point the DB2 Setup Wizard will
start.
5. Choose Install Products once the DB2 Launchpad opens.
6. Select the client you want to install.
7. Proceed by following the DB2 setup Wizard’s prompts. Online help is
available to guide you through the remaining steps.
When installation is complete DB2 software will be installed in the DB2DIR
directory,
where DB2DIR
122
DB2 Connect EE Quick Beginnings
= /usr/opt/db2_08_01 on AIX
= /opt/IBM/db2/V8.1 on all other UNIX operating
systems.
After installing your DB2 client, you should configure it to access a remote
DB2 server.
Related tasks:
v “Modifying kernel parameters (Solaris)” in the Quick Beginnings for DB2
Servers
v “Modifying kernel parameters (HP-UX)” in the Quick Beginnings for DB2
Servers
v “Configuring a client to server connection using the Configuration Assistant
(CA)” in the Quick Beginnings for DB2 Servers
v “Configuring remote access to a server database” in the Installation and
Configuration Supplement
v “Modifying kernel parameters (Linux)” in the Quick Beginnings for DB2
Servers
Chapter 17. Installing clients
123
124
DB2 Connect EE Quick Beginnings
Chapter 18. Configuring DB2 clients to use DB2 Connect
When installing DB2 Connect Personal Edition, you can also choose to install
a DB2 run-time client. These topics detail the instructions of how to configure
a connection from the DB2 run-time client to a DB2 UDB server. The DB2
run-time client can connect to databases on Windows and UNIX, as well as
host or iSeries databases using DB2 Connect. You can connect directly to host
or iSeries databases using DB2 Connect Personal Edition, if you have it
installed on the same workstation as the DB2 run-time client, or you can
connect through a DB2 Connect Enterprise Edition server.
This task describes how to connect a DB2 client to a remote database host or
iSeries database server using the Configuration Assistant (CA). The
Configuration Assistant is a DB2 GUI tool that can be used to configure
database connections and other database settings.
The Configuration Assistant (CA) was referred to as the Client Configuration
Assistant (CCA) in previous releases of DB2.
Prerequisites:
v The Configuration Assistant must be installed on DB2 Connect workstation.
In DB2 Version 8, the Configuration Assistant is available as part of the DB2
Administration Client and DB2 Application Development Client.
v The remote server must be configured to accept inbound client requests. By
default, the server installation program detects and configures most
protocols on the server for inbound client connections.
Procedure:
To configure a connection to a database using the CA, select one of the
following methods:
v Connecting to a database using discovery
v Connecting to a database using a profile
v Connecting to a database manually using the CA
Configuration tasks
Configuring a database connection using Discovery
You can use the Discovery feature of the Configuration Assistant to search a
network for databases.
© Copyright IBM Corp. 1993-2002
125
Prerequisites:
Before you configure a connection to a database using Discovery:
v Ensure that you have a valid DB2 user ID.
v If adding a database to a system that has a DB2 Server or DB2 Connect
server product installed, ensure that you have a user ID with SYSADM or
SYSCTRL authority for the instance.
Restrictions:
A DB2 Administration Server (DAS) must be running and enabled for the
Discovery feature of the CA to return information about DB2 systems.
Procedure:
To add a database to your system using Discovery:
1. Log on to the system with a valid DB2 user ID.
2. Start the CA. The CA can be started from the Start menu on Windows or
using the db2ca command on both Windows and UNIX systems.
3. On the CA menu bar, under Selected, choose Add a database using
wizard.
4. Select the Search the network radio button and click Next.
5. Double-click on the folder beside Known Systems to list all the systems
known to your client.
6. Click the [+] sign beside a system to get a list of the instances and
databases on it. Select the database that you want to add, click the Next
push button,
7. Enter a local database alias name in the Database alias field and
optionally enter a comment that describes this database in the Comment
field.
8. If you are planning to use ODBC, register this database as an ODBC data
source. ODBC must be installed to perform this operation.
9. Click Finish. You are now able to use the database you added. Click Close
to exit the CA.
Related tasks:
v “Configuring a database connection using the Configuration Assistant
(CA)” on page 92
v “Configuring a database connection using a profile” on page 91
v “Testing a database connection” on page 93
126
DB2 Connect EE Quick Beginnings
Configuring a database connection using a profile
A server profile contains information about server instances on a system, and
databases within each server instance. A client profile contains database
information that was cataloged on another client system. Use the steps in the
following task to connect to a database using a profile.
Prerequisites:
Before you connect to a database through the CA using a profile:
v Ensure that you have a valid DB2 user ID.
v If adding a database to a system that has a DB2 Server or DB2 Connect
server product installed, ensure that you have a user ID with SYSADM or
SYSCTRL authority for the instance.
Procedure:
To connect to a database using a profile:
1. Log on to the system with a valid DB2 user ID.
2. Start the CA. The CA can be started from the Start menu on Windows or
using the db2ca command on both Windows and UNIX systems.
3. On the CA menu bar, under Selected, choose Add a database using
wizard.
4. Select the Use a profile radio button and click Next.
5. Click the ... push button and select a profile. Select a remote database from
the object tree that is displayed from the profile, and if the database
selected is a gateway connection, select a connection route to the database.
Click the Next push button.
6. Enter a local database alias name in the Database alias field and
optionally enter a comment that describes this database in the Comment
field. Click Next.
7. If you are planning to use ODBC, register this database as an ODBC data
source. ODBC must be installed to perform this operation.
8. Click Finish. You are now able to use this database. Select the Exit menu
action to exit the CA.
Related tasks:
v “Creating client profiles using the export function of the Configuration
Assistant (CA)” on page 131
v “Testing a database connection” on page 93
Chapter 18. Configuring DB2 clients to use DB2 Connect
127
Configuring a database connection using the Configuration Assistant
(CA)
If you have the information for the database you want to connect to and the
server upon which it resides, you can manually enter all of the configuration
information. This method is analogous to entering commands via the
command line processor, however, the parameters are presented graphically.
Prerequisites:
Before you configure a connection to a database using the CA:
v Ensure that you have a valid DB2 user ID.
v If adding a database to a system that has a DB2 Server or DB2 Connect
server product installed, ensure that you have a user ID with SYSADM or
SYSCTRL authority for the instance.
Procedure:
To add a database to your system manually using the CA:
1. Log on to the system with a valid DB2 user ID.
2. Start the CA. The CA can be started from the Start menu on Windows or
using the db2ca command on both Windows and UNIX systems.
3. On the CA menu bar, under Selected, choose Add a database using
wizard.
4. Select the Manually configure a connection to a database radio button
and click Next.
5. If you are using Lightweight Directory Access Protocol (LDAP), select the
radio button that corresponds to the location where you would like your
DB2 directories to be maintained. Click Next.
6. Select the radio button that corresponds to the protocol that you want to
use from the Protocol list.
If DB2 Connect is installed on your machine and you select TCP/IP or
APPC, you have the option to select The database physically resides on
a host or OS/400 system. If you select this check box, you will have the
option of selecting the type of connection that you want to make to the
host or OS/400 database:
v To make a connection through a DB2 Connect gateway, select the
Connect to the server via the gateway radio button.
v To make a direct connection, select the Connect directly to the server
radio button.
Click Next.
7. Enter the required communication protocol parameters and click Next.
128
DB2 Connect EE Quick Beginnings
8. Enter the database alias name of the remote database that you want to
add in the Database name field and a local database alias name in the
Database alias field.
If you are adding a host or OS/400 database, type the Location name for
an OS/390 or z/OS database, the RDB name for an OS/400 database, or
the DBNAME for a VSE or VM database in the Database name field.
Optionally add a comment that describes this database in the Comment
field.
Click Next.
9. If you are planning to use ODBC, register this database as an ODBC data
source. ODBC must be installed to perform this operation.
10. Click Finish. You are now able to use this database. Select the Exit menu
action to close the CA.
Related tasks:
v “Configuring a database connection using Discovery” on page 90
v “Configuring a database connection using a profile” on page 91
v “Testing a database connection” on page 93
Testing a database connection
After configuring the database, the database connection should be tested.
Procedure:
To test a database connection:
1. Start the CA.
2. Highlight the database in the details view and invoke the Test Connection
menu action. The Test Connection window opens.
3. Select the type of connection that you would like to test (CLI is the
default). Enter a valid user ID and password for the remote database and
click Test Connection. If the connection is successful, a message
confirming the connection appears on the Results page.
If the connection test failed, you will receive a help message. To change
any settings you may have incorrectly specified, select the database in the
details view and invoke the Change Database menu action.
Related tasks:
v “Configuring a database connection using Discovery” on page 90
v “Configuring a database connection using the Configuration Assistant
(CA)” on page 92
v “Configuring a database connection using a profile” on page 91
Chapter 18. Configuring DB2 clients to use DB2 Connect
129
130
DB2 Connect EE Quick Beginnings
Chapter 19. Using client and server profiles
Client profiles
Client profiles are used to configure database connections between DB2®
clients and servers. A client profile is generated from a client using the export
function of the Configuration Assistant (CA) or by using the db2cfexp
command. The information contained in a client profile is determined during
the export process. Depending on the settings chosen, it can contain
information such as the following:
v Database connection information (including CLI or ODBC settings).
v Client settings (including database manager configuration parameters and
DB2 registry variables).
v CLI or ODBC common parameters.
v Configuration data for the local APPC or NetBIOS communications
subsystem.
Once the information in a client profile has been determined, it can be used to
configure other clients by using either the import function of the CA, or by
importing profiles using the db2cfimp command. Clients can import all or a
subset of the configuration information in an existing profile.
Related tasks:
v “Configuring a database connection using a profile” on page 91
v “Exporting and importing a profile” on page 134
v “Creating client profiles using the export function of the Configuration
Assistant (CA)” on page 131
v “Configuring client profiles using the import function of the Configuration
Assistant (CA)” on page 133
Creating client profiles using the export function of the Configuration Assistant
(CA)
Client profiles are used to create connections between DB2 clients and servers.
The information contained in a client profile is determined during the export
process. Once the information in a client profile has been determined, it can
be used to configure other clients by using the import process.
Procedure:
© Copyright IBM Corp. 1993-2002
131
To create client profiles using the export function of the CA, perform the
following steps:
1. Start the CA.
2. Click Export. The Select Export Option window opens.
3. Select one of the following options:
v If you want to create a profile that contains all of the databases
cataloged on your system, and all of the configuration information for
this client, select the All radio button, click OK, and go to Step 8.
4.
5.
6.
7.
8.
v If you want to create a profile that contains all of the databases
cataloged on your system without any of the configuration information
for this client, select the Database connection information radio button,
click OK, and go to Step 8.
v If you want to select a subset of the databases that are cataloged on
your system, or a subset of the configuration information for this client,
select the Customize radio button, click OK, and go to the next step.
Select the databases to be exported from the Available databases box and
add them to the Selected databases box by clicking on the push button. To
add all of the available databases to the Databases to be exported box,
click the >> button.
Select the check boxes from the Select custom export option box that
correspond to the options that you want to set up for the target client.
Click OK. The Export Client Profile window opens.
Enter a path and file name for this client profile and click OK. The DB2
Message window opens.
Click OK.
Once you have completed this task, you must then use the import function to
configure other clients.
Related concepts:
v “Client profiles” on page 131
Related tasks:
v “Configuring a database connection using a profile” on page 91
v “Exporting and importing a profile” on page 134
v “Configuring client profiles using the import function of the Configuration
Assistant (CA)” on page 133
132
DB2 Connect EE Quick Beginnings
Configuring client profiles using the import function of the Configuration
Assistant (CA)
This task must be performed to configure client profiles after using the export
function of the CA. Client profiles are used to create connections between DB2
clients and servers. The information contained in a client profile is determined
during the export process. Once the information in a client profile has been
determined, it can be used to configure other clients by using the import
process.
Procedure:
To configure client profiles using the import function of the CA, perform the
following steps:
1. Start the CA.
2. Click Import. The Select Profile window opens.
3. Select a client profile to import and click OK. The Import Profile window
opens.
4. You can choose to import all or a subset of the information in a Client
Profile. Select one of the following import options:
v To import everything in a client profile, select the All radio button. If
you choose this option, you are now ready to start using your DB2
product.
v To import a specific database or settings that are defined in a Client
Profile, select the Customize radio button. Select the check boxes that
correspond to the options that you want to customize.
5. Click OK.
6. You are presented with a list of systems, instances, and databases. Select
the database that you want to add and click Next.
7. Enter a local database alias name in the Database alias field and
optionally enter a comment that describes this database in the Comment
field. Click Next.
8. If you are planning to use ODBC, register this database as an ODBC data
source.
Note: ODBC must be installed to perform this operation.
a. Ensure that the Register this database for ODBC check box is
selected.
b. Select the radio button that describes how you would like to register
this database:
v If you would like all users on your system to have access to this
data source, select the As a system data source radio button.
Chapter 19. Using client and server profiles
133
v If you would like only the current user to have access to this data
source, select the As a user data source radio button.
v If you would like to create an ODBC data source file to share
database access, select the As a file data source radio button and
enter the path and file name for this file in the File data source
name field.
c. Click the Optimize for application drop down box and select the
application for which you want to tune the ODBC settings.
d. Click Finish to add the database that you selected. The Confirmation
window opens.
9. Click the Test Connection push button to test the connection. The
Connect to DB2 Database window opens.
10. In the Connect to DB2 Database window, enter a valid user ID and
password for the remote database and click OK. If the connection is
successful, a message confirming the connection appears.
If the connection test failed, you will receive a help message. To change
any settings that you may have incorrectly specified, click the Change
push button in the Confirmation window to return to the Add Database
Wizard.
11. You are now able to use this database. Click Add to add more databases,
or click Close to exit the Add Database Wizard. Click Close again to exit
the CA.
Related concepts:
v “Client profiles” on page 131
Related tasks:
v “Configuring a database connection using a profile” on page 91
v “Exporting and importing a profile” on page 134
v “Creating client profiles using the export function of the Configuration
Assistant (CA)” on page 131
Exporting and importing a profile
Procedure:
If you did not use a configuration profile when you installed your DB2
product using the response file that was created by the response file generator,
you can enter the db2cfexp command to create a configuration profile. The
db2cfimp command can then be used to import a configuration profile.
You can also use the CA to export and import a configuration profile.
134
DB2 Connect EE Quick Beginnings
Part 6. Using DB2 Connect
© Copyright IBM Corp. 1993-2002
135
136
DB2 Connect EE Quick Beginnings
Chapter 20. Running your own applications
You can build and run DB2® applications with a DB2 Application
Development Client installed. You can also run DB2 applications on the DB2
Run-Time Client and the DB2 Administration Client.
Various types of applications can access DB2 databases:
v Applications developed using the DB2 Application Development Client that
include embedded SQL, APIs, stored procedures, user-defined functions or
calls to the DB2 CLI.
v ODBC applications such as Lotus® Approach.
v JDBC applications and applets.
v Net.Data® macros containing HTML and SQL.
On Windows® operating systems, the following can also access DB2
databases:
v ActiveX Data Objects (ADO) implemented in Microsoft® Visual Basic and
Microsoft Visual C++
v Remote Data Objects (RDO) implemented in Microsoft Visual Basic
v Object Linking and Embedding (OLE) Automation Routines (UDFs and
Stored Procedures)
v Object Linking and Embedding Database (OLE DB) table functions
An application on a DB2 client can access a remote database without knowing
its physical location. The DB2 client determines the location of the database,
manages the transmission of the requests to the database server, and returns
the results.
To run a database client application:
1. Ensure the server is configured and running.
2. Ensure that the database manager is started on the database server to
which the application program is connecting. If it is not, you must issue
the db2start command at the server before starting the application.
3. Ensure that you can connect to the database that the application uses.
4. Bind the utilities and the applications to the database.
5. Run the application program.
Related concepts:
v “DB2 Supported Programming Interfaces” in the Application Development
Guide: Programming Client Applications
© Copyright IBM Corp. 1993-2002
137
Related reference:
v “DB2 Application Development Client” in the Application Development Guide:
Building and Running Applications
138
DB2 Connect EE Quick Beginnings
Chapter 21. Binding database utilities on DB2 Connect
You must bind the database utilities (import, export, reorg, the Command
Line Processor) and DB2 CLI bind files to each database before they can be
used with that database. In a network environment, if you are using multiple
clients that run on different operating systems or are at different versions or
service levels of DB2, you must bind the utilities once for each operating
system and DB2-version combination.
Binding a utility creates a package, which is an object that includes all of the
information that is needed to process specific SQL statements from a single
source file.
The bind files are grouped together in different .lst files in the bnd directory,
under the installation directory (typically sqllib for Windows). Each file is
specific to a server.
Procedure:
Binding to host or iSeries databases
To bind the utilities and applications to the host or iSeries database
server, connect to the host or iSeries server and use the following
example as a template:
connect to dbalias user userid using password
bind path/bnd/@ddcsmvs.lst blocking all sqlerror continue
messages mvs.msg grant public
connect reset
where path corresponds to the DB2PATH registry value.
Binding to DB2 Universal Databases
How you bind the database utilities to a database depends on your
workstation’s operating system:
v Using the Configuration Assistant:
1. Start the Configuration Assistant (CA).
2. Select the database to which you want to bind the utilities.
3. Click Bind.
4. Select the Bind DB2 Utilities radio button.
5. Click Continue.
6. Enter a user ID and password to connect to the database. The
user ID must have the authority to bind new packages against
the database. Select the utilities you want to bind and click OK.
v Use the command line processor:
© Copyright IBM Corp. 1993-2002
139
1. Change to the bnd directory, which is x:\sqllib\bnd, where x:
represents the drive where you installed DB2.
2. To connect to the database, enter the following commands in the
Command Center or the Command Line Processor:
connect to database_alias
where database_alias represents the name of the database to
which you want to connect.
3. Enter the following commands in the Command Center or the
Command Line Processor:
"bind @db2ubind.lst messages bind.msg grant public"
"bind @db2cli.lst messages clibind.msg grant public"
In this example, bind.msg and clibind.msg are the output
message files, and EXECUTE and BINDADD privileges are
granted to public.
4. Reset the connection to the database by entering the following
command:
connect reset
Notes:
1. The db2ubind.lst file contains the list of bind (.bnd) files required
to create the packages for the database utilities. The db2cli.lst
file contains the list of bind (.bnd) files required to create packages
for the DB2 CLI and the DB2 ODBC driver.
2. Binding may take a few minutes to complete.
3. If you have BINDADD authority, the first time you use the DB2
CLI or ODBC driver, the DB2 CLI packages will be bound
automatically. If the applications that you are using require
binding to the database, you can use the Configuration Assistant’s
Bind facility, or the command line processor, to perform the bind
action.
Related reference:
v “BIND” in the Command Reference
v “DB2 CLI Bind Files and Package Names” in the CLI Guide and Reference,
Volume 1
140
DB2 Connect EE Quick Beginnings
Chapter 22. DB2 Connect and the CLI environment
Setting Up the CLI Environment
Runtime support for DB2 CLI applications is contained in all DB2 clients.
Support for building and running DB2 CLI applications is contained in the
DB2 Application Development (DB2 AD) Client. This section describes the
general setup required for DB2 CLI runtime support.
The CLI/ODBC driver will autobind on the first connection to the database,
provided the user has the appropriate privilege or authorization. The
administrator may want to perform the first connect or explicitly bind the
required files.
Prerequisites:
Before you set up your CLI environment, ensure you have set up the
application development environment.
Procedure:
In order for a DB2 CLI application to successfully access a DB2 database:
1. Ensure the DB2 CLI/ODBC driver was installed during the DB2 client
install.
2. Catalog the DB2 database and node if the database is being accessed from
a remote client.
On the Windows platform, you can use the CLI/ODBC Settings GUI to
catalog the DB2 database.
3. Optional: Explicitly bind the DB2 CLI/ODBC bind files to the database
with the command:
db2 bind ~/sqllib/bnd/@db2cli.lst blocking all sqlerror continue \
messages cli.msg grant public
On the Windows platform, you can use the CLI/ODBC Settings GUI to
bind the DB2 CLI/ODBC bind files to the database.
4. Optional: Change the DB2 CLI/ODBC configuration keywords by editing
the db2cli.ini file, located in the sqllib directory on Windows, and in
the sqllib/cfg directory on UNIX platforms.
On the Windows platform, you can use the CLI/ODBC Settings GUI to set
the DB2 CLI/ODBC configuration keywords.
© Copyright IBM Corp. 1993-2002
141
Once you have completed the above steps, proceed to setting up your
Windows CLI environment, or setting up your UNIX ODBC environment if
you are running ODBC applications on UNIX.
Related concepts:
v “Initialization and Termination in CLI Overview” in the CLI Guide and
Reference, Volume 1
Related tasks:
v “Initializing CLI Applications” in the CLI Guide and Reference, Volume 1
v “Setting Up the UNIX ODBC Environment” on page 142
v “Setting Up the Windows CLI Environment” on page 144
Related reference:
v “BIND” in the Command Reference
v “CATALOG DATABASE” in the Command Reference
Setting Up the UNIX ODBC Environment
This topic explains how to set up UNIX client access to DB2 for ODBC
applications. (If your application is a DB2 CLI application, your CLI
environmental setup will be complete once the task in the Prerequisites
section is performed.)
Prerequisites:
Before setting up the UNIX ODBC environment, ensure you have set up the
CLI environment.
Procedure:
For ODBC applications on UNIX that need to access a DB2 database, follow
the steps described below.
1. Ensure that an ODBC Driver Manager is installed and that each user that
will use ODBC has access to it. DB2 does not install an ODBC Driver
Manager, so you must use the ODBC Driver Manager that was supplied
with your ODBC client application or ODBC SDK in order to access DB2
data using that application.
2. Set up .odbc.ini, the end-user’s data source configuration. Each user ID
has a separate copy of this file in their home directory. Note that the file
starts with a dot. Although necessary files are usually updated
automatically by the tools on most platforms, users of ODBC on UNIX
platforms will have to edit them manually.
142
DB2 Connect EE Quick Beginnings
Using an ASCII editor, update the file to reflect the appropriate data
source configuration information. To register a DB2 database as an ODBC
data source there must be one stanza (section) for each DB2 database.
The .odbc.ini file must contain the following lines:
v in the [ODBC Data Source] stanza:
SAMPLE=IBM DB2 ODBC DRIVER
which indicates that there is a data source called SAMPLE that used the
IBM DB2 ODBC DRIVER;
v in the [SAMPLE] stanza:
on AIX, for example,
[SAMPLE]
Driver=/u/thisuser/sqllib/lib/libdb2.a
Description=Sample DB2 ODBC Database
on Solaris, for example,
[SAMPLE]
Driver=/u/thisuser/sqllib/lib/libdb2.so
Description=Sample DB2 ODBC Database
which indicates that the SAMPLE database is part of the DB2 instance
located in the directory /u/thisuser.
3. Ensure that the application execution environment has reference to the
ODBC Driver Manager by including libodbc.a (for AIX) or libodbc.so
(for UNIX) in the LIBPATH (for AIX) or LD_LIBRARY_PATH (for UNIX)
environment variables.
4. Enable a system-wide .odbc.ini file to be used by setting the ODBCINI
environment variable to the fully qualified pathname of the .ini file. Some
ODBC driver managers support this feature which allows for centralized
control. The following examples show how to set ODBCINI:
in the C shell,
setenv ODBCINI /opt/odbc/system_odbc.ini
in the Bourne or Korn shell,
ODBCINI=/opt/odbc/system_odbc.ini;export ODBCINI
5. Once the .odbc.ini file is set up, you can run your ODBC application and
access DB2 databases. Refer to the documentation that comes with your
ODBC application for additional help and information.
Related concepts:
v “Comparison of DB2 CLI and Microsoft ODBC” in the CLI Guide and
Reference, Volume 1
Chapter 22. DB2 Connect and the CLI environment
143
v “Initialization and Termination in CLI Overview” in the CLI Guide and
Reference, Volume 1
Related tasks:
v “Initializing CLI Applications” in the CLI Guide and Reference, Volume 1
v “Setting Up the CLI Environment” on page 141
v “Building CLI Applications on UNIX” in the CLI Guide and Reference, Volume
1
v “Building CLI Routines on UNIX” in the CLI Guide and Reference, Volume 1
Setting Up the Windows CLI Environment
This task tells you how to perform Windows client access to DB2 using CLI or
ODBC.
Prerequisites:
Before setting up the Windows CLI environment, ensure that the CLI
environment has been set up.
Restrictions:
When using the Configuration Assistant on Windows 64-bit platforms, ODBC
Data Sources can be configured only for 64-bit applications. ODBC Data
Sources for 32-bit applications need to be configured using the Microsoft
32-bit ODBC Data Source Administrator (32-bit odbcad32.exe) that is included
with the Windows 64-bit operating system.
Procedure:
Before DB2 CLI and ODBC applications can successfully access a DB2
database from a Windows client, perform the following steps on the client
system:
1. Verify that the Microsoft ODBC Driver Manager and the DB2 CLI/ODBC
driver are installed. On Windows operating systems they are both installed
with DB2 unless the ODBC component is manually unselected during the
install. DB2 will not overwite a newer version of the Microsoft ODBC
Driver Manager if one is found. To verify that they both exist on the
machine:
a. Start the Microsoft ODBC Data Sources icon in the Control Panel, or
run the odbcad32.exe command from the command line.
b. Click on the ″Drivers″ tab.
c. Verify that IBM DB2 ODBC DRIVER is shown in the list.
144
DB2 Connect EE Quick Beginnings
If either the Microsoft ODBC Driver Manager or the IBM DB2 CLI/ODBC
driver is not installed, then rerun the DB2 install and select the ODBC
component on Windows operating systems.
Note: The latest version of the Microsoft ODBC Driver Manager is
included as part of the Microsoft Data Access Components (MDAC)
and is available for download from
http://www.microsoft.com/data/.
2. Register the DB2 database with the ODBC driver manager as a data
source. On Windows operating systems you can make the data source
available to all users of the system (a system data source), or only the
current user (a user data source). Use either of these methods to add the
data source:
v Using the Configuration Assistant:
a. Select the DB2 database alias that you want to add as a data source.
b. Click on the ″Properties″ push button. The Database Properties
window opens.
c. Select the ″Register this database for ODBC″ check box.
d. Use the radio buttons to add the data source as either a user, system,
or file data source.
v Using the Microsoft ODBC Administration tool, which you can access
from the icon in the Control Panel or by running odbcad32.exe from the
command line:
a. The list of user data sources appears by default. If you want to add
a system data source click on the ″System DSN″ button, or the
″System DSN″ tab (depending on the platform).
b. Click on the ″Add″ push button.
c. Double-click on the IBM DB2 ODBC Driver in the list.
d. Select the DB2 database to add and click on OK.
v Use the CATALOG command to register the DB2 database with the ODBC
driver manager as a data source:
CATALOG [ user | system ] ODBC DATA SOURCE
Using this command, an administrator could create a command line
processor script to register the required databases. This script could then
be run on all machines that require access to DB2 databases through
ODBC.
3. Optional: Configure the DB2 CLI/ODBC driver using the Configuration
Assistant:
a. Select the DB2 database alias you want to configure.
b. Click on the ″Properties″ push button. The Database Properties
window opens.
Chapter 22. DB2 Connect and the CLI environment
145
c. Click on the ″Settings″ push button. The CLI/ODBC Settings window
opens.
d. Click on the ″Advanced″ push button. You can set the configuration
keywords in the window that opens. These keywords are associated
with the database alias name, and affect all DB2 CLI/ODBC
applications that access the database.
4. If you have installed ODBC access (as described above), you can now
access DB2 data using ODBC applications.
Related concepts:
v “db2cli.ini Initialization File” in the CLI Guide and Reference, Volume 1
v “Initialization and Termination in CLI Overview” in the CLI Guide and
Reference, Volume 1
Related tasks:
v “Initializing CLI Applications” in the CLI Guide and Reference, Volume 1
v “Setting Up the CLI Environment” on page 141
v “Building CLI Applications on Windows” in the CLI Guide and Reference,
Volume 1
v “Building CLI Routines on Windows” in the CLI Guide and Reference, Volume
1
146
DB2 Connect EE Quick Beginnings
Part 7. Appendixes
© Copyright IBM Corp. 1993-2002
147
148
DB2 Connect EE Quick Beginnings
Appendix A. Language Support
Changing the DB2 interface language (Windows)
The interface language of DB2 is the language that appears in messages, help,
and graphical tool interfaces. When installing DB2, you have the option of
installing support for one or more languages. If, at some time after
installation, you want to change the interface language for DB2 to one of the
other installed interface languages, use the steps outlined in this task.
Do not confuse languages supported by DB2 with languages supported by the
DB2 interface. Languages supported by DB2, that is, languages that data can
exist in, are a superset of languages supported by the DB2 interface.
Prerequisites:
The DB2 interface language you want to use must be installed on your
system. DB2 interface languages are selected and installed when you install
DB2 using the DB2 Setup wizard. If you change the interface language of DB2
to a supported interface language that has not been installed, the DB2
interface language will default to the operating system language first, and if
that is not supported, English.
Procedure:
Changing the interface language for DB2 on Windows requires that you
change the default language setting for your Windows operating system.
To change the DB2 interface language on Windows:
1. Through the Control Panel on your Windows operating system, select
Regional Options.
2. In the Regional Options dialog window, change the default language
setting for the system to the language in which you want to interface with
DB2.
Refer to your operating system help for additional information about
changing the default system language.
Related reference:
v “Supported territory codes and code pages” in the Administration Guide:
Planning
v “Supported DB2 interface languages, locales, and code pages” on page 150
© Copyright IBM Corp. 1993-2002
149
Changing the DB2 interface language (UNIX)
The interface language of DB2 is the language that appears in messages, help,
and graphical tool interfaces. When installing DB2, you have the option of
installing support for one or more languages. If, at some time after
installation, you want to change the interface language for DB2 to one of the
other installed interface languages, use the steps outlined in this task.
Do not confuse languages supported by DB2 with languages supported by the
DB2 interface. Languages supported by DB2, that is, languages that data can
exist in, are a superset of languages supported by the DB2 interface.
Prerequisites:
Support for the DB2 interface language you want to use must be installed on
your system. DB2 interface language support is selected and installed when
you install DB2 using the DB2 Setup wizard. If you change the interface
language of DB2 to a supported interface language that has not been installed,
the DB2 interface language will default to the operating system language first,
and if that is not supported, English.
Procedure:
To change the DB2 interface language on UNIX systems, set the LANG
environment variable to the desired locale.
For example, to interface with DB2 in French using DB2 for AIX, you must
have French language support installed and you must set the LANG
environment variable to a French locale, for example, fr_FR.
Related reference:
v “Supported territory codes and code pages” in the Administration Guide:
Planning
v “Supported DB2 interface languages, locales, and code pages” on page 150
Supported DB2 interface languages, locales, and code pages
The following two tables list the languages (by operating system) supported
by the DB2 interface, the language locale, and the code page for each locale.
The DB2 interface includes messages, help, and graphical tool interfaces.
Do not confuse languages supported by DB2 with languages supported by the
DB2 interface. Languages supported by DB2 that is, languages that data can
exist in, are a superset of languages supported by the DB2 interface.
150
DB2 Connect EE Quick Beginnings
Language
Languages supported by the DB2 interface (messages, help, and
graphical tool interfaces).
Locale/code page
The locale is used with the LANG environment variable on UNIX
systems to set the language for the DB2 interface. A locale is not
required for setting the DB2 interface language on Windows systems.
On Windows systems, the DB2 interface language is determined by
the system default language setting. The associated code page for each
locale is listed as well.
Table 20. AIX, HP-UX, and Solaris Operating Environment locales and code pages
Language
AIX locale/code
page
HP-UX locale/code
page
Solaris locale/code
page
French
fr_FR/819
Fr_FR/850
FR_FR/1208
fr_FR.iso88591/819 fr/819
fr_FR.roman8/1051 fr_FR.UTF-8/1208
fr_FR.utf8/1208
German
de_DE/819
De_DE/850
DE_DE/1208
de_DE.iso88591/819 de/819
de_DE.roman8/1051 de_DE.UTF-8/1208
de_DE.utf8/1208
Italian
it_IT/819
It_IT/850
IT_IT/1208
it_IT.iso88591/819 it/819
it_IT.roman8/1051 it_IT.UTF-8/1208
it_IT.utf8/1208
Spanish
es_ES/819
Es_ES/850
ES_ES/1208
es_ES.iso88591/819 es/819
es_ES.roman8/1051 es_ES.UTF-8/1208
es_ES.utf8/1208
Brazil. Portuguese pt_BR/819
PT_BR/1208
pt_BR.iso88591/819 pt_BR/819
pt_BR.utf8/1208
pt_BR.UTF-8/1208
Japanese
ja_JP/954
Ja_JP/932
JA_JP/1208
ja_JP.eucJP/954
ja_JP.utf8/1208
ja/954
ja_JP.UTF-8/1208
Korean
Ko_KR/970
kO_KR1208
ko_KR.eucKR/970
ko_KR.utf8/1208
ko/970
ko_KR.UTF-81208
Simplified Chinese zh_CN/1383
Zh_ CN.GBK/1386
ZH_CN/1208
zh_CN.hp15CN/1383
zh_CN.utf8/1208
zh/1383
zh_CN.UTF-8/1208
Traditional Chinese zh_TW/964
Zh_ CN.GBK/950
ZH_CN/1208
zh_CN.hp15CN/1283
zh_CN.utf8/1208
zh/1383
zh_CN.UTF-8/1208
Appendix A. Language Support
151
Table 20. AIX, HP-UX, and Solaris Operating Environment locales and code
pages (continued)
152
Language
AIX locale/code
page
HP-UX locale/code
page
Danish
da_DK/819
Da_DK/850
DA_DK/1208
da_DK.iso88591/819 da/819
da_DK.roman8/1051 da_DK.UTF-8/1208
da_DK.utf8/1208
Dutch
nl_NL/819
NL_NL/
N/A
Finnish
fi_FI/819
Fi_FI/850
FI_FI/1208
fi_FI.iso88591/819 fi/819
fi_FI.roman8/1051 fi_FI.UTF-8/1208
fi_FI.utf8/1208
Norwegian
no_NO/819
No_NO/850
NO_NO/1208
no_NO.iso88591/819 no/819
no_NO.roman8/850
no_NO.UTF-8/1208
no_NO.utf8/1208
Swedish
Sv_SE/819
sv_SE/850
SV_SE/1208
sv_SE.iso88591/819 sv/819
sv_SE.roman8/1051 sv_SE.UTF-8/1208
sv_SE.utf8/1208
Czech
cs_CZ/912
CS_CZ/1208
cs_CZ.utf8/1208
cs_CZ.UTF-8/1208
Hungarian
hu_HU/912
HU_HU/1208
hu_HU.utf8/1208
hu_HU.UTF-8/1208
Polish
pl_PL/912
PL_PL/1208
pl_PL.utf8/1208
nl_NL.UTF-8/1208
Turkish
tr_TR/920
TR_TR/1208
tr_TR.utf8/1208
tr_TR.UTF-8/1208
Russian
ru_RU/915
RU_RU/1208
ru_RU.utf8/1208
ru_RU.UTF-8/1208
Bulgarian
bg_BG/915
BG_BG/1208
bg_BG.iso88595/915 bg_BG.UTF-8/1208
bg_BG.utf8/1208
Slovenian
sl_SI/912
SL_SI/1208
sl_SI.iso88592/912 sl_SI/912
sl_SI.utf8/1208
sl_SI.UTF-8/1208
DB2 Connect EE Quick Beginnings
Solaris locale/code
page
N/A
Table 20. AIX, HP-UX, and Solaris Operating Environment locales and code
pages (continued)
Language
AIX locale/code
page
HP-UX locale/code
page
Solaris locale/code
page
Croatian
hr_HR/912
HR_HR/1208
hr_HR.iso88592/912 hr_HR/912
hr_HR.utf8/1204
hr_HR.UTF-8/1204
Slovak
sk_SK/912
SK_SK/1204
sk_SK.iso88592/912 sk_SK/912
sk_SK.utf8/1204
sk_SK.UTF-8/1204
Romanian
ro_RU/912
RO_RO/1204
ro_RO.iso88592/912 N/A
ro_RO.utf8/1204
Table 21. Linux and Linux/390 locales and codepages
Language
Linux locale/code page
Linux/390 locale/code page
French
fr/819
fr_FR.utf8/1208
fr/819
fr_FR.utf8/1208
German
de/819
de_DE.utf8/1208
de/819
de_DE.utf8/1208
Italian
de_DE.utf8/1208
it_IT.utf8/1208
Spanish
es_ES.utf8/1208
es_ES.utf8/1208
Brazil. Portuguese
pt_BR/819
pt_BR.utf8/1208
pt_BR/819
pt_BR.utf8/1208
Japanese
ja_JP.ujis/954
ja_JP.utf8/1208
ja_JP.ujis/954
ja_JP.utf8/1208
Korean
ko/970
ko_KR.utf8/1208
ko/970
ko_KR.utf8/1208
Simplified Chinese
zh zh_CN.GBKz/1386
h_CN.utf8/1208
zh zh_CN.GBK/1386
zh_CN.utf8/1208
Traditional Chinese
zh_TW.Big5/950
zh_TW.utf8/1208
zh_TW.Big5/950
zh_TW.utf8/1208
Appendix A. Language Support
153
Table 21. Linux and Linux/390 locales and codepages (continued)
Language
Linux locale/code page
Linux/390 locale/code page
Russian
ru_RU/915
ru_RU.utf8/1208
ru_RU/915
ru_RU.utf8/1208
Arabic
ar/1089
ar_AA.utf8/1208
ar/1089
ar_AA.utf8/1208
Polish
pl_PL/912
pl_PL.utf8/1208
pl_PL/912
pl_PL.utf8/1208
Czech
cs_CZ/912
cs_CZ.utf8/1208
pl_PL/912
pl_PL.utf8/1208
Hungarian
hu_HU/912
hu_HU.utf81208
hu_HU/912
hu_HU.utf8/1208
Bulgarian
bg_BG/915
bg_BG.utf8/1208
bg_BG/915
bg_BG.utf8/1208
Slovanian
sl_SI/912
sl_SI.utf8/1208
sl_SI/912
sl_SI.utf8/1208
Croatian
hr_HR/912
hr_HR.utf8/1208
hr_HR/912
hr_HR.utf8/1208
Slovak
sk_SK/912
sk_SK.utf8/1208
sk_SK/912
sk_SK.utf8/1208
Romanian
ro_RO/912
ro_RO.utf8/1208
ro_RO/912
ro_RO.utf8
/1208
Related tasks:
v “Changing the diagnostic error level before DB2 migration” in the Quick
Beginnings for DB2 Servers
v “Changing the DB2 interface language (Windows)” on page 149
v “Changing the DB2 interface language (UNIX)” on page 150
Related reference:
v “National language versions” in the Administration Guide: Planning
154
DB2 Connect EE Quick Beginnings
v “Supported territory codes and code pages” in the Administration Guide:
Planning
Language identifiers (for running the DB2 Setup wizard in another language)
If you want to run the DB2 Setup wizard in a language different from the
default language on your computer, you can start the DB2 Setup wizard
manually, specifying a language identifier. The language must be available on
the platform where you are running the installation.
Table 22. Language identifiers
Language
Language identifier
Arabic
ar
Bulgarian
bg
Brazilian Portuguese
br
Simplified Chinese
zh
Croatian
hr
Czech
cs
German
de
Danish
da
English
en
Slovenian
sl
Slovak
sk
Spanish
es
Finnish
fi
French
fr
Greek
gr
Hungarian
hu
Hebrew
il
Italian
it
Japanese
ja
Korean
ko
Dutch
nl
Norwegian
no
Polish
pl
Portuguese
pt
Russian
ru
Appendix A. Language Support
155
Table 22. Language identifiers (continued)
Language
Language identifier
Romanian
ro
Swedish
sv
Slovenian
si
Turkish
tr
Traditional Chinese
zh
Bidirectional CCSID support
The following BiDi attributes are required for correct handling of Bidirectional
data on different platforms:
-
Text type (LOGICAL vs VISUAL)
Shaping (SHAPED vs UNSHAPED)
Orientation (RIGHT-TO-LEFT vs LEFT-TO-RIGHT)
Numeral shape (ARABIC vs HINDI)
Symmetric swapping (YES or NO)
Since defaults on different platforms are not the same, problems appear when
DB2 data is sent from one platform to another. For example, Windows
platforms use LOGICAL UNSHAPED data, while data on OS/390 is usually
in SHAPED VISUAL format. Therefore, without any support for these
attributes data sent from DB2 Universal Database for OS/390 and z/OS to
DB2 UDB on a Windows 32-bit operating systems workstation displays
incorrectly.
Bidirectional-specific CCSIDs:
Table 23. Bidirectional Coded Character Set Identifiers (CCSID) defined and
implemented with DB2
156
CCSID
Code Page
String Type
00420
420
4
00424
424
4
08612
420
5
08616
424
6
12708
420
7
X’3F00’
856
4
X’3F01’
862
4
X’3F02’
916
4
DB2 Connect EE Quick Beginnings
Table 23. Bidirectional Coded Character Set Identifiers (CCSID) defined and
implemented with DB2 (continued)
X’3F03’
424
5
X’3F04’
856
5
X’3F05’
862
5
X’3F06’
916
5
X’3F07’
1255
5
X’3F08
1046
5
X’3F09’
864
5
X’3F0A’
1089
5
X’3F0B’
1256
5
X’3F0C’
856
6
X’3F0D’
862
6
X’3F0E’
916
6
X’3F0F’
1255
6
X’3F10’
420
6
X’3F11’
864
6
X’3F12’
1046
6
X’3F13’
1089
6
X’3F14’
1256
6
X’3F15’
424
8
X’3F16’
856
8
X’3F17’
862
8
X’3F18’
916
8
X’3F19’
420
8
X’3F1A’
420
9
X’3F1B’
424
10
X’3F1C’
856
10
X’3F1D’
862
10
X’3F1E’
916
10
X’3F1F’
1255
10
X’3F20’
424
11
X’3F21’
856
11
X’3F22’
862
11
Appendix A. Language Support
157
Table 23. Bidirectional Coded Character Set Identifiers (CCSID) defined and
implemented with DB2 (continued)
X’3F23’
916
11
X’3F24’
1255
11
Table 24. Where CDRA String Types are defined
String Type
Text Type
Numerical
Shape
Orientation
Shaping
Symmetrical
Swapping
4
Visual
Arabic
LTR
Shaped
OFF
5
Implicit
Arabic
LTR
Unshaped
ON
6
Implicit
Arabic
RTL
Unshaped
ON
7(*)
Visual
Arabic
Contextual(*) UnshapedLig
OFF
8
Visual
Arabic
RTL
Shaped
OFF
9
Visual
Passthru
RTL
Shaped
ON
10
Implicit
Contextual-L
ON
11
Implicit
Contextual-R
ON
Field orientation is left-to-right (LTR) when the first alphabetic character is a
Latin one, and right-to-left (RTL) when it is a bidirectional (RTL) character.
Characters are unshaped, but LamAlef ligatures are kept, and not broken into
constituents.
Conversion of character data
When character data is transferred between machines, it must be convertedto
a form that the receiving machine can use.
For example, when data is transferred between the DB2 Connect server and a
hostor iSeries™ database server, it is usually converted from a server code
pageto a host CCSID, and vice versa. If the two machines use different code
pagesor CCSIDs, code points are mapped from one code page or CCSID to
the other. This conversion is always performed at the receiver.
Character data sent to a database consistsof SQL statements and input data.
Character data sent from a database consists of output data. Output data that
is interpretedas bit data is not converted. For example, data from a column
declared withthe FOR BIT DATA clause. Otherwise all input and output
character data isconverted if the two machines have different code pages or
CCSIDs.
158
DB2 Connect EE Quick Beginnings
For example, if DB2 Connect is used to access DB2 Universal Database for
OS/390 and z/OS data, the following happens:
1. DB2® Connect sends an SQL statement and input data to OS/390® or
z/OS.
2. DB2 Universal Database for OS/390 and z/OS converts the data to an
EBCDIC CCSID and processes it.
3. DB2 Universal Database for OS/390 and z/OS sends the result back to the
DB2 Connect server.
4. DB2 Connect™ converts the result to an ASCII or ISO code page and
returnsit to the user.
The table that follows shows the conversions that are supported betweencode
pages (on the DB2 Connect Server) and CCSIDs (on the host or iSeriesserver).
Table 25. Server Code Page to host or iSeriesCCSID Conversion
Host CCSIDs
Code Page
Territory
037, 273, 277, 278, 280, 284,
285, 297, 500,871, 1140-1149
437, 819, 850, 858, 860, 863,
1004, 1051,1252, 1275
Albania, Australia, Austria,
Belgium, Brazil,Canada,
Denmark, Finland, France,
Germany, Iceland, Ireland,
Italy, LatinAmerica,
Netherlands, New Zealand,
Norway, Portugal, South
Africa, Spain,Sweden,
Switzerland, UK, USA
423, 875
737, 813, 869, 1253, 1280
Greece
4
870
852, 912, 920 ,1250, 1282
Croatia, Czech Republic,
Hungary, Poland,Romania,
Serbia/Montenegro (Latin),
Slovakia, Slovenia
1025
855, 866, 915, 1251, 1283
Bulgaria, FYR Macedonia,
Russia,
Serbia/Montenegro(Cyrillic)
1026
857, 920, 1254, 1281
Turkey
424
862, 916, 1255
Israel3
420
864, 1046, 1089, 1256
Arabic countries3
838
874
Thailand
930, 939, 5026, 5035
932, 942, 943, 954, 5039
Japan
937
938, 948, 950, 964
Taiwan
933, 1364
949, 970, 1363
Korea
935, 1388
1381, 1383, 1386
People’s Republic of China
Appendix A. Language Support
159
Table 25. Server Code Page to host or iSeriesCCSID Conversion (continued)
Host CCSIDs
Code Page
Territory
1112, 1122
921, 922
Estonia, Latvia, Lithuania
1025
915, 1131, 1251, 1283
Belarus
1123
1124, 1125, 1251
Ukraine
Notes:
1. Code page 1004 is supported as code page 1252.
2. In general, data can be converted from a code page to a CCSID and
backagain to the same code page with no change. The following are the
only exceptionsto that rule:
v In double-byte character set (DBCS) code pages, some data containing
user-definedcharacters may be lost.
v For single-byte code pages defined within mixed-byte code pages,
andfor some newer single-byte code pages, characters that do not exist
in boththe source and the target may be mapped to substitution
characters and thenlost when the data is converted back to the original
code page.
3. For bidirectional languages, a number of special ″BiDi CCSIDS″ have
beendefined by IBM® and are supported by DB2 Connect.
If the bidirectional attributesof the database server are different from those
of the client you can usethese special CCSIDS to manage the difference.
See the DB2 Connect ReleaseNotes for detailed information about how to
set them up for host or iSeriesconnections.
4. This code page is not support of VM systems.
Related concepts:
v “Guidelines for character conversion” in the Administration Guide:
Performance
160
DB2 Connect EE Quick Beginnings
Appendix B. Naming Rules
Naming rules
Unless otherwise specified, all names can include the following characters:
v A through Z. When used in most names, characters A through Z are
converted from lowercase to uppercase.
v 0 through 9
v @, #, $, and _ (underscore)
Names cannot begin with a number or with the underscore character.
Do not use SQL reserved words to name tables, views, columns, indexes, or
authorization IDs.
There are other special characters that might work separately depending on
your operating system and where you are working with DB2. However, while
they might work, there is no guarantee that they will work. It is not
recommended that you use these other special characters when naming
objects in your database.
You also need to consider object naming rules, workstation naming rules,
naming rules in an NLS environment, and naming rules in a Unicode
environment.
Related concepts:
v “General rules for naming objects and users” in the Administration Guide:
Implementation
v “DB2 object naming rules” on page 161
v “Workstation naming rules” on page 165
v “User, userID and group naming rules” on page 163
v “Federated database object naming rules” on page 164
DB2 object naming rules
All objects follow the General Naming Rules. In addition, some objects have
additional restrictions shown below.
© Copyright IBM Corp. 1993-2002
161
Table 26. Database, database alias and instance naming Rules
Objects
Guidelines
v Databases
v Database names must be unique within the location in which they are
cataloged. On UNIX-based implementations of DB2, this location is a
directory path, while on Windows® implementations, it is a logical disk.
v Database aliases
v Instances
v Database alias names must be unique within the system database directory.
When a new database is created, the alias defaults to the database name.
As a result, you cannot create a database using a name that exists as a
database alias, even if there is no database with that name.
v Database, database alias and instance names can have up to 8 bytes.
v On Windows NT, Windows 2000, Windows XP and Windows .NET
systems, no instance can have the same name as a service name.
Note: To avoid potential problems, do not use the special characters @, #,
and $ in a database name if you intend to use the database in a
communications environment. Also, because these characters are not common
to all keyboards, do not use them if you plan to use the database in another
language.
Table 27. Database Object Naming Rules
Objects
Guidelines
v Aliases
Can contain up to 18 bytes except for the following:
v Table names (including view names, summary table names, alias names,
and correlation names), which can contain up to 128 bytes
v Buffer pools
v Columns
v Event monitors
v Indexes
v Package names, which can contain up to 8 bytes
v Schema names, which can contain up to 30 bytes
v Package versions, which can contain up to 64 bytes
v Methods
v Object names can also include:
v Nodegroups
– valid accented characters (such as ö)
v Packages
v Package versions
v Schemas
v Stored procedures
– multibyte characters, except multibyte spaces (for multibyte
environments)
v Package names and package versions can also include periods (.), hyphens
(-), and colons (:).
v Tables
v Table spaces
v Triggers
v UDFs
v UDTs
v Views
Related concepts:
v “Naming rules” on page 161
162
DB2 Connect EE Quick Beginnings
Subconcepts
Delimited identifiers and object names
Keywords can be used. If a keyword is used in a context where it could also
be interpreted as an SQL keyword, it must be specified as a delimited
identifier.
Using delimited identifiers, it is possible to create an object that violates these
naming rules; however, subsequent use of the object could result in errors. For
example, if you create a column with a + or − sign included in the name and
you subsequently use that column in an index, you will experience problems
when you attempt to reorganize the table.
Related concepts:
v “Naming rules” on page 161
User, userID and group naming rules
Table 28. User, userID and group naming rules
Objects
Guidelines
v Group names
v Group names can contain up to 8 bytes.
v User names
v User IDs on UNIX-based systems can
contain up to 8 characters.
v User IDs
v User names on Windows® can contain
up to 30 characters. Windows NT,
Windows 2000, Windows XP and
Windows .NET currently have a
practical limit of 20 characters.
v When not Client authentication,
non-Windows 32-bit clients connecting
to Windows NT, Windows 2000,
Windows XP and Windows .NET with
user names longer than 8 characters are
supported when the user name and
password are specified explicitly.
v Names and IDs cannot:
– Be USERS, ADMINS, GUESTS,
PUBLIC, LOCAL or any SQL
reserved word
– Begin with IBM, SQL or SYS.
– Include accented characters.
Appendix B. Naming Rules
163
Notes:
1. Some operating systems allow case sensitive user IDs and passwords. You
should check your operating system documentation to see if this is the
case.
2. The authorization ID returned from a successful CONNECT or ATTACH is
truncated to 8 characters. An ellipsis (...) is appended to the authorization
ID and the SQLWARN fields contain warnings to indicate truncation.
Related concepts:
v “Naming rules” on page 161
v “Federated database object naming rules” on page 164
Federated database object naming rules
Table 29. Federated database object naming rules
Objects
Guidelines
v Function mappings
v Nicknames, mappings, index specifications, servers, and wrapper names
cannot exceed 128 bytes.
v Index specifications
v Nicknames
v Server and nickname options and option settings are limited to 255 bytes.
v Names for federated database objects can also include:
v Servers
v Type mappings
– Valid accented letters (such as ö)
v User mappings
– Multibyte characters, except multibyte spaces (for multibyte
environments)
v Wrappers
Related concepts:
v “Naming rules” on page 161
Additional schema names information
v User-defined types (UDTs) cannot have schema names longer than 8 bytes.
v The following schema names are reserved words and must not be used:
SYSCAT, SYSFUN, SYSIBM, SYSSTAT.
v To avoid potential migration problems in the future, do not use schema
names that begin with SYS. The database manager will not allow you to
create triggers, user-defined types or user-defined functions using a schema
name beginning with SYS.
v It is recommended that you not use SESSION as a schema name. Declared
temporary tables must be qualified by SESSION. It is therefore possible to
have an application declare a temporary table with a name identical to that
of a persistent table, in which case the application logic can become overly
complicated. Avoid the use of the schema SESSION, except when dealing
with declared temporary tables.
164
DB2 Connect EE Quick Beginnings
Related concepts:
v “Naming rules” on page 161
Additional password information
You may be required to perform password maintenance tasks. Since such
tasks are required at the server, and many users are not able or comfortable
working with the server environment, performing these tasks can pose a
significant challenge. DB2® UDB provides a way to update and verify
passwords without having to be at the server. For example, DB2 for OS/390®
Version 5 supports this method of changing a user’s password. If an error
message SQL1404N “Password expired” is received, use the CONNECT
statement to change the password as follows:
CONNECT TO <database> USER <userid> USING <password>
NEW <new_password> CONFIRM <new_password>
The “Password change” dialog of the DB2 Configuration Assistant (CA) can
also be used to change the password.
Related concepts:
v
v
v
v
v
v
“Naming rules” on page 161
“DB2 object naming rules” on page 161
“Workstation naming rules” on page 165
“User, userID and group naming rules” on page 163
“Federated database object naming rules” on page 164
“Delimited identifiers and object names” on page 163
v “Additional schema names information” on page 164
Workstation naming rules
A workstation name specifies the NetBIOS name for a database server, database
client, or DB2® Personal Edition that resides on the local workstation. This
name is stored in the database manager configuration file. The workstation
name is known as the workstation nname.
In addition, the name you specify:
v Can contain 1 to 8 characters
v Cannot include &, #, or @
v Must be unique within the network
In a partitioned database system, there is still only one workstation nname that
represents the entire partitioned database system, but each node has its own
derived unique NetBIOS nname.
Appendix B. Naming Rules
165
The workstation nname that represents the partitioned database system is
stored in the database manager configuration file for the database partition
server that owns the instance.
Each node’s unique nname is a derived combination of the workstation nname
and the node number.
If a node does not own an instance, its NetBIOS nname is derived as follows:
1. The first character of the instance-owning machine’s workstation nname is
used as the first character of the node’s NetBIOS nname.
2. The next 1 to 3 characters represent the node number. The range is from 1
to 999.
3. The remaining characters are taken from the instance-owning machine’s
workstation nname. The number of remaining characters depends on the
length of the instance-owning machine’s workstation nname. This number
can be from 0 to 4.
For example:
Instance-Owning Machine’s
Workstation nname
Node Number
Derived Node NetBIOS
nname
GEORGE
3
G3ORGE
A
7
A7
B2
94
B942
N0076543
21
N216543
GEORGE5
1
G1RGE5
If you have changed the default workstation nname during the installation, the
workstation nname’s last 4 characters should be unique across the NetBIOS
network to minimize the chance of deriving a conflicting NetBIOS nname.
Related concepts:
v “Naming rules” on page 161
Naming rules in an NLS environment
The basic character set that can be used in database names consists of the
single-byte uppercase and lowercase Latin letters (A...Z, a...z), the Arabic
numerals (0...9) and the underscore character (_). This list is augmented with
three special characters (#, @, and $) to provide compatibility with host
database products. Use special characters #, @, and $ with care in an NLS
environment because they are not included in the NLS host (EBCDIC)
invariant character set. Characters from the extended character set can also be
used, depending on the code page that is being used. If you are using the
166
DB2 Connect EE Quick Beginnings
database in a multiple code page environment, you must ensure that all code
pages support any elements from the extended character set you plan to use.
When naming database objects (such as tables and views), program labels,
host variables, cursors, and elements from the extended character set (for
example, letters with diacritical marks) can also be used. Precisely which
characters are available depends on the code page in use.
Extended Character Set Definition for DBCS Identifiers:
In DBCS environments, the extended character set consists of all the
characters in the basic character set, plus the following:
v All double-byte characters in each DBCS code page, except the double-byte
space, are valid letters.
v The double-byte space is a special character.
v The single-byte characters available in each mixed code page are assigned
to various categories as follows:
Category
Valid Code Points within each Mixed Code Page
Digits
x30-39
Letters
x23-24, x40-5A, x61-7A, xA6-DF (A6-DF for code pages 932 and 942
only)
Special
Characters
All other valid single-byte character code points
Related concepts:
v “Naming rules” on page 161
v “DB2 object naming rules” on page 161
v “Workstation naming rules” on page 165
Naming rules in a Unicode environment
In a UCS-2 database, all identifiers are in multibyte UTF-8. Therefore, it is
possible to use any UCS-2 character in identifiers where the use of a character
in the extended character set (for example, an accented character, or a
multibyte character) is allowed by DB2® UDB.
Clients can enter any character that is supported by their environment, and all
the characters in the identifiers will be converted to UTF-8 by the database
manager. Two points must be taken into account when specifying national
language characters in identifiers for a UCS-2 database:
v Each non-ASCII character requires two to four bytes. Therefore, an n-byte
identifier can only hold somewhere between n/4 and n characters,
Appendix B. Naming Rules
167
depending on the ratio of ASCII to non-ASCII characters. If you have only
one or two non-ASCII (for example, accented) characters, the limit is closer
to n characters, while for an identifier that is completely non-ASCII (for
example, in Japanese), only n/4 to n/3 characters can be used.
v If identifiers are to be entered from different client environments, they
should be defined using the common subset of characters available to those
clients. For example, if a UCS-2 database is to be accessed from Latin-1,
Arabic, and Japanese environments, all identifiers should realistically be
limited to ASCII.
Related concepts:
v “Naming rules” on page 161
v “DB2 object naming rules” on page 161
v “Workstation naming rules” on page 165
168
DB2 Connect EE Quick Beginnings
Appendix C. DB2 Universal Database technical information
Overview of DB2 Universal Database technical information
DB2 Universal Database technical information can be obtained in the
following formats:
v
v
v
v
v
Books (PDF and hard-copy formats)
A topic tree (HTML format)
Help for DB2 tools (HTML format)
Sample programs (HTML format)
Command line help
v Tutorials
This section is an overview of the technical information that is provided and
how you can access it.
Categories of DB2 technical information
The DB2 technical information is categorized by the following headings:
v Core DB2 information
v
v
v
v
v
Administration information
Application development information
Business intelligence information
DB2 Connect information
Getting started information
v Tutorial information
v Optional component information
v Release notes
The following tables describe, for each book in the DB2 library, the
information needed to order the hard copy, print or view the PDF, or locate
the HTML directory for that book. A full description of each of the books in
the DB2 library is available from the IBM Publications Center at
www.ibm.com/shop/publications/order
The installation directory for the HTML documentation CD differs for each
category of information:
htmlcdpath/doc/htmlcd/%L/category
where:
© Copyright IBM Corp. 1993-2002
169
v htmlcdpath is the directory where the HTML CD is installed.
v %L is the language identifier. For example, en_US.
v category is the category identifier. For example, core for the core DB2
information.
In the PDF file name column in the following tables, the character in the sixth
position of the file name indicates the language version of a book. For
example, the file name db2d1e80 identifies the English version of the
Administration Guide: Planning and the file name db2d1g80 identifies the
German version of the same book. The following letters are used in the sixth
position of the file name to indicate the language version:
Language
Arabic
Brazilian Portuguese
Bulgarian
Croatian
Czech
Danish
Dutch
English
Finnish
French
German
Greek
Hungarian
Italian
Japanese
Korean
Norwegian
Polish
Portuguese
Romanian
Russian
Simp. Chinese
Slovakian
Slovenian
Spanish
Swedish
Trad. Chinese
Turkish
Identifier
w
b
u
9
x
d
q
e
y
f
g
a
h
i
j
k
n
p
v
8
r
c
7
l
z
s
t
m
No form number indicates that the book is only available online and does not
have a printed version.
170
DB2 Connect EE Quick Beginnings
Core DB2 information
The information in this category cover DB2 topics that are fundamental to all
DB2 users. You will find the information in this category useful whether you
are a programmer, a database administrator, or you work with DB2 Connect,
DB2 Warehouse Manager, or other DB2 products.
The installation directory for this category is doc/htmlcd/%L/core.
Table 30. Core DB2 information
Name
Form Number
PDF File Name
IBM DB2 Universal Database
Command Reference
SC09-4828
db2n0x80
IBM DB2 Universal Database
Glossary
No form number
db2t0x80
IBM DB2 Universal Database
Master Index
SC09-4839
db2w0x80
IBM DB2 Universal Database
Message Reference, Volume 1
GC09-4840
db2m1x80
IBM DB2 Universal Database
Message Reference, Volume 2
GC09-4841
db2m2x80
IBM DB2 Universal Database
What’s New
SC09-4848
db2q0x80
Administration information
The information in this category covers those topics required to effectively
design, implement, and maintain DB2 databases, data warehouses, and
federated systems.
The installation directory for this category is doc/htmlcd/%L/admin.
Table 31. Administration information
Name
Form number
PDF file name
IBM DB2 Universal Database
Administration Guide:
Planning
SC09-4822
db2d1x80
IBM DB2 Universal Database
Administration Guide:
Implementation
SC09-4820
db2d2x80
IBM DB2 Universal Database
Administration Guide:
Performance
SC09-4821
db2d3x80
IBM DB2 Universal Database
Administrative API Reference
SC09-4824
db2b0x80
Appendix C. DB2 Universal Database technical information
171
Table 31. Administration information (continued)
Name
Form number
PDF file name
IBM DB2 Universal Database
SC09-4830
Data Movement Utilities Guide
and Reference
db2dmx80
IBM DB2 Universal Database
Data Recovery and High
Availability Guide and
Reference
SC09-4831
db2hax80
IBM DB2 Universal Database
Data Warehouse Center
Administration Guide
SC27-1123
db2ddx80
IBM DB2 Universal Database
Federated Systems Guide
GC27-1224
db2fpx80
IBM DB2 Universal Database
Guide to GUI Tools for
Administration and
Development
SC09-4851
db2atx80
IBM DB2 Universal Database
SC27-1121
Replication Guide and Reference
db2e0x80
IBM DB2 Installing and
Administering a Satellite
Environment
GC09-4823
db2dsx80
IBM DB2 Universal Database
SQL Reference, Volume 1
SC09-4844
db2s1x80
IBM DB2 Universal Database
SQL Reference, Volume 2
SC09-4845
db2s2x80
IBM DB2 Universal Database
System Monitor Guide and
Reference
SC09-4847
db2f0x80
Application development information
The information in this category is of special interest to application developers
or programmers working with DB2. You will find information about
supported languages and compilers, as well as the documentation required to
access DB2 using the various supported programming interfaces, such as
embedded SQL, ODBC, JDBC, SQLj, and CLI. If you view this information
online in HTML you can also access a set of DB2 sample programs in HTML.
172
DB2 Connect EE Quick Beginnings
The installation directory for this category is doc/htmlcd/%L/ad.
Table 32. Application development information
Name
Form number
PDF file name
IBM DB2 Universal Database
Application Development
Guide: Building and Running
Applications
SC09-4825
db2axx80
IBM DB2 Universal Database
Application Development
Guide: Programming Client
Applications
SC09-4826
db2a1x80
IBM DB2 Universal Database
Application Development
Guide: Programming Server
Applications
SC09-4827
db2a2x80
IBM DB2 Universal Database
Call Level Interface Guide and
Reference, Volume 1
SC09-4849
db2l1x80
IBM DB2 Universal Database
Call Level Interface Guide and
Reference, Volume 2
SC09-4850
db2l2x80
IBM DB2 Universal Database
Data Warehouse Center
Application Integration Guide
SC27-1124
db2adx80
IBM DB2 XML Extender
Administration and
Programming
SC27-1234
db2sxx80
Business intelligence information
The information in this category describes how to use components that
enhance the data warehousing and analytical capabilities of DB2 Universal
Database.
The installation directory for this category is doc/htmlcd/%L/wareh.
Table 33. Business intelligence information
Name
Form number
PDF file name
IBM DB2 Warehouse Manager
Information Catalog Center
Administration Guide
SC27-1125
db2dix80
IBM DB2 Warehouse Manager
Installation Guide
GC27-1122
db2idx80
Appendix C. DB2 Universal Database technical information
173
DB2 Connect information
The information in this category describes how to access host or iSeries data
using DB2 Connect Enterprise Edition or DB2 Connect Personal Edition.
The installation directory for this category is doc/htmlcd/%L/conn.
Table 34. DB2 Connect information
Name
Form number
PDF file name
APPC, CPI-C, and SNA Sense
Codes
No form number
db2apx80
IBM Connectivity Supplement
No form number
db2h1x80
IBM DB2 Connect Quick
Beginnings for DB2 Connect
Enterprise Edition
GC09-4833
db2c6x80
IBM DB2 Connect Quick
Beginnings for DB2 Connect
Personal Edition
GC09-4834
db2c1x80
IBM DB2 Connect User’s
Guide
SC09-4835
db2c0x80
Getting started information
The information in this category is useful when you are installing and
configuring servers, clients, and other DB2 products.
The installation directory for this category is doc/htmlcd/%L/start.
Table 35. Getting started information
174
Name
Form number
PDF file name
IBM DB2 Universal Database
Quick Beginnings for DB2
Clients
GC09-4832
db2itx80
IBM DB2 Universal Database
Quick Beginnings for DB2
Servers
GC09-4836
db2isx80
IBM DB2 Universal Database
Quick Beginnings for DB2
Personal Edition
GC09-4838
db2i1x80
IBM DB2 Universal Database
Installation and Configuration
Supplement
GC09-4837
db2iyx80
IBM DB2 Universal Database
Quick Beginnings for DB2
Data Links Manager
GC09-4829
db2z6x80
DB2 Connect EE Quick Beginnings
Tutorial information
Tutorial information introduces DB2 features and teaches how to perform
various tasks.
The installation directory for this category is doc/htmlcd/%L/tutr.
Table 36. Tutorial information
Name
Form number
PDF file name
Business Intelligence Tutorial:
Introduction to the Data
Warehouse
No form number
db2tux80
Business Intelligence Tutorial:
Extended Lessons in Data
Warehousing
No form number
db2tax80
Development Center Tutorial
for Video Online using
Microsoft Visual Basic
No form number
db2tdx80
Information Catalog Center
Tutorial
No form number
db2aix80
Video Central for e-business
Tutorial
No form number
db2twx80
Visual Explain Tutorial
No form number
db2tvx80
Optional component information
The information in this category describes how to work with optional DB2
components.
The installation directory for this category is doc/htmlcd/%L/opt.
Table 37. Optional component information
Name
Form number
PDF file name
IBM DB2 Life Sciences Data
GC27-1235
Connect Planning, Installation,
and Configuration Guide
db2lsx80
IBM DB2 Spatial Extender
User’s Guide and Reference
SC27-1226
db2sbx80
IBM DB2 Universal Database
Data Links Manager
Administration Guide and
Reference
SC27-1221
db2z0x80
Appendix C. DB2 Universal Database technical information
175
Table 37. Optional component information (continued)
Name
Form number
PDF file name
IBM DB2 Universal Database
Net Search Extender
Administration and
Programming Guide
Note: HTML for this
document is not installed
from the HTML
documentation CD.
SH12-6740
N/A
Release notes
The release notes provide additional information specific to your product’s
release and FixPak level. They also provides summaries of the documentation
updates incorporated in each release and FixPak.
Table 38. Release notes
Name
Form number
PDF file name
HTML directory
DB2 Release Notes
See note.
See note.
doc/prodcd/%L/db2ir
where %L is the
language identifier.
DB2 Connect Release
Notes
See note.
DB2 Installation Notes Available on
product CD-ROM
only.
See note.
doc/prodcd/%L/db2cr
where %L is the
language identifier.
Available on
product CD-ROM
only.
Note: The HTML version of the release notes is available from the
Information Center and on the product CD-ROMs. To view the ASCII
file:
v On UNIX-based platforms, see the Release.Notes file. This file is
located in the DB2DIR/Readme/%L directory, where %L represents the
locale name and DB2DIR represents:
– /usr/opt/db2_08_01 on AIX
– /opt/IBM/db2/V8.1 on all other UNIX operating systems
v On other platforms, see the RELEASE.TXT file. This file is located in
the directory where the product is installed.
Related tasks:
v “Printing DB2 books from PDF files” on page 177
176
DB2 Connect EE Quick Beginnings
v “Ordering printed DB2 books” on page 178
v “Accessing online help” on page 178
v “Finding product information by accessing the DB2 Information Center
from the administration tools” on page 182
v “Viewing technical documentation online directly from the DB2 HTML
Documentation CD” on page 183
Printing DB2 books from PDF files
You can print DB2 books from the PDF files on the DB2 PDF Documentation
CD. Using Adobe Acrobat Reader, you can print either the entire book or a
specific range of pages.
Prerequisites:
Ensure that you have Adobe Acrobat Reader. It is available from the Adobe
Web site at www.adobe.com
Procedure:
To print a DB2 book from a PDF file:
1. Insert the DB2 PDF Documentation CD. On UNIX operating systems,
mount the DB2 PDF Documentation CD. Refer to your Quick Beginnings
book for details on how to mount a CD on UNIX operating systems.
2. Start Adobe Acrobat Reader.
3. Open the PDF file from one of the following locations:
v On Windows operating systems:
x:\doc\language directory, where x represents the CD-ROM drive letter
and language represents the two-character territory code that represents
your language (for example, EN for English).
v On UNIX operating systems:
/cdrom/doc/%L directory on the CD-ROM, where /cdrom represents the
mount point of the CD-ROM and %L represents the name of the desired
locale.
Related tasks:
v “Ordering printed DB2 books” on page 178
v “Finding product information by accessing the DB2 Information Center
from the administration tools” on page 182
v “Viewing technical documentation online directly from the DB2 HTML
Documentation CD” on page 183
Related reference:
Appendix C. DB2 Universal Database technical information
177
v “Overview of DB2 Universal Database technical information” on page 169
Ordering printed DB2 books
Procedure:
To order printed books:
v Contact your IBM authorized dealer or marketing representative. To find a
local IBM representative, check the IBM Worldwide Directory of Contacts at
www.ibm.com/shop/planetwide
v Phone 1-800-879-2755 in the United States or 1-800-IBM-4YOU in Canada.
v Visit the IBM Publications Center at
www.ibm.com/shop/publications/order
Related tasks:
v “Printing DB2 books from PDF files” on page 177
v “Finding topics by accessing the DB2 Information Center from a browser”
on page 180
v “Viewing technical documentation online directly from the DB2 HTML
Documentation CD” on page 183
Related reference:
v “Overview of DB2 Universal Database technical information” on page 169
Accessing online help
The online help that comes with all DB2 components is available in three
types:
v Window and notebook help
v Command line help
v SQL statement help
Window and notebook help explain the tasks that you can perform in a
window or notebook and describe the controls. This help has two types:
v Help accessible from the Help button
v Infopops
The Help button gives you access to overview and prerequisite information.
The infopops describe the controls in the window or notebook. Window and
notebook help are available from DB2 centers and components that have user
interfaces.
178
DB2 Connect EE Quick Beginnings
Command line help includes Command help and Message help. Command
help explains the syntax of commands in the command line processor.
Message help describes the cause of an error message and describes any
action you should take in response to the error.
SQL statement help includes SQL help and SQLSTATE help. DB2 returns an
SQLSTATE value for conditions that could be the result of an SQL statement.
SQLSTATE help explains the syntax of SQL statements (SQL states and class
codes).
Note: SQL help is not available for UNIX operating systems.
Procedure:
To access online help:
v For window and notebook help, click Help or click that control, then click
F1. If the Automatically display infopops check box on the General page
of the Tool Settings notebook is selected, you can also see the infopop for a
particular control by holding the mouse cursor over the control.
v For command line help, open the command line processor and enter:
– For Command help:
? command
where command represents a keyword or the entire command.
For example, ? catalog displays help for all the CATALOG commands,
while ? catalog database displays help for the CATALOG DATABASE
command.
v For Message help:
? XXXnnnnn
where XXXnnnnn represents a valid message identifier.
For example, ? SQL30081 displays help about the SQL30081 message.
v For SQL statement help, open the command line processor and enter:
– For SQL help:
? sqlstate or ? class code
where sqlstate represents a valid five-digit SQL state and class code
represents the first two digits of the SQL state.
For example, ? 08003 displays help for the 08003 SQL state, while ? 08
displays help for the 08 class code.
– For SQLSTATE help:
Appendix C. DB2 Universal Database technical information
179
help statement
where statement represents an SQL statement.
For example, help SELECT displays help about the SELECT statement.
Related tasks:
v “Finding topics by accessing the DB2 Information Center from a browser”
on page 180
v “Viewing technical documentation online directly from the DB2 HTML
Documentation CD” on page 183
Finding topics by accessing the DB2 Information Center from a browser
The DB2 Information Center accessed from a browser enables you to access
the information you need to take full advantage of DB2 Universal Database
and DB2 Connect. The DB2 Information Center also documents major DB2
features and components including replication, data warehousing, metadata,
Life Sciences Data Connect, and DB2 extenders.
The DB2 Information Center accessed from a browser is composed of the
following major elements:
Navigation tree
The navigation tree is located in the left frame of the browser window.
The tree expands and collapses to show and hide topics, the glossary,
and the master index in the DB2 Information Center.
Navigation toolbar
The navigation toolbar is located in the top right frame of the browser
window. The navigation toolbar contains buttons that enable you to
search the DB2 Information Center, hide the navigation tree, and find
the currently displayed topic in the navigation tree.
Content frame
The content frame is located in the bottom right frame of the browser
window. The content frame displays topics from the DB2 Information
Center when you click on a link in the navigation tree, click on a
search result, or follow a link from another topic or from the master
index.
Prerequisites:
To access the DB2 Information Center from a browser, you must use one of
the following browsers:
v Microsoft Explorer, version 5 or later
v Netscape Navigator, version 6.1 or later
180
DB2 Connect EE Quick Beginnings
Restrictions:
The DB2 Information Center contains only those sets of topics that you chose
to install from the DB2 HTML Documentation CD. If your Web browser returns
a File not found error when you try to follow a link to a topic, you must
install one or more additional sets of topics DB2 HTML Documentation CD.
Procedure:
To find a topic by searching with keywords:
1. In the navigation toolbar, click Search.
In the top text entry field of the Search window, enter two or more terms
related to your area of interest and click Search. A list of topics ranked by
accuracy displays in the Results field.
Entering more terms increases the precision of your query while reducing
the number of topics returned from your query.
3. In the Results field, click the title of the topic you want to read. The topic
displays in the content frame.
2.
To find a topic in the navigation tree:
1. In the navigation tree, click the book icon of the category of topics related
to your area of interest. A list of subcategories displays underneath the
icon.
Continue to click the book icons until you find the category containing
the topics in which you are interested. Categories that link to topics
display the category title as an underscored link when you move the
cursor over the category title. The navigation tree identifies topics with a
page icon.
3. Click the topic link. The topic displays in the content frame.
2.
To find a topic or term in the master index:
1. In the navigation tree, click the “Index” category. The category expands to
display a list of links arranged in alphabetical order in the navigation tree.
2. In the navigation tree, click the link corresponding to the first character of
the term relating to the topic in which you are interested. A list of terms
with that initial character displays in the content frame. Terms that have
multiple index entries are identified by a book icon.
3. Click the book icon corresponding to the term in which you are
interested. A list of subterms and topics displays below the term you
clicked. Topics are identified by page icons with an underscored title.
4. Click on the title of the topic that meets your needs. The topic displays in
the content frame.
Appendix C. DB2 Universal Database technical information
181
Related concepts:
v “Accessibility” on page 189
v “DB2 Information Center for topics” on page 191
Related tasks:
v “Finding product information by accessing the DB2 Information Center
from the administration tools” on page 182
v “Updating the HTML documentation installed on your machine” on page
184
v “Troubleshooting DB2 documentation search with Netscape 4.x” on page
186
v “Searching the DB2 documentation” on page 187
Related reference:
v “Overview of DB2 Universal Database technical information” on page 169
Finding product information by accessing the DB2 Information Center from the
administration tools
The DB2 Information Center provides quick access to DB2 product
information and is available on all operating systems for which the DB2
administration tools are available.
The DB2 Information Center accessed from the tools provides six types of
information.
Tasks
Key tasks you can perform using DB2.
Concepts
Key concepts for DB2.
Reference
DB2 reference information, such as keywords, commands, and APIs.
Troubleshooting
Error messages and information to help you with common DB2
problems.
Samples
Links to HTML listings of the sample programs provided with DB2.
Tutorials
Instructional aid designed to help you learn a DB2 feature.
Prerequisites:
182
DB2 Connect EE Quick Beginnings
Some links in the DB2 Information Center point to Web sites on the Internet.
To display the content for these links, you will first have to connect to the
Internet.
Procedure:
To find product information by accessing the DB2 Information Center from
the tools:
1. Start the DB2 Information Center in one of the following ways:
v From the graphical administration tools, click on the Information
Center icon in the toolbar. You can also select it from the Help menu.
v At the command line, enter db2ic.
2. Click the tab of the information type related to the information you are
attempting to find.
3. Navigate through the tree and click on the topic in which you are
interested. The Information Center will then launch a Web browser to
display the information.
4. To find information without browsing the lists, click the Search icon to the
right of the list.
Once the Information Center has launched a browser to display the
information, you can perform a full-text search by clicking the Search icon
in the navigation toolbar.
Related concepts:
v “Accessibility” on page 189
v “DB2 Information Center for topics” on page 191
Related tasks:
v “Finding topics by accessing the DB2 Information Center from a browser”
on page 180
v “Searching the DB2 documentation” on page 187
Viewing technical documentation online directly from the DB2 HTML
Documentation CD
All of the HTML topics that you can install from the DB2 HTML
Documentation CD can also be read directly from the CD. Therefore, you can
view the documentation without having to install it.
Restrictions:
Appendix C. DB2 Universal Database technical information
183
Because the following items are installed from the DB2 product CD and not
the DB2 HTML Documentation CD, you must install the DB2 product to view
these items:
v Tools help
v DB2 Quick Tour
v Release notes
Procedure:
1. Insert the DB2 HTML Documentation CD. On UNIX operating systems,
mount the DB2 HTML Documentation CD. Refer to your Quick Beginnings
book for details on how to mount a CD on UNIX operating systems.
2. Start your HTML browser and open the appropriate file:
v For Windows operating systems:
e:\Program Files\sqllib\doc\htmlcd\%L\index.htm
where e represents the CD-ROM drive, and %L is the locale of the
documentation that you wish to use, for example, en_US for English.
v For UNIX operating systems:
/cdrom/Program Files/sqllib/doc/htmlcd/%L/index.htm
where /cdrom/ represents where the CD is mounted, and %L is the locale
of the documentation that you wish to use, for example, en_US for
English.
Related tasks:
v “Finding topics by accessing the DB2 Information Center from a browser”
on page 180
v “Copying files from the DB2 HTML Documentation CD to a Web Server”
on page 186
Related reference:
v “Overview of DB2 Universal Database technical information” on page 169
Updating the HTML documentation installed on your machine
It is now possible to update the HTML installed from the DB2 HTML
Documentation CD when updates are made available from IBM. This can be
done in one of two ways:
v Using the Information Center (if you have the DB2 administration GUI
tools installed).
v By downloading and applying a DB2 HTML documentation FixPak .
184
DB2 Connect EE Quick Beginnings
Note: This will NOT update the DB2 code; it will only update the HTML
documentation installed from the DB2 HTML Documentation CD.
Procedure:
To use the Information Center to update your local documentation:
1. Start the DB2 Information Center in one of the following ways:
v From the graphical administration tools, click on the Information
Center icon in the toolbar. You can also select it from the Help menu.
v At the command line, enter db2ic.
2. Ensure your machine has access to the external Internet; the updater will
download the latest documentation FixPak from the IBM server if
required.
3. Select Information Center —> Update Local Documentation from the
menu to start the update.
4. Supply your proxy information (if required) to connect to the external
Internet.
The Information Center will download and apply the latest documentation
FixPak, if one is available.
To manually download and apply the documentation FixPak :
1. Ensure your machine is connected to the Internet.
2. Open the DB2 support page in your Web browser at:
www.ibm.com/software/data/db2/udb/winos2unix/support
3. Follow the link for version 8 and look for the ″Documentation FixPaks″
link.
4. Determine if the version of your local documentation is out of date by
comparing the documentation FixPak level to the documentation level you
have installed. This current documentation on your machine is at the
following level: DB2 v8.1 GA.
5. If there is a more recent version of the documentation available then
download the FixPak applicable to your operating system. There is one
FixPak for all Windows platforms, and one FixPak for all UNIX platforms.
6. Apply the FixPak:
v For Windows operating systems: The documentation FixPak is a self
extracting zip file. Place the downloaded documentation FixPak in an
empty directory, and run it. It will create a setup command which you
can run to install the documentation FixPak.
v For UNIX operating systems: The documentation FixPak is a
compressed tar.Z file. Uncompress and untar the file. It will create a
directory named delta_install with a script called installdocfix. Run
this script to install the documentation FixPak.
Appendix C. DB2 Universal Database technical information
185
Related tasks:
v “Copying files from the DB2 HTML Documentation CD to a Web Server”
on page 186
Related reference:
v “Overview of DB2 Universal Database technical information” on page 169
Copying files from the DB2 HTML Documentation CD to a Web Server
The entire DB2 information library is delivered to you on the DB2 HTML
Documentation CD, so you can install the library on a Web server for easier
access. Simply copy to your Web server the documentation for the languages
that you want.
Procedure:
To copy files from the DB2 HTML Documentation CD to a Web server, use the
appropriate path:
v For Windows operating systems:
E:\Program Files\sqllib\doc\htmlcd\%L\*.*
where E represents the CD-ROM drive and %L represents the language
identifier.
v For UNIX operating systems:
/cdrom:Program Files/sqllib/doc/htmlcd/%L/*.*
where cdrom represents the CD-ROM drive and %L represents the language
identifier.
Related tasks:
v “Searching the DB2 documentation” on page 187
Related reference:
v “Supported DB2 interface languages, locales, and code pages” on page 150
v “Overview of DB2 Universal Database technical information” on page 169
Troubleshooting DB2 documentation search with Netscape 4.x
Most search problems are related to the Java support provided by web
browsers. This task describes possible workarounds.
Procedure:
186
DB2 Connect EE Quick Beginnings
A common problem with Netscape 4.x involves a missing or misplaced
security class. Try the following workaround, especially if you see the
following line in the browser Java console:
Cannot find class
java/security/InvalidParameterException
v On Windows operating systems:
From the DB2 HTML Documentation CD, copy the supplied x:Program
Files\sqllib\doc\htmlcd\locale\InvalidParameterException.class file to
the java\classes\java\security\ directory relative to your Netscape
browser installation, where x represents the CD-ROM drive letter and locale
represents the name of the desired locale.
Note: You may have to create the java\security\ subdirectory structure.
v On UNIX operating systems:
From the DB2 HTML Documentation CD, copy the supplied /cdrom/Program
Files/sqllib/doc/htmlcd/locale/InvalidParameterException.class file to
the java/classes/java/security/ directory relative to your Netscape
browser installation, where cdrom represents the mount point of the
CD-ROM and locale represents the name of the desired locale.
Note: You may have to create the java/security/ subdirectory structure.
If your Netscape browser still fails to display the search input window, try the
following:
v Stop all instances of Netscape browsers to ensure that there is no Netscape
code running on the machine. Then open a new instance of the Netscape
browser and try to start the search again.
v Purge the browser’s cache.
v Try a different version of Netscape, or a different browser.
Related tasks:
v “Searching the DB2 documentation” on page 187
Searching the DB2 documentation
To search DB2’s documentation, you need Netscape 6.1 or higher, or
Microsoft’s Internet Explorer 5 or higher. Ensure that your browser’s Java
support is enabled.
A pop-up search window opens when you click the search icon in the
navigation toolbar of the Information Center accessed from a browser. If you
are using the search for the first time it may take a minute or so to load into
the search window.
Restrictions:
Appendix C. DB2 Universal Database technical information
187
The following restrictions apply when you use the documentation search:
v Boolean searches are not supported. The boolean search qualifiers and and
or will be ignored in a search. For example, the following searches would
produce the same results:
– servlets and beans
– servlets or beans
v Wildcard searches are not supported. A search on java* will only look for
the literal string java* and would not, for example, find javadoc.
In general, you will get better search results if you search for phrases instead
of single words.
Procedure:
To search the DB2 documentation:
1. In the navigation toolbar, click Search.
2. In the top text entry field of the Search window, enter two or more terms
related to your area of interest and click Search. A list of topics ranked by
accuracy displays in the Results field.
Entering more terms increases the precision of your query while reducing
the number of topics returned from your query.
3. In the Results field, click the title of the topic you want to read. The topic
displays in the content frame.
Note: When you perform a search, the first result is automatically loaded into
your browser frame. To view the contents of other search results, click
on the result in results lists.
Related tasks:
v “Troubleshooting DB2 documentation search with Netscape 4.x” on page
186
Online DB2 troubleshooting information
With the release of DB2® UDB Version 8, there will no longer be a
Troubleshooting Guide. The troubleshooting information once contained in this
guide has been integrated into the DB2 publications. By doing this, we are
able to deliver the most up-to-date information possible. To find information
on the troubleshooting utilities and functions of DB2, access the DB2
Information Center from any of the tools.
Refer to the DB2 Online Support site if you are experiencing problems and
want help finding possible causes and solutions. The support site contains a
188
DB2 Connect EE Quick Beginnings
large, constantly updated database of DB2 publications, TechNotes, APAR
(product problem) records, FixPaks, and other resources. You can use the
support site to search through this knowledge base and find possible solutions
to your problems.
Access the Online Support site at
www.ibm.com/software/data/db2/udb/winos2unix/support, or by clicking
the Online Support button in the DB2 Information Center. Frequently
changing information, such as the listing of internal DB2 error codes, is now
also available from this site.
Related concepts:
v “DB2 Information Center for topics” on page 191
Related tasks:
v “Finding product information by accessing the DB2 Information Center
from the administration tools” on page 182
Accessibility
Accessibility features help users with physical disabilities, such as restricted
mobility or limited vision, to use software products successfully. These are the
major accessibility features in DB2® Universal Database Version 8:
v DB2 allows you to operate all features using the keyboard instead of the
mouse. See “Keyboard Input and Navigation”.
v DB2 enables you customize the size and color of your fonts. See “Accessible
Display” on page 190.
v DB2 allows you to receive either visual or audio alert cues. See “Alternative
Alert Cues” on page 190.
v DB2 supports accessibility applications that use the Java™ Accessibility API.
See “Compatibility with Assistive Technologies” on page 190.
v DB2 comes with documentation that is provided in an accessible format.
See “Accessible Documentation” on page 190.
Keyboard Input and Navigation
Keyboard Input
You can operate the DB2 Tools using only the keyboard. You can use keys or
key combinations to perform most operations that can also be done using a
mouse.
Appendix C. DB2 Universal Database technical information
189
Keyboard Focus
In UNIX-based systems, the position of the keyboard focus is highlighted,
indicating which area of the window is active and where your keystrokes will
have an effect.
Accessible Display
The DB2 Tools have features that enhance the user interface and improve
accessibility for users with low vision. These accessibility enhancements
include support for customizable font properties.
Font Settings
The DB2 Tools allow you to select the color, size, and font for the text in
menus and dialog windows, using the Tools Settings notebook.
Non-dependence on Color
You do not need to distinguish between colors in order to use any of the
functions in this product.
Alternative Alert Cues
You can specify whether you want to receive alerts through audio or visual
cues, using the Tools Settings notebook.
Compatibility with Assistive Technologies
The DB2 Tools interface supports the Java Accessibility API enabling use by
screen readers and other assistive technologies used by people with
disabilities.
Accessible Documentation
Documentation for the DB2 family of products is available in HTML format.
This allows you to view documentation according to the display preferences
set in your browser. It also allows you to use screen readers and other
assistive technologies.
DB2 tutorials
The DB2® tutorials help you learn about various aspects of DB2 Universal
Database. The tutorials provide lessons with step-by-step instructions in the
areas of developing applications, tuning SQL query performance, working
with data warehouses, managing metadata, and developing Web services
using DB2.
Before you begin:
Before you can access these tutorials using the links below, you must install
the tutorials from the DB2 HTML Documentation CD-ROM.
190
DB2 Connect EE Quick Beginnings
If you do not want to install the tutorials, you can view the HTML versions of
the tutorials directly from the DB2 HTML Documentation CD. PDF versions of
these tutorials are also available on the DB2 PDF Documentation CD.
Some tutorial lessons use sample data or code. See each individual tutorial for
a description of any prerequisites for its specific tasks.
DB2 Universal Database tutorials:
If you installed the tutorials from the DB2 HTML Documentation CD-ROM,
you can click on a tutorial title in the following list to view that tutorial.
Business Intelligence Tutorial: Introduction to the Data Warehouse Center
Perform introductory data warehousing tasks using the Data
Warehouse Center.
Business Intelligence Tutorial: Extended Lessons in Data Warehousing
Perform advanced data warehousing tasks using the Data Warehouse
Center. (Not provided on CD. You can download this tutorial from the
Downloads section of the Business Intelligence Solutions Web site at
http://www.ibm.com/software/data/bi/.)
Development Center Tutorial for Video Online using Microsoft® Visual Basic
Build various components of an application using the Development
Center Add-in for Microsoft Visual Basic.
Information Catalog Center Tutorial
Create and manage an information catalog to locate and use metadata
using the Information Catalog Center.
Video Central for e-business Tutorial
Develop and deploy an advanced DB2 Web Services application using
WebSphere® products.
Visual Explain Tutorial
Analyze, optimize, and tune SQL statements for better performance
using Visual Explain.
DB2 Information Center for topics
The DB2® Information Center gives you access to all of the information you
need to take full advantage of DB2 Universal Database™ and DB2 Connect™
in your business. The DB2 Information Center also documents major DB2
features and components including replication, data warehousing, the
Information Catalog Center, Life Sciences Data Connect, and DB2 extenders.
The DB2 Information Center accessed from a browser has the following
features:
Appendix C. DB2 Universal Database technical information
191
Regularly updated documentation
Keep your topics up-to-date by downloading updated HTML.
Search
Search all of the topics installed on your workstation by clicking
Search in the navigation toolbar.
Integrated navigation tree
Locate any topic in the DB2 library from a single navigation tree. The
navigation tree is organized by information type as follows:
v Tasks provide step-by-step instructions on how to complete a goal.
v Concepts provide an overview of a subject.
v Reference topics provide detailed information about a subject,
including statement and command syntax, message help,
requirements.
Master index
Access the information in topics and tools help from one master
index. The index is organized in alphabetical order by index term.
Master glossary
The master glossary defines terms used in the DB2 Information
Center. The glossary is organized in alphabetical order by glossary
term.
Related tasks:
v “Finding topics by accessing the DB2 Information Center from a browser”
on page 180
v “Finding product information by accessing the DB2 Information Center
from the administration tools” on page 182
v “Updating the HTML documentation installed on your machine” on page
184
192
DB2 Connect EE Quick Beginnings
Appendix D. 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/region or send
inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any
other country/region 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
© Copyright IBM Corp. 1993-2002
193
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 programs and other programs (including this one) and (ii) the mutual
use of the information that has been exchanged, should contact:
IBM Canada Limited
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
CANADA
Such information may be available, subject to appropriate terms and
conditions, including in some cases payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement, or any equivalent
agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments
may vary significantly. Some measurements may have been made on
development-level systems, and there is no guarantee that these
measurements will be the same on generally available systems. Furthermore,
some measurements may have been estimated through extrapolation. Actual
results may vary. Users of this document should verify the applicable data for
their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements, or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy
of performance, compatibility, or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be
addressed to the suppliers of those products.
194
DB2 Connect EE Quick Beginnings
All statements regarding IBM’s future direction or intent are subject to change
or withdrawal without notice, and represent goals and objectives only.
This information may contain 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 may contain 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.
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.
Appendix D. Notices
195
Trademarks
The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both, and have been used
in at least one of the documents in the DB2 UDB documentation library.
ACF/VTAM
AISPO
AIX
AIXwindows
AnyNet
APPN
AS/400
BookManager
C Set++
C/370
CICS
Database 2
DataHub
DataJoiner
DataPropagator
DataRefresher
DB2
DB2 Connect
DB2 Extenders
DB2 OLAP Server
DB2 Universal Database
Distributed Relational
Database Architecture
DRDA
eServer
Extended Services
FFST
First Failure Support Technology
IBM
IMS
IMS/ESA
iSeries
LAN Distance
MVS
MVS/ESA
MVS/XA
Net.Data
NetView
OS/390
OS/400
PowerPC
pSeries
QBIC
QMF
RACF
RISC System/6000
RS/6000
S/370
SP
SQL/400
SQL/DS
System/370
System/390
SystemView
Tivoli
VisualAge
VM/ESA
VSE/ESA
VTAM
WebExplorer
WebSphere
WIN-OS/2
z/OS
zSeries
The following terms are trademarks or registered trademarks of other
companies and have been used in at least one of the documents in the DB2
UDB documentation library:
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Intel and Pentium are trademarks of Intel Corporation in the United States,
other countries, or both.
196
DB2 Connect EE Quick Beginnings
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc.
in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and
other countries.
Other company, product, or service names may be trademarks or service
marks of others.
Appendix D. Notices
197
198
DB2 Connect EE Quick Beginnings
Index
A
accessibility
features 189
accessing
data
through DB2 Connect 5
using Net.Data or JDBC 12
adding
databases 92, 128
administration server 16
AIX
installation requirements for DB2
Connect Enterprise Edition 31
installing DB2 clients 114
installing DB2 Connect Enterprise
Edition 35
memory requirements for DB2
Connect Enterprise Edition 32
mounting the CD-ROM 34
application development
through Net.Data or JDBC 12
using ODBC 137
using the DB2 Application
Development Client 18
applications
ODBC 139
B
BiDi
language support
binding
utilities 139
158
C
cached address list 104
CCSID (coded character set
identifier)
bidirectional languages 158
bidirectional support
required attributes 156
CD-ROM mounting
AIX 34
HP-UX 43
Linux 50
Solaris Operating
Environment 59
CLI (Call Level Interface)
environmental setup 141
© Copyright IBM Corp. 1993-2002
client profiles
configuring using the import
function 133
creating using the export
function 131
export function 131
import function 131
overview 131
code pages
conversion
exceptions 158
supported 150
Command Center
overview 16
commands
db2licm 67, 69
communication protocols
DRDA host access
configuration 75
communications
Control Center 16
Configuration Assistant (CA)
configuring a connection to the
host database server 89
configuring a connection to the
iSeries database server 89
configuring a database
connection
general 92, 128
configuring client profiles 133
creating client profiles 131
configuring
connection, using the
Configuration Assistant 89
DB2 Connect ESE 19
connecting
to a database using a profile 91,
127
connections
Configuration Assistant 15
DRDA hosts through
communications server 75
overview 15
Control Center
multisite updates 96
overview 16
D
data
conversions
character 158
database administration tools
Control Center 16
overview 16
database connections
configuring
using a profile 91, 127
using Discovery 90, 125
using the Configuration
Assistant (CA) 92, 128
testing 93, 129
database objects
naming rules
NLS 166
Unicode 167
databases
configuring 93, 129
DB2
code pages 150
installing
applying the latest FixPak 65
interface languages 150
locales 150
DB2 Administration Client
operating systems 109
overview 109
DB2 Administration Server (DAS)
overview 16
DB2 Application Development client
operating systems 110
DB2 Application Development Client
overview 18, 110
DB2 clients
accessing databases 12
DB2 Administration Client 109
DB2 Application Development
client 110
DB2 Run-Time Client 110
disk requirements 119
installation requirements 119
AIX 114
HP-UX 115
Linux 116
Solaris Operating
Environment 117
Windows 113
199
DB2 clients (continued)
installing
UNIX 122
Windows 113, 120
memory requirements 120
overview 12, 15, 109
DB2 Connect
migrating from previous
versions 63
non-Administrator
installation 29
overview 5
preparing DB2 for VSE & VM for
connections 85
Sysplex support 101
DB2 Connect Enterprise Edition
installation requirements
AIX 31
HP-UX 39
Linux 47
Solaris Operating
Environment 55
Windows 23
installing
AIX 35
HP-UX 44
Linux 50
Solaris Operating
Environment 59
Windows 26
installing and configuring 19
memory requirements
AIX 32
HP-UX 40
Linux 48
Solaris Operating
Environment 56
Windows 24
product description 3
DB2 Connect license key
installing using the db2licm
command 67
installing using the License
Center 68
DB2 Connect PE
product description 3
DB2 documentation search
using Netscape 4.x 186
DB2 Information Center 191
DB2 objects
naming rules 161
DB2 Run-Time Client
overview 110
DB2 Setup wizard
language identifiers 155
200
DB2 tutorials 190
DB2 Universal Database
Control Center 16
DB2 Performance Monitor 16
DB2 Snapshot Monitor 12
platforms supported 16
Visual Explain 16
DB2 Universal Database for OS/390
and z/OS
updating system tables 74
DB2CONNECT_IN_APP_PROCESS
registry variable 101
db2licm command 67, 69
DBCS (double-byte character set)
naming rules 166
developing applications
using Net.Data or JDBC 12
directory schema
extending
on Windows 2000 and
Windows .NET 28
disability 189
discovery feature
configuring a database
connection 90, 125
disk requirements
DB2 Connect Enterprise
Edition 25
DB2 Connect Personal
Edition 33, 41, 49, 57
distributed unit of work
multisite updates 95
supported servers 95
two-phase commit 95
E
export function
creating client profiles 131
exporting
profiles 134
F
federated databases
object naming rules 164
fixed disks
hardware requirements 25, 33,
41, 49, 57
FixPak
applying 65
G
groups
naming rules 163
DB2 Connect EE Quick Beginnings
H
hardware requirements
fixed disk 25, 33, 41, 49, 57
HP-UX
installation requirements for DB2
Connect Enterprise Edition 39
installing DB2 clients 115
installing DB2 Connect Enterprise
Edition 44
kernel configuration
parameters 42
memory requirements for DB2
Connect Enterprise Edition 40
mounting the CD-ROM 43
I
import function
configuring client profiles 133
importing
profiles 134
installing
client 25, 33, 41, 49, 57
DB2 Connect Enterprise
Edition 19
DB2 for Linux on S/390 52
server 25, 33, 41, 49, 57
interface languages 150
changing
on UNIX 150
on Windows 149
iSeries
configuring DB2 Connect 83
configuring DB2 for DB2
Connect 83
DSPNETA 83
DSPRDBDIRE 83
WRKLIND 83
K
kernel configuration parameters
for Solaris 58
recommended settings for
HP-UX 42
L
language identifiers, DB2 Setup
wizard 155
languages
bidirectional support 158
License Center
installing
DB2 Connect license key 68
setting the license type
using the db2licm
command 69
License Center (continued)
setting the license type
(continued)
using the License Center 69
Linux
installation requirements
DB2 Connect Enterprise
Edition 47
installing
DB2 clients 116
DB2 Connect Enterprise
Edition 50
mounting the CD-ROM 50
memory requirements
DB2 Connect Enterprise
Edition 48
locales
supported 150
M
manually adding databases 92, 128
migrating
DB2 Connect 63
Multisite Update Wizard 96
multisite updates
Control Center 96
distributed unit of work
(DUOW) 95
enabling 95
sync point manager 98
testing 97
N
naming conventions
general 161
naming rules
delimited identifiers and object
names 163
for DB2 objects 161
for federated database
objects 164
for users, userIDs and
groups 163
for workstations 165
national languages 166
schema names 164
Unicode 167
national language support (NLS)
bidirectional CCSID support 156
converting character data 158
Net.Data
accessing DB2 data 12
connecting to Internet 12
O
ODBC (open database connectivity)
enabled applications 139
setting up UNIX
environment 142
online
help, accessing 178
ordering DB2 books 178
OS/390
configuring DB2 Universal
Database 74
P
passwords
updating 165
verifying 165
printed books, ordering 178
product packaging 3
profile
exporting 134
importing 134
S
S/390, installing DB2 for Linux 52
schema names
description 164
servers
communications 16
settings
CLI environment
run-time support 141
Windows 144
Solaris Operating Environment
installation
DB2 clients 117
DB2 Connect Enterprise
Edition 59
requirements, DB2 Connect
Enterprise Edition 55
kernel configuration
parameters 58
memory requirements
for DB2 Connect Enterprise
Edition 56
mounting the CD-ROM 59
SQL
keywords 163
SQL (Structured Query Language)
viewing with Visual Explain 16
sync point manager (SPM)
scenarios 98
Sysplex
APPC connections 103
configuration requirements 103
considerations for zSeries 101
Sysplex (continued)
DB2 Connect support 101
fault tolerance 104
load balancing 104
priority information 104
using 104
system configuration
with DB2 Connect 5
T
TCP/IP
configuration
host connections 75
DB2 UDB for OS/390 and z/OS
configuration 73
territory codes
page support 158
transaction processing monitors
multisite updates 95
transactions
distributed
supported servers 95
multisite updates 95
troubleshooting
DB2 documentation search 186
online information 188
tutorials 190
two-phase commit
enabling 95
U
Unicode (UCS-2)
identifiers 167
naming rules 167
units of work (UOW)
distributed 95
UNIX
changing the DB2 interface
language 150
installing DB2 clients 122
setting up ODBC
environment 142
user IDs
naming rules 163
utilities
binding 139
V
Visual Explain
overview 16
VSE and VM for connections
preparing DB2 from DB2
Connect 85
VTAM
preparing OS/390 or z/OS for
DB2 Connect 73
Index
201
VTAM (continued)
sample definitions 78
sample logon mode table
entry 78
sample PU and LU
definitions 78
W
Windows
changing the DB2 interface
language 149
CLI environment 144
installation requirements
DB2 Connect Enterprise
Edition 23
installing
DB2 clients 113, 120
DB2 Connect Enterprise
Edition 26
DB2 Connect,
non-Administrator 29
memory requirements
DB2 Connect Enterprise
Edition 24
setting up CLI environment 144
Windows .NET, extending the
directory schema 28
Windows 2000
extending the directory
schema 28
wizards
Multisite Update 96
workstations
(nname), naming rules 165
Z
z/OS
configuring DB2 Universal
Database 74
202
DB2 Connect EE Quick Beginnings
Contacting IBM
In the United States, call one of the following numbers to contact IBM:
v 1-800-237-5511 for customer service
v 1-888-426-4343 to learn about available service options
v 1-800-IBM-4YOU (426-4968) for DB2 marketing and sales
In Canada, call one of the following numbers to contact IBM:
v 1-800-IBM-SERV (1-800-426-7378) for customer service
v 1-800-465-9600 to learn about available service options
v 1-800-IBM-4YOU (1-800-426-4968) for DB2 marketing and sales
To locate an IBM office in your country or region, check IBM’s Directory of
Worldwide Contacts on the web at www.ibm.com/planetwide
Product information
Information regarding DB2 Universal Database products is available by
telephone or by the World Wide Web at
www.ibm.com/software/data/db2/udb
This site contains the latest information on the technical library, ordering
books, client downloads, newsgroups, FixPaks, news, and links to web
resources.
If you live in the U.S.A., then you can call one of the following numbers:
v 1-800-IBM-CALL (1-800-426-2255) to order products or to obtain general
information.
v 1-800-879-2755 to order publications.
For information on how to contact IBM outside of the United States, go to the
IBM Worldwide page at www.ibm.com/planetwide
© Copyright IBM Corp. 1993-2002
203
Part Number: CT16BNA
GC09-4833-00
(1P) P/N: CT16BNA
Printed in the United States of America
on recycled paper containing 10%
recovered post-consumer fiber.
®
™
IBM DB2 Connect
Spine information:
DB2 Connect EE Quick Beginnings
Version 8
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement