1 – NSP
Network Services Protocol is the DNA transport utilized by PhaseIV.
1.1 – ATBs
Show the Association Block Table and any of its extensions tables. This table contains the information regarding associations between transport and its users.
1.2 – LSBs
Show the Link Service Blocks for Normal DATA and Expedited DATA Subchannels.
1.3 – LSPs
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 thought of as a point of entry for
users of NSP transport.
1.4 – PORTs
A port is a data structure describing a transport
connection.
1.4.1 – RSP
Specify a Remote Service Provider to select those ports. 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.
1.5 – 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 with
this Local Service Provider using NSP transport.
A Remote NSAP can be thought of as a point of entry on
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.
1.5.1 – LSP
Specify a Local Service Provider under 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 thought of as a point of entry for users of NSP transport.
1.6 – TCTBs
Show the Transport Connection Block Table and any of its
extensions tables. This Table contains information
regarding connections that exist on this node.
2 – TPCONS
Format: sda> net show tpcons
Transport Provider Connection Oriented network Service VAX
Communication module. An executable loadable image, which
is a lower VCM to OSI Transport and a user of TCP/IP stack.
This convergence layer will make TCP transport appear to be
a CONS Network Service to OSI Transport.
The number of connections displayed might not map to the
number of transport connections if OSI is using classes
{ 2, 4} due to the multiplexing of transport connections.
(@tpcons$ga_serv/type=tpcons).
2.1 – ATBS
Format: sda> net show tpcons atbs
Show the Association Block Table and any of its
extensions tables. This table contains the
information regarding associations between transport
and TPCONS. The association table contains TPCB port
blocks. (@tpcons$ga_atb/type=atb)
2.2 – TPTBs
Format: sda> net show tpcons tptbs
Show the Transport Provider Association Block Table and any
of its extensions tables. This table contains the
information regarding associations between transport
and the tcp/ip provider.
The table should contain a 1-1 correspondence to TPCONS
connections. For example: if you have a single connection
looped back to your node, you will see three TPCB blocks in
the TPTB table. One for the listen port and one for each end
of the TPCONS connection for a total of three TPCB ports.
(@tpcons$ga_tptb /type=atb)
2.3 – TPCBS
Format: sda> net show tpcons tpcbs
A TPCB is a data structure describing a TPCONS
connection. Each Transport Provider Control Block represents
one TCP/IP connection. The existence of a TPCB block does
NOT constitute an OSI Transport Connections until a connect
initiate/accept has been requested by OSI Transport. Once
this procedure has been sucessfully accomplished, the TPCB
represents one or more OSI Transport connections over TCP/IP
depending on the OSI Transport CLASS selected - multiplexing.
2.4 – STATS
Format: sda> net show tpcons stats
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 – OSI
Integrated OSI Transport is a transport that may be utilized by DNA session or OSI applications.
3.1 – ATBs
Show the Association Block Table and any of its extensions tables. This table contains the information regarding associations between transport and its users.
3.2 – LSBs
Show the Link Service Blocks for Normal DATA and Expedited DATA Subchannels.
3.3 – LSPs
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.
3.4 – NCCBs
Show all Network COnnection COntrol Blocks for OSI Transport.
For OSI Transport when run over a connection oriented network service
(CONS), there will be one NCCB for each network connection established,
and one NCCB for each X.25 Access filter OSI transport is listening on.
3.4.1 – RSP
Specify a Remote Service Provider to select those nccbs. This will list all OSI Transport network connections, both incoming and outgoing, that exist between this local network address and a specific remote network address.
3.5 – PORTs
A port is a data structure describing a transport
connection.
3.5.1 – RSP
Specify a Remote Service Provider to select those ports. 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.
3.5.2 – NCCB
Specify a Network Connection Block to select those ports. This will list all the transport connections, using a existing over a specific network connection.
3.6 – 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 with
this Local Service Provider using OSI transport.
A Remote NSAP can be thought of as a point of entry on
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.
3.6.1 – LSP
Specify a Local Service Provider under 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.
3.7 – TCTBs
Show the Transport Connection Block Table and any of its
extensions tables. This Table contains information
regarding connections that exist on this node.
4 – SESSION
4.1 – ASSOCIATIONS
Gives a brief display of all open associations. Syntax: NET$SDA> show session associations Specify an Hexadecimal Association ID as a value and you will get a more complete display. Syntax: NET$SDA> show session association=<association id>
4.2 – CONNECTIONS
Gives a brief display of all connections. Syntax: NET$SDA> show session connections Specify an Hexadecimal Connection ID as a value and you will get a more complete display. Syntax: NET$SDA> show session connection=<connection id>
5 – EVENT
Lists the Events not yet processed by the Event Dispatcher.
6 – EMAA
Entity Management Architecture Agent. Lists all the registered entities and any outstanding invoke blocks or management request packets.
7 – FORK
Although not a true DECnet-Plus display, will show VMS Fork Blocks queued awaiting execution at time of crash.
8 – QIO
The QIO interface is support for applications using the PhaseIV or VOTS style programming.
8.1 – 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.
8.2 – SUMMARY
Shows whether the QIO drivers are loaded, the DDB address, and driver name.
9 – ITEMLIST
Displays itemlists.
10 – ROUTING
10.1 – CACHE
Lists ES Cache entries.
10.2 – PORT
Lists Routing Port structure information.
11 – SUMMARY
Shows build information and number of active NSP and OSI links. Clearly this needs more useful information.
12 – TASK
Displays network task structures.
13 – TRACE
Show's TRACE STACK attempting to symbolize routine symbols.
14 – VCI
Show registered VMS Communications Modules. (Also displayed as part of SHOW SUMMARY.)