Quick Beginnings

Setting the DB2COMM Registry Value

Your DB2 Connect server can support multiple communication protocols concurrently; however, you only need to enable the protocols that you want to use.

If you deselected a detected protocol during installation, did not install the Control Center (for DB2 for OS/2 or Windows NT servers), or have added a communication protocol to your network since installation, you must update the DB2COMM registry value with the protocol that you now want to support.

The DB2COMM registry value determines which protocol's connection managers will be enabled when the database manager is started. You can set this value for multiple communication protocols by separating the keywords with commas.

For your DB2 Connect server, DB2COMM can be any combination of the following keywords:

appc: starts APPC support
ipxspx: starts IPX/SPX support
netbios: starts NetBIOS support
npipe: starts NAMED PIPE support (for Windows NT servers) or Local support (for OS/2 servers)
tcpip: starts TCP/IP support

To set the DB2COMM registry value for the current instance, issue the db2set DB2COMM= protocol_names command. Change the protocol_names parameter to reflect those protocols that you want to start when the database manager is started.

For example, to set the database manager to start connection managers for the APPC and TCP/IP communication protocols, enter:

   db2set DB2COMM=appc,tcpip
   db2stop
   db2start

If you are setting up communications for the Administration Server, use the db2set command as follows:

   db2set DB2COMM=appc,tcpip -i DB2DAS00
   db2admin stop
   db2admin start

where:

DB2DAS00

The name of the Administration Server's instance. If you are not sure of the instance name, issue the following command to resolve it:

db2set DB2ADMINSERVER

When the db2start command is reissued, connection managers for the protocols specified by the DB2COMM registry value are started.

If there are problems starting a protocol's connection managers, a warning message is displayed and the error messages are logged in the db2diag.log file. The location of this file depends on your operating system.

UNIX-based Platforms
$HOME/sqllib/db2dump directory, where $HOME is home directory of the instance owner.
Other Platforms
x:\sqllib\%db2instance% directory, where x: is the drive that the client is installed and %db2instance% represents the DB2 instance.

Refer to the Troubleshooting Guide for information on the db2diag.log file.

If DB2COMM is undefined or set to null, no protocol connection managers are started when the database manager is started.

For more information on setting DB2 parameters, see "Controlling the DB2 Profile Registry".

You are now ready to configure the server workstation to use any of the following communication protocols:

Named Pipes - see "Configuring Named Pipes on the DB2 Connect Server"
TCP/IP - see "Configuring TCP/IP on the DB2 Connect Server to Accept Clients"
NetBIOS - see "Configuring NetBIOS on the DB2 Connect Server"
IPX/SPX - see "Configuring IPX/SPX on the DB2 Connect Server"
APPC - see "Configuring APPC on the DB2 Connect Server to Accept Clients" to configure DB2 Connect to accept inbound clients requests

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

[ DB2 List of Books | Search the DB2 Books ]