LIST NODE DIRECTORY command
The LIST NODE DIRECTORY command lists the contents of the node directory.
Authorization
None
Required connection
None
Command syntax
Command parameters
- ADMIN
- Specifies administration server nodes.
- SHOW DETAIL
- Specifies that the output should include the following information:
- Remote instance name
- System
- Operating system type
Examples
The following is sample output from LIST NODE DIRECTORY:
Node Directory
Number of entries in the directory = 2
Node 1 entry:
Node name = LANNODE
Comment =
Directory entry type = LDAP
Protocol = TCPIP
Hostname = LAN.db2ntd3.torolab.ibm.com
Service name = 50000
Node 2 entry:
Node name = TLBA10ME
Comment =
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = tlba10me
Service name = 447
The following is sample output from LIST ADMIN NODE DIRECTORY:
Node Directory
Number of entries in the directory = 2
Node 1 entry:
Node name = LOCALADM
Comment =
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = jaguar
Service name = 523
Node 2 entry:
Node name = MYDB2DAS
Comment =
Directory entry type = LDAP
Protocol = TCPIP
Hostname = peng.torolab.ibm.com
Service name = 523
- Node name
- The name of the remote node. This corresponds to the name entered for the nodename parameter when the node was cataloged.
- Comment
- A comment associated with the node, entered when the node was cataloged. To change a comment in the node directory, uncatalog the node, and then catalog it again with the new comment.
- Directory entry type
- LOCAL means the entry is found in the local node directory file. LDAP means the entry is found on the LDAP server or LDAP cache.
- Protocol
- The communications protocol cataloged for the node.
For information about fields associated with a specific node type, see the applicable CATALOG ... NODE command.
Usage notes
Regardless of the DB2LDAPCACHE miscellaneous variable setting, if using the LIST DATABASE DIRECTORY or the LIST NODE DIRECTORY commands, the list of local database and node entries are read from the LDAP server.
A node directory is created and maintained on each IBM® Data Server Runtime Client. It contains an entry for each remote workstation having databases that the client can access. The Db2® client uses the communication end point information in the node directory whenever a database connection or instance attachment is requested.
The database manager creates a node entry and adds it to the node directory each time it processes a CATALOG...NODE command. The entries can vary, depending on the communications protocol being used by the node.
- LDAP
- Local
- Named pipe
- TCPIP
- TCPIP4
- TCPIP6