This parameter contains the name of the TCP/IP port which a database server will use to await communications from remote client nodes. This name must be the first of two consecutive ports reserved for use by the database manager; the second port is used to handle interrupt requests from down-level clients.
In order to accept connection requests from a database client using TCP/IP, the database server must be listening on a port designated to that server. The system administrator for the database server must reserve a port (number n) and define its associated TCP/IP service name in the services file at the server. If the database server needs to support requests from down-level clients, a second port (number n+1, for interrupt requests) needs to be defined in the services file at the server.
The database server port (number n) and its TCP/IP service name need to be defined in the services file on the database client. Down-level clients also require the interrupt port (number n+1) to be defined in the client's services file.
The location of the services file depends on your operating environment. For example:
The svcename parameter should be set to the service name associated with the main connection port so that when the database server is started, it can determine on which port to listen for incoming connection requests. If you are supporting or using a down-level client, the service name for the interrupt port is not saved in the configuration file. The interrupt port number can be derived based on the main connection port number (interrupt port number = main connection port + 1).
See the Installing and Configuring DB2 Clients for more information about setting up TCP/IP for database servers.