Cataloging a Node in an IBM DB2 Universal Database Client

Catalog a node in an IBM DB2 Universal Database.

1. On UNIX or Linux, navigate to the server or client sqllib directory, which is located in the IBM DB2 Universal Database instance owner user home directory. For example, on UNIX:

   cd /db2home/db2inst1/sqllib

2. On UNIX or Linux, set the IBM DB2 Universal Database environment variables by sourcing the appropriate script:
   • For C shell:

     source db2cshrc

   • For Bourne or Korn shell:

     . db2profile

   If necessary, log in to the operating system as the IBM DB2 Universal Database instance owner. Logging in sets up all the IBM DB2 Universal Database environment variables.

   Note:

   On Windows, the IBM DB2 Universal Database installation sets up all necessary environment variables.

3. Start the IBM DB2 Universal Database command line processor (CLP).

   • On UNIX or Linux, enter:

     db2

   • On Windows, select Start > Programs > IBM DB2 > Command Line Tools > Command Line Processor.

4. Determine if the desired IBM DB2 Universal Database node has already been cataloged. At the CLP prompt, enter:

   list node directory

   If a node has already been cataloged, depending on whether the node is local (first entry below) or remote (second entry below), you see results similar to this:

   Node 1 entry:

   Node name                  = DB2NODE1

   Comment                    =

   Directory entry type       = LOCAL

   Protocol                   = LOCAL

   Instance name              = DB2_01

   Node 2 entry:

   Node name                  = DB2NODE2

   Comment                    =

   Directory entry type       = LOCAL

   Protocol                   = TCPIP

   Hostname                   = 10.22.85.228

   Service name               = 50001

5. If your desired node is not listed, catalog it at the CLP prompt.
   • To catalog a local node:

     CATALOG LOCAL NODE node_name INSTANCE db2_instance_name

     where:

     • node_name is the name of the node on the local host.

     • db2_instance_name is the name of the associated DB2 instance.

   • To catalog a remote node:

     CATALOG TCPIP NODE node_name REMOTE ip_address SERVER port_number

     where:

     • node_name is the name of the node on the remote host.

     • ip_address is either the IP address or name of the host on which the remote node is running.

     • port_number is the port on which the remote node is listening for client connections.

6. Verify that the node has been cataloged by issuing the list node directory command again.