Application Building Guide

Enabling Communications on the Server

This section explains how to connect to DB2 Universal Database servers.

Before you begin installing, cataloging, and binding the sample database, you should ensure that the server is operational and configured to support the protocol being cataloged. Do the following on the server:

Ensure that the db2comm environment variable is set. For example, enter:
```
   db2set DB2COMM=tcpip
```
Ensure that the protocol for TCP/IP support is configured.
Refer to your platform's Quick Beginnings book for instructions on adding the TCP/IP settings to the Services file.
Start the database instance by entering:
```
   db2start
```

Windows NT

In a DB2 for Windows NT production system, you have to start the database instance as a service. The steps are as follows:

If using communications protocols, ensure that the db2comm environment variable is set in the System Environment Variables section of the Windows NT control panel.
Start the security service. This can be done automatically (see the note below), or you can start this service manually using the following command:
```
   NET START DB2NTSECSERVER
```
Start the instance by entering:
```
   db2start
```

Note: Starting the Security Service automatically. Normally the only time you would want to set the security service to start automatically is if the workstation is acting as a DB2 client connecting to a server that is configured for Client Authentication. To have the security service start automatically, do the following:

Click on the "Start" button.
Click on "Settings".
Click on "Control Panel".
In the Control Panel, click on "Services".
In the Services window, highlight "DB2 Security Server".
If it does not have the settings "Started" and "Automatic" listed, click on "Startup".
Click on "Automatic".
Click on "OK".
Reboot your machine to have the settings take effect.

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

[ DB2 List of Books | Search the DB2 Books ]