Command

Command description

db2stop 

 Stop DB2

db2updv8 

 Update database to Version 8 current level

sqlj 

 DB2 SQLJ translator

dynexpln 

 Explain dynamic SQL (deprecated)

1.1.4  DB2 database access

In this section the following topics are discussed:

DB2 clients

Application access

DB2 application programming interfaces

DB2 clients

To access a DB2 UDB database, a DB2 client has to be installed on the client 

system. IBM offers three types of DB2 clients:

Run time Client

This client provides you access to DB2 UDB servers with application 

interfaces such as JDBC, SQLJ, ODBC, CLI, and OLE DB. This client can be 

used if no DB2 server administration has to be done from this client.

Administration Client

The Administration Client has all features of the DB2 Run Time Client plus 

tools to administer a DB2 Server. 

Application Development Client

This client provides a collection of graphical and non graphical tools for 

developing applications. It includes all components of the DB2 Administration 

Client.

For client server communication, DB2 supports several communication protocols 

like TCP/IP, APPC, NPIPE, NetBIOS, etc. Most protocols are automatically 

detected and configured during an instance creation. The DB2COMM registry 

variable identifies the protocol detected in a server. To enable a specific protocol, 

the 

db2set DB2COMM

 command must be executed. For TCP/IP, a unique port 

address has to be specified in the database manager configuration. This port is 

registered in the services file. To reserve port 50000 with the service name 

db2cidb2, for example, the entry in services file is:

db2icdb2 50000/tcp

 Chapter 1. Introduction 

21