LIST NODES UTILITY Release Level THU 10/25/90 14:10 PM This application consists of one runfile: ListNodes.Run Product Name : List Nodes Supported On : B24, B26, B27, B28, B38, B39, and all SuperGen hardware Supported OS : BTOS II, CTOS I, CTOS II, CTOS III Description : The List Nodes utility operates very much like the FILES command, except that it displays a list of node names known to BNet. It will not necessarily display all the nodes that you can access through BNet, because BNet uses query mechanisms that allow it to initiate a search for a specified node when someone tries to access it. However, once BNet has accessed such a node, if it is through the OSI stack, the Naming Service will retain the information and it will then appear on the List Nodes display. The List Nodes utility depends on various BNet components for information concerning known nodes. It will therefore display node names that appear in the NCU or NCC tables, even if those nodes do not "really" exist. It will display information on cluster access nodes only if those nodes are currently up. Directions/Use : The List Nodes utility may be run by executing the /List Nodes command using the optional parameters which are described and detailed below: [Node spec (*)] This field can be used to specify a wildcarded expression that the displayed node names must match. The default is to match anything. [Details?] The default is 'No'. If you select 'Yes', then the addressing information displayed depends on the type of entry. For NCU mapped entries, the mapping is shown. For all NCU entries the SSAP is shown. The SSAP indicates which "protocol stack" (X.25, LAN, DCA, SNA) to use to reach the node; if it is set to 0, then the node is presummably a classic or cluster node. If the SSAP is not 0, then the address is as used by the OSI Session. It consists of three strings, known as the Session Selector (SSel), the Transport Selector (TSel), and the NSAP Address (NSAP). These fields are shown on the next line, in binary, and also in ASCII if printable. The SSel field will always be set to "BNet". For some transport services, such as OSI Transport WAN and OSI Transport LAN, the TSel field is null; for others, like DCA and SNA, it is set to the BNet nodename. As far as BNet is concerned the TSel and NSAP fields are arbitrary strings. For OSI Transport WAN the NSAP address is the X.25 address, preceded by a two-character character count (in hex). For OSI Transport LAN the NSAP address is arbitrary, but we generally use "49" style addressing, which contains the Media Access (MAC) address (e.g. for IEEE 802.3, the "Ethernet" address) as a subfield. For DCA and SNA transport, the NSAP field is set to null. For classic nodes, the classic address (specified when installing the classic transport) is shown. If the node is an adjacent node, the install number and the config number are also shown. (The config number uniquely identifies an NCC media table entry. The install number identifies a media service.) For switched connections, the classic subnet address is shown on the next line. It corresponds to the phone number for dialup or the X.25 address. For access cluster nodes and for your own nodename and server's nodename, there is no additional addressing information. [Print file] The default is to send it to the video. Enter the name of a file (or device) where the output will be sent. [Omit self (and server)?] The default is 'No'. If you enter 'yes' for 'omit self', it will not be present. (However, if your own nodename appears on other tables, then it may appear elsewhere in the list.) In the case where this command is run on a cluster, and both it and the server are BNet nodes, then this option will also suppress the server's nodename. [Omit NCU direct?] The default is 'No'. Enter 'yes' for 'omit NCU direct', then the command will not report any Naming Service direct entries (i.e. nodes mapped to themselves). This option has no effect if the Naming Service is not installed. [Omit NCU mapped?] The default is 'No'. Enter 'yes' to 'omit NCU mapped', then the command will not report any Naming Service mapped entries (i.e. nodes mapped through other nodes.) This option also has no effect if the Naming Service is not installed. [Omit classic nodes?] The default is 'No'. Enter 'yes' to 'omit classic nodes', then nodes reached through the classic transport will be omitted. This option has no effect if the classic transport is not installed. [Omit cluster access nodes?] The default is 'No'. Enter 'yes' to 'omit cluster access' nodes, then nodes reached through BNet's cluster access method will be omitted. (If List Nodes is run on a cluster, and both it and the server are nodes, then the server's nodename will also be omitted.) If you do not enter yes, individual cluster nodes will still be omitted if they are not currently up. [Omit nodes reached thru server?] The default is 'No'. Enter 'yes' for 'omit nodes reached through server', then only nodes reached through the Naming Service and the classic transport on the cluster will be shown. (In other words, it will show you the nodes that could still be reached if the server were down.) If you leave this line blank, then List Nodes will display node names of nodes reached both through the cluster and through the server. (Of course, the other options may cause it to omit some of those nodes.) For example, if you specified 'yes' to 'omit classic nodes', then nodes reached through the classic transport on either the cluster or the server will be omitted. If the cluster is not a BNet node, or if the List Nodes command is run on the server or on a standalone, then this option has no effect. [Omit wildcarded entries?] The default is 'No'. If you have NCU entries that contain wildcard characters (such as * and ?) in the target node names, then if you enter 'yes' to 'omit wildcarded entries', those entries will not appear. [Omit duplicate node names?] The default is 'No'. Enter 'yes' to 'omit duplicate node names', then only the first occurrence of a nodename will be displayed; other entries involving other addresses will be omitted. [Alphabetical sort?] The default is 'No'. Enter 'yes' to 'alphabetic sort', then the node names will be displayed in alphabetic order. Otherwise they will be displayed in the following order: own nodename, NCU direct entries, NCU mapped entries, classic transport entries, server's nodename*, cluster access nodes, server's NCU direct entries*, server's NCU mapped entries*, and server's classic transport entries*. The entries marked with the asterix (*) are only present if List Nodes is run on a cluster that is a BNet node. [SSAP to match] [Config # to match] These last two fields allow you to specify the nodes you want, more precisely. If you enter a number in the 'SSAP to match' field, then of the NCU entries returned, only those matching that SSAP value will be present. This has no effect on other types of nodes; you need to use other options to suppress them if desired. Similarly if you enter a number in the 'Config # to match' field, then of the classic entries returned, only those matching that config number will be present. If the number entered for either field is preceeded by a tilde (~), then only those nodes NOT matching will be returned. By using combinations of these options, it is possible to produce a list of nodes of a particular type. For example, when a new node is added to an X.25 network, one might obtain a list of all existing X.25 nodes that need to be informed of the new node. Alternatively this program might be used by operators who cannot quite remember the name of a node they want to access, to jog their memories. It might also be used by an administrator to get a list of all accessible nodes, which may need to be updated, perhaps when a new version of an application is distributed. COMMAND /List Nodes [Node spec (*)] [Details?] [Print file] [Omit self (and server)?] [Omit NCU direct?] [Omit NCU mapped?] [Omit classic nodes?] [Omit cluster access nodes?] [Omit nodes reached thru server?] [Omit wildcarded entries?] [Omit duplicate node names?] [Alphabetical sort?] [SSAP to match] [Config # to match]