Lists the contents of the node directory.
Authorization
None
Required Connection
None
Command Syntax
>>-LIST--+-------+--NODE DIRECTORY--+-------------+------------>< '-ADMIN-' '-SHOW DETAIL-'
Command Parameters
Examples
The following is sample output from LIST NODE DIRECTORY:
Node Directory Number of entries in the directory = 6 Node 1 entry: Node name = DB2APPC1 Comment = A remote APPC node Protocol = APPC Symbolic destination name = db2inst1 Security type = PROGRAM Node 2 entry: Node name = DB2IPX1 Comment = A remote IPX/SPX node Protocol = IPXSPX File server name = netwsrv Bindery object name = db2inst1 Node 3 entry: Node name = DB2IPX2 Comment = IPX/SPX node using direct addr Protocol = IPXSPX File server name = * Bindery object name = 09212700.400011527745.879E Node 4 entry: Node name = DB2NETB1 Comment = A remote NetBIOS node Protocol = NETBIOS Adapter number = 0 Server NNAME = DB2INST1 Node 5 entry: Node name = DB2TCP1 Comment = A remote TCP/IP node Protocol = TCPIP Hostname = tcphost Service name = db2inst1 Node 6 entry: Node name = DB2TCP2 Comment = TCP/IP node using IP address Protocol = TCPIP Hostname = 9.21.15.235 Service name = db2inst2
The common fields are identified as follows:
Note: | For information about fields associated with a specific node type, see the applicable CATALOG...NODE command. |
Usage Notes
A node directory is created and maintained on each database 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.
The node directory can contain entries for the following types of nodes:
See Also