Б%ь Librarian A09-30ж'6е мй 4<е мй▓5HELP н 4<е мй1 HELP- DECnet-Plus System Dump Analyzer Extensions.; These commands are intended for the use of Digital support5 personnel in the maintenance of DECnet-Plus for VMS.= They have not been externally documented as they are subject7 to change. The information displayed may not be clear8 to those not familiar with the internals of DECnet-Plus@ for VMS. Thus, the HELP supplied with NET$SDA does not explain) the information displayed in any detail.2 Invoking_NET$SDA; NET$SDA is a shareable image that SDA finds when you issue: the SHOW DECNET or NET command. (SHOW DECNET is provided, for consistency with the PhaseIV behavior.)= You may type a single NET$SDA command following the verb NET8 on an SDA command line. Or you may chose to type just? the verb NET to be prompted for specifically NET$SDA commands.2 SDA_Commands: Some SDA verbs that do not conflict with NET$SDA commands7 are executed as they would if issued at the SDA prompt: as a courte sy to the user. Examples are EXAMINE, FORMAT, and EVALUATE.2 Restrictions5 A multiple page display will get you back to the SDA- prompt unless you finish the entire display. 2 SymbolsA To change the directory from which the default symbols are read,D you must define the logical NET$SDA_STB_DIR to point to the desired directory. : example: define net$sda_stb_dir somedisk:[somedirectory]2 CLEAR3 DEBUG (See SET DEBUG.)2 EXIT Exits the NET$SDA extensions.# (Gets you back to the SDA prompt).2 QUIT Exits SDA.$ (Gets you back to your DCL prompt).2 SET3 DEBUG< For NET$SDA Developement Only! When SET, all DEBUG 8 PRINT statements will display. (Most MACROS have DEBUG9 embedded within.) Within source code, use DEBUG/DEBUGD 8 MACROs as you would PRINT/PRINTD with the knowlege that+ these will only display when DEBUG is SET.2 SHOW3 NSP8 Network Services Protocol is the DNA transport utilized by PhaseIV. 4 ATBs1 Show the Association Block Table and any of its - extensions tables. This table contains the 6 information regarding associations between transport and its users.4 LSBs2 Show the Link Service Blocks for Normal DATA and Expedited DATA Subchannels.4 LSPs4 Show all Local Service providers for NSP Transport.: For NSP Transport, there will be one Local Service> Provider for each local NSAP that includes NSP as its transport selector.> A Local NSAP can be thou ght of as a point of entry for users of NSP transport.4 PORTs9 A port is a data structure describing a transport connection.5 RSP9 Specify a Remote Service Provider to select those ports.9 This will in effect, list all NSP Transport connections : that exist between a specific local service provider and % a specific remote service provider .> NOTE: There exists one Local Service Provider per local NSAP.@ There exists one Remote Service Provider per remote NSAP.4 RSPs; Show Remote Service Providers under a Local Service< Provider under NSP transport. (All is the default).; For NSP Transport, there will be one Remote Service@ Provider for each remote NSAP that has had contact with9 this Local Service Provider using NSP transport.> A Remote NSAP can be thought of as a point of entry on5 the remote node, for users of NSP transport.> NOTE: There exists one Local Service Provider per local NSAP.@ There exists one Remote Service Provider per remote NSAP.5 LSP6 Specify a Local Service Provider under NSP transport.3 For NSP Transport, there will be one Local Service6 Provider for each local NSAP that includes NSP as its transport selector.A A Local NSAP can be thought of as a point of entry for users of NSP transport.4 TCTBsA Show the Transport Connection Block Table and any of its : extensions tables. This Table contains information7 regarding connections that exist on this node. 3 TPCONS Format: sda> net show tpcons; Transport Provider Connection Oriented network Service VAX; Communication module. An executable loadable image, which D is a lower VCM to OSI Transport and a user of TCP/IP stack. D This convergence layer will make TCP transport appear to be 0 a CONS Network Service to OSI Transport.; The number of connections displayed might not map to the 9 number of transport connections if OSI is using classes B { 2, 4} due to the multiplexing of transport connections. & (@tpcons$ga_serv/type=tpcons). 4 ATBS# Format: sda> net show tpcons atbs1 Show the Association Block Table and any of its - extensions tables. This table contains the 6 information regarding associations between transport 6 and TPCONS. The association table contains TPCB port ) blocks. (@tpcons$ga_atb/type=atb)4 TPTBs$ Format: sda> net show tpcons tptbs= Show the Transport Provider Association Block Table and any 4 of its extensions tables. This table contains the 6 information regarding associations between transport and the tcp/ip provider. 9 The table should contain a 1-1 correspondence to TPCONS B connections. For example: if you have a single connection D looped back to your node, you will see three TPCB blocks in E the TPTB table. One for the listen port and one for each end B of the TPC ONS connection for a total of three TPCB ports. $ (@tpcons$ga_tptb /type=atb) 4 TPCBS$ Format: sda> net show tpcons tpcbs6 A TPCB is a data structure describing a TPCONSE connection. Each Transport Provider Control Block represents B one TCP/IP connection. The existence of a TPCB block does D NOT constitute an OSI Transport Connections until a connect B initiate/accept has been requested by OSI Transport. Once C this procedure has been sucessfully accomplished, the TPCB E represents one or more OSI Transport connections over TCP/IP E depending on the OSI Transport CLASS selected - multiplexing. 4 STATS$ Format: sda> net show tpcons stats5 The Statistic block holds all operations issued and = received by the TPCONS VCM. Currectly the low order longword is displayed.' (tpcons$ga_statistics/type=tpconsstat)3 OSID Integrated OSI Transport is a transport that may be utilized by DNA session or OSI applications.4 ATBs1 Show the Association Block Table and any of its - extensions tables. This table contains the 6 information regarding associations between transport and its users.4 LSBs2 Show the Link Service Blocks for Normal DATA and Expedited DATA Subchannels.4 LSPs4 Show all Local Service providers for OSI Transport.: For OSI Transport, there will be one Local Service> Provider for each local NSAP that includes OSI as its transport selector.> A Local NSAP can be thought of as a point of entry for users of OSI transport.4 NCCBs> Show all Network COnnection COntrol Blocks for OSI Transport.M For OSI Transport when run over a connection oriented network serviceH (CONS), there will be one NCCB for each network connection established,H and one NCCB for each X.25 Access filter OSI transport is listening on.5 RSP9 Specify a Remote Service Provider to select those nccbs.D This will list all OSI Transport network connections, both incomingA and outgoing, that exist between this local network address and # a specific remote network address.4 PORTs9 A port is a data structure describing a transport connection.5 RSP9 Specify a Remote Service Provider to select those ports.9 This will in effect, list all OSI Transport connections : that exist between a specific local service provider and % a specific remote service provider .> NOTE: There exists one Local Service Provider per local NSAP.@ There exists one Remote Service Provider per remote NSAP.5 NCCB: Specify a Network Connection Block to select those ports.D This will list all the transport connections, using a existing over a specific network connection.4 RSPs; Show Remote Service Providers under a Local Service< Provider under OSI transport. (All is the default).; For OSI Transport, there will be one Remote Service@ Provider for each remote NSAP that has had contact with9 this Local Service Provider using OSI transport.> A Remote NSAP can be thought of as a point of entry on5 the remote node, for users of OSI transport.> NOTE: There exists one Local Service Provider per local NSAP.@ There exists one Remote Service Provider per remote NSAP.5 LSP6 Specify a Local Service Provider under OSI transport.3 For OSI Transport, there will be one Local Service6 Provider for each local NSAP that includes OSI as its transport selector.A A Local NSAP can be thought of as a point of entry for users of OSI transport.4 TCTBsA Show the Transport Connection Block Table and any of its : extensions tables. This Table contains information7 regarding connections that exist on this node. 3 SESSION4 ASSOCIATIONS0 Gives a brief display of all open associations. Syntax:$ NET$SDA> show session associations5 Specify an Hexadecimal Association ID as a value and& you will get a more complete display. Syntax:4 NET$SDA> show session association= 4 CONNECTIONS* Gives a brief display of all connections. Syntax:# NET$SDA> show session connections4 Specify an Hexadecimal Connection ID as a value and& you will get a more complete display. Syntax:2 NET$SDA> show session connection=3 EVENT< Lists the Events not yet processed by the Event Dispatcher.3 EMAA& Entity Management Architecture Agent.6 Lists all the registered entities and any outstanding- invoke blocks or management request packets.3 FORK7 Although not a true DECnet-Plus display, will show VMS8 Fork Blocks queued awaiting execution at time of crash.3 QIO4 The QIO interface is support for applications using) the PhaseIV or VOTS style programming. 4 DEVICES= The command SHOW DECNET /QIO /DEVICES [ /DNA | /VOTS ] will = display a summary of all the DNA or VOTS devices (including < declared applications). If you don't specify /DNA or /VOTS then /DNA is the default. 4 SUMMARY? Shows whether the QIO drivers are loaded, the DDB address, and driver name. 3 ITEMLIST Displays itemlists. 3 ROUTING4 CACHE Lists ES Cache entries.4 PORT* Lists Routing Port structure information. 3 SUMMARY@ Shows build information and number of active NSP and OSI links., Clearly this needs more useful information.3 TASK" Displays network task structures.3 TRACE< Show's TRACE STACK attempting to symbolize routine symbols.3 VCI= Show registered VMS Communications Modules. (Also displayed as part of SHOW SUMMARY.)ww