Setting communication protocols for a Db2 instance

Setting communication protocols for a Db2 instance is part of the main task of configuring TCP/IP or SSL communications for a Db2 instance.

Before you begin

To perform this task you require SYSADM authority.

About this task

You can set communication protocols for the current Db2 instance by using the DB2COMM registry variable. If the DB2COMM registry variable is undefined or set to null, then no TCP/IP connection managers are started. An exception is when DB2COMM=TCPIP is not set in the database manager configuration (DBM CFG) file but SVCENAME is set, which starts the TCP/IP connection manager in restricted mode.

For information on the restricted mode, see svcename - TCP/IP service name configuration parameter.

The DB2COMM registry variable can be set with the following keywords:

tcpip: starts TCP/IP support
ssl: starts SSL support

Procedure

To set the communication protocol for the instance:

Enter the db2set DB2COMM command from the Db2 command window:

     db2set DB2COMM=tcpip

Example

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

   db2set DB2COMM=tcpip
   db2stop
   db2start