Sample Steps for DB2® Administration Client Configuration on UNIX™

The following illustrates some sample steps you may wish to follow when configuring your DB2® connectivity using the Administration client on UNIX™. For full details, refer to the DB2® manual Install/Use DB2® Clients for xxx where xxx is your UNIX™ operating system. The following steps assume you are installing the Administration client for the server machine running on UNIX™ and using TCP/IP.

Install the DB2® Administration client software.
Ensure the server machine can resolve the DB2® server TCP/IP host address. For example, you should be able to ping the server. If it can't, either update the Domain Name server to include the DB2® server name and address or add an entry to your server machine's /etc/hosts file.
Ensure the DB2® server has enabled the TCP/IP protocol through the DB2COMM environment variable. This variable may indicate multiple protocols. Make certain it includes TCPIP. This variable must be set at the time the DB2® server is started.
Ensure the services file on the DB2® server machine contains an entry for TCP/IP support for each database manager instance you plan on accessing.
```
db2inst1c   3700/tcp	
# DB2 connection service port
db2inst1i   3701/tcp	
# DB2 interrupt connection service port
```
In this example, db2inst1c is the value of the service_name parameter and db2inst1i is arbitrary. 3700 and 3701 are the port numbers for the connection and interrupt port, and TCP is the protocol. The port number 3700 is arbitrary, but must be unique within the file. The second port number must also be unique and be equal to the first number plus one. These same numbers must be used when configuring the services file on the server machine.
On the server machine, catalog the DB2® server and database. To catalog the server, use the DB2® command line processor on the server machine and enter the command:
```
CATALOG TCPIP NODE nodename REMOTE hostname SERVER servicename
```
In this example, nodename is a name you use to refer to this connection, hostname is the TCP/IP name of the DB2® server machine, and servicename is the instance name you entered in the services file (you only need to do this once using the first port even if you also entered an interrupt connection service port in the services file).
Catalog the database using the following command:
```
CATALOG DATABASE databasename AS local_database_alias AT NODE nodename
```
In this example, databasename is the name of the database on the DB2® server, local_database_alias is a name you choose when you wish to connect to the database from the server machine, and nodename is the name you used in the previous CATALOG TCP/IP command.
Exit and restart the DB2® command line processor. Connect to the DB2® database with the following command:
```
CONNECT TO local_database_alias USER username USING password
```
In this example, local_database_alias is the alias you cataloged and username is a valid DB2® user name.
Verify connectivity to DB2® by running the DCTEST program found in the Domino® program directory. This program will prompt you for the database name or database alias, userid, and password.