Lists the contents of the node directory.
None
None
>>-LIST--+-------+--NODE DIRECTORY--+-------------+------------>< '-ADMIN-' '-SHOW DETAIL-'
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
For information about fields associated with a specific node type, see the applicable CATALOG...NODE command.
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.