As part of the instance creation, the installer creates three users identified as 

db2inst1

, 

db2fenc1

, and 

dasadm1

. If you do not want to use the default user IDs, 

you can create the user IDs and groups ahead of time and use the IDs during 

creating the instance. The installer will also add the following entry to the 

/etc/services

 file in order to allow communication from DB2 clients:

db2c_db2inst1 50000 

Where 

db2c_db2inst1

 indicates the service name, and 

50000

 indicates the port 

number. Subsequent instances may be created on the same server simply by 

using one of the methods introduced above.

4.1.4  Client setup on Linux

This section discusses installation and configuration of DB2 UDB clients to 

access a remote DB2 UDB server. DB2 UDB provides three types of clients free 

of charge:

The Run Time Client 

The Administration Client

The Application Development Client

All clients are supported on Linux, AIX, HP UX, Solaris, and Windows operating 

systems.

Note:

 Typically, for a production environment, DB2 clients are installed on 

physically separate machines from the DB2 server machine. However, for an 

application development environment, it may be useful to have everything 

such as the DB2 database server plus the clients on the same machine.

To access a remote DB2 UDB database, you can either run the easy to use 

graphical tool 

Configuration Assistant 

or use the catalog commands to provide 

entries for the following three directories: 

NODE directory: A list of remote DB2 instances

ADMIN NODE directory: A list of remote DB2 Administration servers

DATABASE directory: A list of databases

To access a remote DB2 UDB database, you first catalog the DB2 UDB node, 

which is the server where the database resides, then catalog the database. See 

Example 4 2.

Example 4 2   Cataloging node and database 

    catalog database node

82 

MySQL to DB2 UDB Conversion Guide