Quick Beginnings for DB2 Universal Database for UNIX

Configuration Steps for DB2 Universal Database Server

This section describes the steps and conditions required to configure a DB2 Universal Database server to accept connection from host and AS/400 database clients.

Before you begin, you must determine whether your connection will use the APPC communication protocol, or the TCP/IP communication protocol, or both.

Platform: Supported Protocols
AIX: TCP/IP, APPC, APPC Two Phase Commit
HP-UX: TCP/IP
SCO: TCP/IP
SINIX: TCP/IP
Solaris: TCP/IP, APPC
OS/2: TCP/IP, APPC, APPC Two Phase Commit
Windows NT: TCP/IP, APPC, APPC Two Phase Commit

Notes:

The protocol you choose may depend on the host or AS/400 database client version:
- APPC is supported by all host or AS/400 database client versions
- TCP/IP is supported on the following host or AS/400 database client versions
  - DB2 for OS/390 Version 5 or higher
  - DB2 for AS/400 Version 4 Release 2 or higher
  - DB2 for VM Version 6 or higher.
Considerations for Multisite Update (Two Phase Commit)
If your host or AS/400 application required Multisite Update support (two-phase commit), you should note the following:

APPC Connections (SNA)
DB2 Universal Database Enterprise Edition for OS/2, AIX, and Windows NT and DB2 Extended Enterprise Edition for AIX, and Windows NT provide support for SNA two phase commit with host and AS/400 database clients. The exception is AS/400 clients which cannot have Multisite Update support with DB2 for AIX Enterprise Edition or Extended Enterprise Edition.
TCP/IP Connections
Multisite Update is not supported with any host or AS/400 database clients. Remote Unit of Work (RUW) is supported (one phase commit)
To use APPC on AIX, the optional communication support component for SNA (db2_05_00.cs.sna) must also be installed.
To use APPC on Solaris, the optional communication support component for SNA (db2cssna) must also be installed.

Configuring DB2 Universal Database Servers for Host or AS/400 Client Access

This section gives an overview of the steps necessary to configure DB2 Universal Database to allow connectivity from host or AS/400 database clients. The example shows how to configure a connection from a DB2 for MVS/ESA or DB2 for OS/390 client to a DB2 Universal Database server:

Ensure DB2 for MVS/ESA or DB2 for OS/390 is installed and operational on the host.
Refer to the DB2 Connectivity Supplement for information on the configuration required for the DB2 for MVS/ESA or DB2 for OS/390 AR.
If you use APPC, ensure VTAM is installed and operational on the host.
Refer to the DB2 Connect Enterprise Edition Quick Beginnings and the DB2 for OS/390 V5 Installation Guide manual for information on configuring the DB2 for MVS/ESA or DB2 for OS/390 AR.
Set up the DB2 server communications, if required. (Typically, DB2 server communications are set up as part of the DB2 installation. However, complete details are provided in Chapter 26. Setting up Communications on the Server Using the Command Line Processor. If you want to use Multisite Update, refer to the chapter entitled Enabling Multisite Update in the DB2 Connect Enterprise Edition Quick Beginnings manual.) DB2 Connect is not required for host or AS/400 database client connections to DB2 Universal Database; however, the steps to enable Multisite Update are common with DB2 Connect.
Update the tables at the DB2 for MVS/ESA or DB2 for OS/390 host.
Refer to the DB2 Connectivity Supplement for more information.
Stop and restart the DB2 Universal Database instance named in DB2SERVICETPINSTANCE (that is, the instance in which you updated the database configuration parameter(s) tpname and/or svcename. Enter the following commands:
```
   db2stop
   db2start
```
Test the host-server DRDA connection by logging onto TSO and using DB2I/SPUFI.

For information on setting up two-phase commit, refer to the on-line DB2 Connect Enterprise Edition Quick Beginnings manual.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]