DB2 Universal Database V8.1 Certification Exam 700 Study Guide

The process used to catalog nodes (servers) is significantly different from the process used to catalog databases. Instead of being explicitly cataloged as needed, nodes are usually implicitly cataloged whenever a remote database is cataloged using the Configuration Assistant. However, if you desire to explicitly catalog a particular node, you can do so by executing the CATALOG NODE command that corresponds to the communications protocol that will be used to access the server being cataloged. Several forms of the CATALOG NODE command are available, including:

  • CATALOG APPC NODE

  • CATALOG APPN NODE

  • CATALOG LDAP NODE

  • CATALOG NAMED PIPE NODE

  • CATALOG NETBIOS NODE

  • CATALOG TCPIP NODE

The syntax for all of these commands is very similar, the major difference being that many of the options available with each are specific to the communications protocol the command has been tailored for. Because TCP/IP is certainly the most common communications protocol used today, let's take a look at the syntax for that form of the CATALOG NODE command.

The syntax for the CATALOG TCPIP NODE command is:

CATALOG <ADMIN> TCPIP NODE [ NodeName ] REMOTE [ HostName ] SERVER [ ServiceName ] <SECURITY SOCKS> <REMOTE INSTANCE [ InstanceName ]> <SYSTEM [ SystemName ]> <OSTYPE [ SystemType ]> <WITH "[ Description ]">

where:

NodeName

Identifies the alias to be assigned to the node to be cataloged. This is an arbitrary name created on the user 's workstation and used to identify the node.

HostName

Identifies the host name, as it is known to the TCP/IP network. (This is the name of the server where the remote database you are trying to communicate with resides.)

ServiceName

Identifies the service name or the port number that the DB2 Database Manager instance on the server uses to communicate with.

InstanceName

Identifies the name of the server instance to which an attachment is to be made.

SystemName

Identifies the DB2 system name that is used to identify the server workstation.

SystemType

Identifies the type of operating system being used on the server workstation. (Valid values include: AIX, WIN, HPUX, SUN, OS390, OS400, VM, VSE, SNI, SCO, and LINUX.)

Description

A comment used to describe the node entry that will be made in the node directory for the node to be cataloged. The description must be enclosed by double quotation marks.

If you wanted to catalog a node for an AS/400 server workstation named DB2HOST and assign it the alias DB2_TCPIP, you could do so by executing a CATALOG TCPIP NODE command that looks something like this:

CATALOG TCPIP NODE DB2_TCPIP REMOTE DB2HOST SERVER 5000 OSTYPE OS400 WITH "A remote TCP/IP node"

Regardless of which CATALOG NODE command was used to catalog it, any node can be uncataloged by executing the UNCATALOG NODE command. The syntax for this command is:

UNCATALOG NODE [ NodeName ]

where:

NodeName

Identifies the alias assigned to the node to be uncataloged.

So if you wanted to uncatalog the node that was cataloged in the previous example, you could do so by executing an UNCATALOG NODE command that looks like this:

UNCATALOG NODE DB2_TCPIP

Related

Категории