HPlogo SNA Link/iX Node Manager's Guide > Chapter 6 MPE Commands

SNACONTROL STATUS

MPE documents

Complete PDF
Table of Contents
Index

Displays the status of a specific SNA node.

Syntax


  SNACONTROL STATUS;NODE=NodeName
                 [;LUNAME[=LUName]]
                 [;NAU][NAUNumber]]
                 [;LFSID[=odai,sid]]
                 [;STATUS=ALL     ]
                 [        ACTIVE  ]
                 [        INACTIVE]
                 [        PENDING ]
                 [        RESET   ]
                 [;SESSTYPE=ALL   ]
                 [          SSCP  ]
                 [          LU    ]
                 [          LU_DEP]
                 [          LU_IND]
                 [;NCB]
                 [;HSCB]
                 [;ROUTE]
                 [;LURECORD]
                 [;LINK[=A[LL]            ]]
                 [     [=L[INK[STATE]]    ]]
                 [     [=C[ONF[IGURATION]]]]
                 [     [=S[TAT[ISTICS]]   ]]
                 [     [=D[IAG[STATS]]    ]]
                 [     [=R[ESET]          ]]

Use

SNACONTROL STATUS can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command.

Parameters

NodeName

Conditionally required. The name of the configured SNA node whose status you want displayed. The name can be up to eight alphanumeric characters long; the first character must be alphabetic.

If only one SNA node is active, this parameter is optional: If you do not include it, the active node's status is displayed. If more than one node is active, this parameter is required: If you do not include it, a list of all configured SNA nodes is displayed, but no status is displayed; you can then reissue this command with the appropriate node name.

LUName

The name of the LU whose session status you want displayed. The name can be up to eight alphanumeric characters long. The first character must be alphabetic. If this parameter is specified, neither the NAU nor LFSID parameters can be specified. Specifying this parameter without an LU name causes the sessions to be displayed in alphabetical order.

NAU

The NAU number of the dependent session whose status you want to display. The NAU number must be a decimal number between 0 and 255. If this parameter is specified, neither the LUNAME nor LFSID parameters can be specified. Specifying this parameter without an NAU number causes the sessions to be displayed in numerical order.

LFSID

The LFSID number of the independent session whose status you want to display. The LFSID must consist of the ODAI followed by the SID, with a comma as a separator. The ODAI must be either 0 or 1. The SID must be a hex number between $0000 and $FFFE. If this parameter is specified, neither the LUNAME nor NAU parameters can be specified. Specifying this parameter without an LFSID number causes the sessions to be displayed in numerical order.

STATUS

Specifies the status of the sessions that are to be displayed. Possible values for this parameter are ALL (all sessions), ACTIVE (only active sessions), INACTIVE (only inactive sessions), PENDING (only sessions that are pending activation or pending reset), and RESET (only reset sessions).

SESSTYPE

Specifies the session type of the sessions that are to be displayed. Possible values for this parameter are ALL (all sessions), SSCP (only PU-SSCP and LU-SSCP sessions), LU (only LU-LU dependent and LU-LU independent sessions), LU_DEP (only LU-LU dependent sessions), and LU_IND (only LU-LU dependent sessions).

NCB

Specifies that the node's Node Control Block (NCB) is to be displayed. This parameter is for Hewlett-Packard debugging purposes, and should be used only under HP recommendation.

HSCB

Specifies that the session's Half Session Control Block (HSCB) is to be displayed.

This parameter is for Hewlett-Packard debugging purposes, and should be used only under HP recommendation.

ROUTE

Specifies that the session's Routing Table entry (packets received) is to be displayed.

This parameter is for Hewlett-Packard debugging purposes, and should be used only under HP recommendation.

LURECORD

Specifies that the session's LU record is to be displayed.

This parameter is for Hewlett-Packard debugging purposes, and should be used only under HP recommendation.

LINK

This is the same as specifying the ALL link status parameter (described below).

ALL

All of the status information for the link is displayed:

  • Link state status (see the LINKSTATE parameter description)

  • Link configuration data (see the CONFIGURATION parameter description)

  • Link statistics (see the STATISTICS parameter description)

Note that if no other link status parameter (LINKSTATE, CONFIGURATION, STATISTICS, DIAGSTATS, and RESET) is specified, this parameter (ALL) is the default.

LINKSTATE

State status information for the link is displayed:

SDLC:

  • Link name

  • Link type

  • Link state

X.25:

  • Link name

  • Link type

  • Link state

  • Tracing status

  • Trace file name

Token Ring:

  • Link name

  • Link type

  • Link state

This information is explained in more detail after the examples later in this command description.

CONFIGURATION

Configuration data for the link is displayed:

SDLC:

  • Link name

  • Link type

  • Link state

  • Physical path

  • Phone number

  • Auto dial status

  • Station ID

  • XID

  • Receive timeout

  • Error retries

  • Cable type

  • Buffer size

  • Connect timeout

  • Local timeout

  • Transmission speed

X.25:

  • Link name

  • Link type

  • Link state

  • Tracing status

  • Trace file name

  • Network interface (NI) name

  • Inactivity timeout

  • Virtual circuit (VC) type

  • For a permanent virtual circuit (PVC):

    • PVC number

  • For a switched virtual circuit (SVC):

    • Remote address

    • Call direction

    • Maximum call retries

    • Call retry delay

    • Call retry count

Token Ring:

  • Link name

  • Link type

  • Link state

  • Physical path

  • Data rate

  • Current station address

  • Default station address

  • Functional address mask

This information is explained in more detail after the examples later in this command description.

STATISTICS

Statistics for the link, for both inbound (sent) and outbound (received) paths of the link, are displayed:

SDLC:

  • Link name

  • Link type

  • Link state

  • Connect duration

  • Data bytes sent

  • Overhead bytes sent

  • Total frames sent

  • Data frames sent

  • Bytes retransmitted

  • Frames retransmitted

  • DSR losses

  • CTS losses unexpected

  • DCD carrier losses

  • Tracing status

  • Data bytes received

  • Overhead bytes received

  • Total frames received

  • Data frames received

  • Oversized frames received

  • Aborted frames received

  • Receive overruns

  • CRC errors

  • Statistics resets

X.25:

  • Link name

  • Link type

  • Link state

  • Tracing status

  • Trace file name

  • Total bytes sent and received

  • Data bytes sent and received

  • Control bytes sent and received

  • Total packets sent and received

  • Data packets sent and received

  • Control packets sent and received

Token Ring:

  • Link name

  • Link type

  • Link state

  • Physical path

  • Data rate

  • Number of frames sent and received without errors

  • Number of bytes sent and received without errors

  • Number of frames not successfully transmitted

  • Number of frames received with errors

This information is explained in more detail after the examples later in this command description.

DIAGSTATS

All of the status information for the link is displayed:

  • Link state status (see the LINKSTATE parameter description)

  • Link configuration data (see the CONFIGURATION parameter description)

  • Link statistics (see the STATISTICS parameter description)

  • Link diagnostics

This parameter is for Hewlett-Packard debugging purposes, and should be used only under HP recommendation.

RESET

Link statistics are gathered from the time the link is started. This parameter resets those statistics to 0. To gather link statistics for a specific time period, issue this command (SNACONTROL STATUS) with this parameter (RESET) specified, to reset the statistics to 0. Once the statistics have been gathered for the desired time period, issue this command again, with the ALL or STATISTICS parameter specified.

Description

You can use SNACONTROL STATUS to display the status of sessions on a specific SNA node. The status of a session can be displayed only when a Half Session Control Block (HSCB) has been created for that session by SNA Transport. An HSCB is created when an SNA service initiates a session with SNA Transport, or if tracing is turned on for a session. The status of a session is not displayed if an LU has only been configured.

SDLC Link-Level Status Information

An example of an SDLC link-level status display is given below, and the terminology used is described after the example. Note that when link-level status information is displayed, the corresponding session-level status information is also displayed. (Since the session-level status terminology is described later under "Session-Level Status Information," it is not described here.)

Example

If an SDLC link is being used, typing

SNACONTROL STATUS;NODE=IBMNODE;LINK=ALL

where IBMNODE is already active could generate this display: 

 Linkname: IBMNODE     Linktype: SNA/SDLC    Linkstate:
 CONNECTING LEVEL 1
 Physical Path                 40
 Phone Number
 Auto Dial                  0         Cable Type             None
 Station ID                C1         Buffer Size              265   bytes
 XID               XID6789012         Connect Timeout          900   sec
 Receive Timeout          180 sec     Local Timeout             30   sec
 Error Retries              7         Transmission Speed     9600    bps

 Connect Duration          135:09:19  Tracing                            OFF
 Data Bytes Sent                   0  Data Bytes Rcvd                      0
 Overhead Bytes Sent               0  Overhead Bytes Rcvd                  0
 Total Frames Sent                 0  Total Frames Rcvd                    0
 Data Frames Sent                  0  Data Frames Rcvd                     0
 Bytes Retransmitted               0  Oversized Frames Rcvd                0
 Frames Retransmitted              0  Aborted Frames Rcvd                  0
 DSR Losses                        0  Receive Overruns                     0
 CTS Losses Unexpected             0  CRC Errors                           0
 DCD Carrier Losses                0  Statistics Resets                    0


 NAME     TYPE    NAU    STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 XPORTPU  PU_SSCP   0    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   1    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   2    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   3    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   4    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   5    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   6    RESET      MANAGER.SYS     OFF
 PFA2     DEP_LU    2    PEND_ACT_R PITEST.PUT21R40 NMTC0090.PUB.SYS
 PFA3     DEP_LU    3    ACTIVE     PITEST.PU2140   OFF
 PFA4     DEP_LU    4    PEND_RST_R PITEST.PU2140   OFF
 PFA5     DEP_LU    5    PEND_SON   PITEST.PU2140   OFF
 PFACLASS DEP_LU    1    RESET      PITEST.PU2140   OFF

 NAME     TYPE    LFSID  STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 INDLU1   IND_LU  1,0200 PEND_ACT_L PITEST.PUT21R40 OFF
 INDLU2   IND_LU  1,0201 PEND_RST_L PITEST.PUT21R40 OFF
 INDLU3   IND_LU  1,0202 PEND_RST_N PITEST.PUT21R40 OFF
 INDLU4   IND_LU   RESET      PITEST.PUT21R40 OFF

Terminology

The linkname is the same as the node name.

The linktype is "SNA/SDLC".

The linkstate is one of the following:

  • NOT CONNECTED = The connection is closed.

  • CONNECTED LEVEL 1 = A level 1 connection has been established.

  • CONNECTED LEVEL 2 = A level 2 connection has been established.

  • CONNECTING LEVEL 1 = A level 1 connection is in progress.

  • CONNECTING LEVEL 2 = A level 2 connection is in progress.

  • DISCONNECTING LVL 1 = A level 1 disconnection is in progress.

  • DISCONNECTING LVL 2 = A level 2 disconnection is in progress.

  • ERROR = The SDLC link driver has detected a link error.

The physical path is the address of the PSI.

The phone number is the number the link dials into, if an auto-dial modem is being used.

Auto dial is "0" if a leased line, a manual-dial modem, or no modem is being used; "1" if an auto-dial modem is being used.

The station ID is the HP e3000's link station identifier to the remote system's communications controller.

The XID is the station identification that is transmitted to the remote system whenever the HP e3000 receives an Exchange Station Identification (XID) request frame.

The receive timeout is the number of seconds the link-level software will wait for the remote system poll before closing the line.

Error retries is the maximum number of times the SDLC link manager will retry after errors or timeouts before setting the line to idle.

The cable type is one of the following:

  • None

  • Loopback

  • Modem eliminator

  • RS232

  • RS366

  • RS449

  • V35

  • X21

The buffer size is the longest frame (in bytes) that the PSI is allowed to receive.

The connect timeout is the number of seconds the SDLC link driver will wait for a link Set Normal Response Mode (SNRM) command after telling the PSI to enable the Data Terminal Ready (DTR) signal, before closing the line.

The local timeout is the number of seconds the SDLC link driver will wait for PSI card activity before reporting a PSI failure.

The transmission speed is the transmission speed (in bits per second) of the line being used by the link if a modem is not being used. If a modem is being used, the modem determines the speed.

The connect duration is how long a level 2 connection has been maintained.

Data bytes sent is the total number of bytes that have been sent in the information field of an Information (I) frame.

Overhead bytes sent is the total number of SDLC bytes that have been sent. The total includes flags and Frame Check Sequence (FCS) bytes.

Total frames sent is the total number of frames that have been sent.

Data frames sent is the total number of Information (I) frames that have been sent.

Bytes retransmitted is the number of non-SDLC data bytes that have been retransmitted.

Frames retransmitted is the number of frames that have been retransmitted because the frame was not acknowledged.

DSR losses is the total number of times the Data Set Ready (DSR) signal has dropped unexpectedly.

CTS losses unexpected is the total number of times the Clear To Send (CTS) signal has dropped unexpectedly.

DCD carrier losses is the total number of times the Data Carrier Detector (DCD) signal has dropped unexpectedly.

Tracing is "ON" if link-level tracing is on, or "OFF" if the tracing is off.

Data bytes rcvd is the total number of bytes that have been received in the information field of an Information (I) frame.

Overhead bytes rcvd is the total number of SDLC bytes that have been received. The total includes flags and Frame Check Sequence (FCS) bytes.

Total frames rcvd is the total number of frames that have been received.

Data frames rcvd is the total number of Information (I) frames that have been received.

Oversized frames rcvd is the total number of received frames that exceed the maximum configured frame size.

Aborted frames rcvd is the total number of aborted frames that were received.

Receive overruns is the total number of received frames that contained no control bytes.

CRC errors is the total number of received frames that contained a Cyclical Redundancy Check (CRC) error.

Statistics resets is the total number of times the statistics have been cleared.

X.25 Link-Level Status Information

Two examples of X.25 link-level status displays are given below, and the terminology used is described after the examples. Note that when link-level status information is displayed, the corresponding session-level status information is also displayed. (Since the session-level status terminology is described later under "Session-Level Status Information," it is not described here.)

Example 1

If an X.25 link is being used, typing

SNACONTROL STATUS;NODE=IBMNODE;LINK=ALL

where IBMNODE is already active, and a permanent virtual circuit (PVC) is being used, could generate this display: 

 LINKNAME : IBMNODE    LINKTYPE : SNA X.25   LINKSTATE:
 SNA CONNECTED

 TRACING  : ON          TRACEFILE: TRACE.PUB.SYS

 LINK CONFIGURATION DATA:

      NINAME            :           X25NI

      INACTIVITY TIMEOUT:               0

      VC TYPE           :             PVC

      PVC NUMBER        :              10

 LINK STATISTICS:

                 SENT                                     RECEIVED
                 - -                                      - - - -
 TOTAL BYTES    :                 8100    TOTAL BYTES    :            8100
 DATA BYTES     :                 8080    DATA BYTES     :            8080
 CONTROL BYTES  :                   20    CONTROL TYPES  :              20
 TOTAL PACKETS  :                   10    TOTAL PACKETS  :              10
 DATA PACKETS   :                    8    DATA PACKETS   :               8
 CONTROL PACKETS:                    2    CONTROL PACKETS:               2

 NAME     TYPE    NAU    STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 XPORTPU  PU_SSCP   0    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   1    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   2    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   3    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   4    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   5    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   6    RESET      MANAGER.SYS     OFF
 PFA2     DEP_LU    2    PEND_ACT_R PITEST.PUT21R40 NMTC0090.PUB.SYS
 PFA3     DEP_LU    3    ACTIVE     PITEST.PU2140   OFF
 PFA4     DEP_LU    4    PEND_RST_R PITEST.PU2140   OFF
 PFA5     DEP_LU    5    PEND_SON   PITEST.PU2140   OFF
 PFACLASS DEP_LU    1    RESET      PITEST.PU2140   OFF

 NAME     TYPE    LFSID  STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 INDLU1   IND_LU  1,0200 PEND_ACT_L PITEST.PUT21R40 OFF
 INDLU2   IND_LU  1,0201 PEND_RST_L PITEST.PUT21R40 OFF
 INDLU3   IND_LU  1,0202 PEND_RST_N PITEST.PUT21R40 OFF
 INDLU4   IND_LU   RESET      PITEST.PUT21R40 OFF

Example 2

If an X.25 link is being used, typing

SNACONTROL STATUS;NODE=IBMNODE;LINK=ALL

where IBMNODE is already active, and a switched virtual circuit (SVC) is being used, could generate this display: 

 LINKNAME : IBMNODE    LINKTYPE : SNA X.25   LINKSTATE:
 SNA CONNECTED
 TRACING  : ON          TRACEFILE: TRACE.PUB.SYS

 LINK CONFIGURATION DATA:
 
      NINAME            :           X25NI    CALL DIRECTION  :         OUT

      INACTIVITY TIMEOUT:               0    MAX CALL RETRIES:          10

 @COMPUTERTEXTW =      VC TYPE           :             SVC    CALL
 RETRY DELAY:          60

      REMOTE ADDRESS    :  FFFFFFFFFFFFFF    CALL RETRY COUNT:           0

 LINK STATISTICS:

                 SENT                                     RECEIVED
                 - -                                      - - - -
 TOTAL BYTES    :                 8100    TOTAL BYTES    :            8100
 DATA BYTES     :                 8080    DATA BYTES     :            8080
 CONTROL BYTES  :                   20    CONTROL TYPES  :              20
 TOTAL PACKETS  :                   10    TOTAL PACKETS  :              10
 DATA PACKETS   :                    8    DATA PACKETS   :               8
 CONTROL PACKETS:                    2    CONTROL PACKETS:               2

 NAME     TYPE    NAU    STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 XPORTPU  PU_SSCP   0    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   1    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   2    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   3    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   4    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   5    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   6    RESET      MANAGER.SYS     OFF
 PFA2     DEP_LU    2    PEND_ACT_R PITEST.PUT21R40 NMTC0090.PUB.SYS
 PFA3     DEP_LU    3    ACTIVE     PITEST.PU2140   OFF
 PFA4     DEP_LU    4    PEND_RST_R PITEST.PU2140   OFF
 PFA5     DEP_LU    5    PEND_SON   PITEST.PU2140   OFF
 PFACLASS DEP_LU    1    RESET      PITEST.PU2140   OFF

 NAME     TYPE    LFSID  STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 INDLU1   IND_LU  1,0200 PEND_ACT_L PITEST.PUT21R40 OFF
 INDLU2   IND_LU  1,0201 PEND_RST_L PITEST.PUT21R40 OFF
 INDLU3   IND_LU  1,0202 PEND_RST_N PITEST.PUT21R40 OFF
 INDLU4   IND_LU   RESET      PITEST.PUT21R40 OFF

Terminology

The linkname is the same as the node name.

The linktype is "SNA X.25".

The linkstate is one of the following:

  • SNA CONNECT PENDING = The virtual circuit to the remote system has been established and an SNA connection (which must use the virtual circuit) is in the process of being established.

  • SNA CONNECTED = The SNA and X.25 connections to the remote system have been established.

  • SNA DISCONNECT PENDING = The SNA connection is in the process of terminating. However, the X.25 connection still exists.

  • SNA ERROR RECOVERY = The X.25 link has received invalid frames from the remote system and is in the process of recovery. Note that the SNA connection, the X.25 connection, and the SNA node are all still active.

  • VC CONNECT PENDING = A request for a virtual circuit from the X.25 network has been made, but the virtual circuit has not been obtained. Note that this state is valid for a switched virtual circuit (SVC) only.

  • VC CONNECTED = The virtual circuit to the remote system has been established; however, no SNA connection has been made. Note that this state is valid for a switched virtual circuit (SVC) only.

Tracing is "ON" if link-level tracing is on, or "OFF" if the tracing is off.

The tracefile is the name of the link trace file.

The NI name is the NS network interface that the link is using.

The inactivity timeout is the number of minutes the Qualified Logical Link Control (QLLC) module will wait between incoming packets. If the value is "0", the timer is disabled.

The VC type is "PVC" for an X.25 permanent virtual circuit, or "SVC" for an X.25 switched virtual circuit.

The PVC number is the number that identifies the permanent virtual circuit for the X.25 link. Note that this information is displayed for a PVC only.

The remote address is the X.25 network address of the remote system. Note that this information is displayed for an SVC only.

The call direction is "IN" if the remote system initiated the call, or "OUT" if the HP e3000 initiated the call. Note that this information is displayed for an SVC only.

Max call retries is the maximum number of times the Qualified Logical Link Control (QLLC) module will try to connect to the remote system without success. Note that this information is displayed for an outgoing SVC only.

The call retry delay is the number of seconds the QLLC module will wait between attempts to connect to the remote system. Note that this information is displayed for an outgoing SVC only.

The call retry count is the number of times call retries have been attempted. Note that this information is displayed for an outgoing SVC only.

Total bytes is the total number of bytes sent from and received by the link.

Data bytes is the total number of bytes of data sent from and received by the link.

Control bytes is the total number of bytes of control information sent from and received by the link.

Total packets is the total number of packets sent from and received by the link.

Data packets is the total number of packets of data sent from and received by the link.

Control packets is the total number of packets of control information sent from and received by the link.

Token Ring Link-Level Status Information

An example of a Token Ring link-level status display is given below, and the terminology used is described after the example. Note that when link-level status information is displayed, the corresponding session-level status information is also displayed. (Since the session-level status terminology is described later under "Session-Level Status Information," it is not described here.)

Example

If a Token Ring link is being used, typing

SNACONTROL STATUS;NODE=IBMNODE;LINK=ALL

where IBMNODE is already active could generate this display: 

 Linkname: IBMNODE     Linktype: IEEE8025    Linkstate:
 CONNECTED

 Physical Path:  48      Data Rate: 16 Mbps

 Current Station Address:  10-00-90-00-00-07
 Default Station Address:  10-00-90-90-C8-46
 Functional Address Mask:        00-00-00-00

 Transmits no error:          6614976    Receives no error:          6620830
 Transmit byte count:      2368752825    Receives byte count:     2367702513
 Transmit errors:                   0    Receive errors:                    0

 NAME     TYPE    NAU    STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 XPORTPU  PU_SSCP   0    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   1    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   2    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   3    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   4    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   5    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   6    RESET      MANAGER.SYS     OFF
 PFA2     DEP_LU    2    PEND_ACT_R PITEST.PUT21R40 NMTC0090.PUB.SYS
 PFA3     DEP_LU    3    ACTIVE     PITEST.PU2140   OFF
 PFA4     DEP_LU    4    PEND_RST_R PITEST.PU2140   OFF
 PFA5     DEP_LU    5    PEND_SON   PITEST.PU2140   OFF
 PFACLASS DEP_LU    1    RESET      PITEST.PU2140   OFF

 NAME     TYPE    LFSID  STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 INDLU1   IND_LU  1,0200 PEND_ACT_L PITEST.PUT21R40 OFF
 INDLU2   IND_LU  1,0201 PEND_RST_L PITEST.PUT21R40 OFF
 INDLU3   IND_LU  1,0202 PEND_RST_N PITEST.PUT21R40 OFF
 INDLU4   IND_LU   RESET      PITEST.PUT21R40 OFF

Terminology

The linkname is the same as the node name.

The linktype is "IEEE8025".

The linkstate is one of the following:

  • NOT CONNECTED = The Token Ring device adapter has not been inserted into the network.

  • CONNECTED = The Token Ring device adapter has been inserted into the network.

  • RETRY = The Token Ring device adapter is retrying to insert into the network.

The physical path is the address of the token ring adapter card.

The data rate is the speed of the token ring (in megabits per second).

The current station address is the currently-active station address.

The default station address is the factory-configured default station address.

The function address mask is the address mask as described in the IBM Token-Ring Network Architecture Reference.

Transmits no error is the number of frames transmitted without errors.

Receives no error is the number of frames received without errors.

Transmit byte count is the number of bytes transmitted without errors.

Receive byte count is the number of bytes received without errors.

Transmit errors is the number of frames not successfully transmitted because of errors.

Receive errors is the number of frames received with errors.

Session-Level Status Information

Regardless of the type of link being used, the same session-level status information is displayed. An example of a session-level status display is given below, and the terminology used is described after the example.

Example

If either an SDLC, X.25, or token ring link is being used, typing

SNACONTROL STATUS;NODE=IBMNODE

where IBMNODE is already active could generate this display: 

 SESSION STATE STATUS FOR NODE : IBMNODE

 NAME     TYPE    NAU    STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 XPORTPU  PU_SSCP   0    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   1    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   2    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   3    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   4    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   5    ACTIVE     MANAGER.SYS     OFF
 XPORTLU  LU_SSCP   6    RESET      MANAGER.SYS     OFF
 PFA2     DEP_LU    2    PEND_ACT_R PITEST.PUT21R40 NMTC0090.PUB.SYS
 PFA3     DEP_LU    3    ACTIVE     PITEST.PU2140   OFF
 PFA4     DEP_LU    4    PEND_RST_R PITEST.PU2140   OFF
 PFA5     DEP_LU    5    PEND_SON   PITEST.PU2140   OFF
 PFACLASS DEP_LU    1    RESET      PITEST.PU2140   OFF

 NAME     TYPE    LFSID  STATE      USER            TRACE FILE
 ======== ======= ====== ========== =============== =========================
 INDLU1   IND_LU  1,0200 PEND_ACT_L PITEST.PUT21R40 OFF
 INDLU2   IND_LU  1,0201 PEND_RST_L PITEST.PUT21R40 OFF
 INDLU3   IND_LU  1,0202 PEND_RST_N PITEST.PUT21R40 OFF
 INDLU4   IND_LU   RESET      PITEST.PUT21R40 OFF

Terminology

The name is the PU or LU name. Note that XPORTPU and XPORTLU are the internal names that are used by SNA Transport. XPORTPU is a PU name used for maintaining the PU-SSCP session. XPORTLU is the LU name used for maintaining the LU-SSCP sessions (for dependent LUs).

The type is the type of the session. This is either PU-SSCP for PU-SSCP sessions, LU-SSCP for LU-SSCP sessions, DEP_LU for dependent LU-LU sessions, or IND_LU for independent LU-LU sessions.

The NAU is the session's Network Addressable Unit number in decimal. All PU-SSCP, LU-SSCP, and dependent LU-LU sessions have a NAU.

The LFSID is the session's Local-form session identifier. It consists of the OAF-DAF assignor indicator (ODAI) followed by the session identifier (SID) in hexadecimal. Only independent LU-LU sessions have an LFSID. If an independent LU-LU session is in RESET state, it will not have an LFSID.

The session state is one of the following:

  • ACTIVE = The session with the remote system has been established. Note that the SNA services are connected to the remote system in this state only.

  • PEND_ACT_L = Pending activation local. An activation request has been sent by the HP e3000. However, a response to the activation request has not yet been received.

  • PEND_ACT_R = Pending activation remote. An activation request has been received by the HP e3000. However, a response to the activation request has not yet been sent.

  • PEND_RST_B = Pending reset both. Both the HP e3000 and the remote system have sent UNBIND requests. The HP e3000 received the remote system's UNBIND request before receiving the response to the UNBIND the HP e3000 sent.

  • PEND_RST_L = Pending reset local. An UNBIND has been sent to the remote system, but no response has been received.

  • PEND_RST_N = Pending reset negative response. A BIND has been sent to the remote LU session, a negative response (-RSP) has been received from an intermediate routing node, and the SNA service must generate an UNBIND to send to the remote LU session.

  • PEND_RST_R = Pending reset remote. A deactivation request has been received from the remote system, but no response has been sent.

  • PEND_SON = Pending session outage notification. A Session Outage Notification (SON) deactivation request has been generated internally or received on the link. However, no response has been sent.

  • RESET = The initial state. No sessions exist.

The user is the name of the user or program that owns the session.

The trace file is the name of the trace file, if tracing has been turned on. If tracing is off, OFF is displayed.



SNACONTROL START

SNACONTROL STOP