The CATALOG TCP/IP NODE command syntax is as follows:

catalog [ ADMIN ] [ TCP/IP protocol ] node [ Node-name ] remote [ 
Hostname ] server [ Service-name ] with [ comment-string ]

Example:

db2 catalog tcpip node wasa-host remote wasa server 4001 with "catalog 
remote host wasa:4001 to local alias wasa-host"

CATALOG TCP/IP NODE takes the following parameters:

ADMIN

Specifies that a TCP/IP administration server node is to be cataloged. This parameter cannot be specified if the SECURITY SOCKS parameter is specified.

TCP/IP Protocol

Specifies TCP/IP protocol used, could be: TCPIP, TCPIP4, TCPIP6

Node-name

The nodename of the TCPIP, TCPIP4, or TCPIP6 node represents a local nickname you can set for the machine that contains the database you want to catalog. Only specify TCPIP4 when specifying an IPv4 IP address, and only specify TCPIP6 when specifying an IPv6 IP address.

Hostname

The hostname or the IP address of the node where the target database resides. IP address can be an IPv4 or IPv6 address. The hostname is the name of the node that is known to the TCP/IP network. The maximum length of the hostname is 255 characters.

Service-name

Specifies the service name or the port number of the server database manager instance. The maximum length is 14 characters. This parameter is case sensitive.

If a service name is specified, the services file on the client is used to map the service name to a port number. A service name is specified in the server's database manager configuration file, and the services file on the server is used to map this service name to a port number. The port number on the client and the server must match.

A port number, instead of a service name, can be specified in the database manager configuration file on the server, but this is not recommended. If a port number is specified, no service name needs to be specified in the local services file.