Command Reference

CATALOG TCP/IP NODE

Adds a Transmission Control Protocol/Internet Protocol (TCP/IP) node entry to the node directory. The TCP/IP communications protocol is used to access the remote node.

Authorization

One of the following:

• sysadm
• sysctrl

Required Connection

None. Directory operations affect the local directory only.

Command Syntax

>>-CATALOG--+-------+--TCPIP NODE--nodename--REMOTE--hostname---> '-ADMIN-' (1) >------------SERVER--service-name---+----------------+----------> '-SECURITY SOCKS-' >-----+---------------------------------+-----------------------> '-REMOTE_INSTANCE--instance-name--' >-----+----------------------+----------------------------------> '-SYSTEM--system-name--' >-----+--------------------------------+------------------------> '-OSTYPE--operating-system-type--' >-----+-------------------------+------------------------------>< '-WITH--"comment-string"--' Notes: SERVER must not be specified for ADMIN nodes, but is mandatory for non-ADMIN nodes.

Command Parameters

ADMIN

Specifies that a TCP/IP administration server node is to be cataloged.

NODE nodename

A local alias for the node to be cataloged. This is an arbitrary name on the user's workstation, used to identify the node. It should be a meaningful name to make it easier to remember. The name must conform to database manager naming conventions (see Appendix B, Naming Conventions).

REMOTE hostname

The host name of the node where the target database resides. The host name is the name of the node that is known to the TCP/IP network. Maximum length is 255 characters.

SERVER service-name

Specifies the service name or the port number of the server database manager instance.

The CATALOG TCPIP NODE command is run on a client.

• 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 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.

  Note:

  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, it must match the port number associated with the service name specified in the server's database manager configuration file. No service name needs to be specified in the local TCP/IP services file.

The value of service-name is used as a key to search the local services file for the associated port number. If a matching entry is not found, and service-name is numeric, the value is interpreted as the port number.

Maximum length is 14 characters. This parameter is case sensitive.

Note:

This parameter must not be specified for ADMIN nodes. The value on ADMIN nodes is always 523.

SECURITY SOCKS

Specifies that the node will be SOCKS-enabled.

The following environment variables are mandatory and must be set to enable SOCKS:

SOCKS_NS

The Domain Name Server for resolving the host address of the SOCKS server. This should be an IP address.

SOCKS_SERVER

The fully qualified host name or the IP address of the SOCKS server. If the SOCKSified DB2 client is unable to resolve the fully qualified host name, it assumes that an IP address has been entered.

One of the following conditions should be true:

• The SOCKS server should be reachable via the domain name server
• It should be listed in the hosts file. The location of this file is described in the TCP/IP documentation.
• It should be in an IP address format.

If these environment variables are set after a db2start has been issued, it is necessary to issue a TERMINATE command.

REMOTE_INSTANCE instance-name

Specifies the name of the server instance to which an attachment is being made.

SYSTEM system-name

Specifies the DB2 system name that is used to identify the server machine.

OSTYPE operating-system-type

Specifies the operating system type of the server machine. Valid values are: OS2, AIX, WIN95, NT, HPUX, SUN, MVS, OS400, VM, VSE, SNI, SCO, SGI, LINUX and DYNIX.

WITH "comment-string"

Describes the node entry in the node directory. Any comment that helps to describe the node can be entered. Maximum length is 30 characters. A carriage return or a line feed character is not permitted. The comment text must be enclosed by single or double quotation marks.

Examples

   db2 catalog tcpip node db2tcp1 remote tcphost server db2inst1
      with "A remote TCP/IP node"
 
   db2 catalog tcpip node db2tcp2 remote 9.21.15.235 server db2inst2
      with "TCP/IP node using IP address"

Usage Notes

The database manager creates the node directory when the first node is cataloged (that is, when the first CATALOG...NODE command is issued). On an OS/2 client or a Windows client, it stores and maintains the node directory in the instance subdirectory where the client is installed. On an AIX client, it creates the node directory in the DB2 installation directory.

List the contents of the local node directory using LIST NODE DIRECTORY.

Note:

If directory caching is enabled (see the configuration parameter dir_cache in GET DATABASE MANAGER CONFIGURATION), database, node, and DCS directory files are cached in memory. An application's directory cache is created during its first directory lookup. Since the cache is only refreshed when the application modifies any of the directory files, directory changes made by other applications may not be effective until the application has restarted.

To refresh the CLP's directory cache, use TERMINATE. To refresh DB2's shared cache, stop (db2stop) and then restart (db2start) the database manager. To refresh the directory cache for another application, stop and then restart that application.