Installation and Configuration Supplement

Setting the DB2COMM Registry Parameter

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

You must update the db2comm registry variable with the protocol that you now want to support, if you have:

Deselected a detected protocol during installation;
Added a communications protocol to your network since installation;
Want to use a communications protocol that could not be detected by the DB2 setup program.

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

For your DB2 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 32-bit operating systems only)
tcpip: starts TCP/IP support

To avoid problems with the Control Center and the Client Configuration Assistant, ensure that the DB2COMM parameter is set in the DB2 registry using the db2set command. It is not recommended that you use any other mechanism to set the DB2COMM value.

For more information on the DB2 registry, refer to the Administration Guide.

To set the db2comm registry variable for the current instance, enter 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 the following command:

   db2set DB2COMM=appc,tcpip
   db2stop
   db2start

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

If you are setting up communications for the Administration Server, enter the db2set command:
db2set DB2COMM=appc,tcpip -i DB2DAS00 db2admin stop db2admin start

where:
DB2DAS00 represents the name of the Administration Server. If you are not sure of the Administration Server name, enter the following command:
db2set DB2ADMINSERVER

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

If there are problems starting a protocol's connection managers, a warning message appears and the error messages are logged in the db2diag.log file.
For more information on the db2diag.log file, refer to the Troubleshooting Guide.

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 Server.
TCP/IP - see Configuring TCP/IP on the Server.
NetBIOS - see Configuring NetBIOS on the Server.
IPX/SPX - see Configuring IPX/SPX on the Server.
APPC - see Configuring APPC on the Server.

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

[ DB2 List of Books | Search the DB2 Books ]