Report field descriptions

  • The following fields are displayed for a TCP connection entry:
    Client Name
    See the Client name or User ID information in Netstat report general concepts for a detailed description.
    Client ID
    See the Client ID or Connection Number information in Netstat report general concepts for a detailed description.
    Local Socket
    See the Local Socket information in Netstat report general concepts for a detailed description.
    Foreign Socket
    See the Foreign Socket information in Netstat report general concepts for a detailed description.
    StartDate
    Date of the last one of the following events that occurred for the TCP connection or UDP endpoint:
    • UDP bind
    • TCP bind
    • TCP listen
    • TCP connection establishment
    StartTime
    Time of the last one of the following events that occurred for the TCP connection or UDP endpoint:
    • UDP bind
    • TCP bind
    • TCP listen
    • TCP connection establishment
    BytesIn
    The number of bytes of data the stack has received for this connection. This includes both the total bytes that the application has received and the total bytes in the receive buffer that have not yet been read by the application.
    Restriction: The TCP/IP stack maintains 64-bit counters for TCP connections and UDP endpoints. However, if you are running an IPv4-only stack, and the Netstat output is in the SHORT format, only the lower 32-bit counter value is displayed. If a large amount of data has been received, the number of bytes can exceed a 32-bit counter so the value displayed will appear to have been reset. Use the FORMAT/-M LONG output option on the Netstat command to cause Netstat to use the LONG format for the output. The LONG format displays the full 64-bit counter value. You can also specify the FORMAT parameter on the IPCONFIG profile statement to set FORMAT LONG as the default value for all Netstat commands.
    BytesOut
    The number of bytes of data the application has sent. This includes all the data that has been sent to the remote connection and all the data that has not been sent but is buffered and waiting to be sent by the local stack.
    Restriction: The TCP/IP stack maintains 64-bit counters for TCP connections and UDP endpoints. However, if you are running an IPv4-only stack, and the Netstat output is in the SHORT format, only the lower 32-bit counter value is displayed. If a large amount of data has been sent, the number of bytes can exceed a 32-bit counter so the value displayed will appear to have been reset. Use the FORMAT/-M LONG output option on the Netstat command to cause Netstat to use the LONG format for the output. The LONG format displays the full 64-bit counter value. You can also specify the FORMAT parameter on the IPCONFIG profile statement to set FORMAT LONG as the default value for all Netstat commands.
    SegmentsIn
    The number of non-retransmitted TCP packets received for this connection.
    Guideline: This value, when displayed for a TCP connection across an SMC-R link, includes the number of Remote Direct Memory Access (RDMA) inbound operations.
    SegmentsOut
    The number of non-retransmitted TCP packets sent for this connection.
    Guideline: This value, when displayed for a TCP connection across an SMC-R link, includes the number of RDMA outbound operations.
    Last touched
    See the Last touched time information in Netstat report general concepts for a detailed description.
    State
    Describes the state of the TCP connection. See TCP connection status for more information.
    RcvNxt
    The sequence number of the next byte this side of the connection is expecting to receive. Each byte that is sent or received in a TCP connection has its own unique, ascending sequence number.
    SndNxt
    The sequence number of the next byte that the stack can send.
    ClientRcvNxt
    The sequence number of the next byte that the application will read from the receive buffer.
    ClientSndNxt
    The sequence number of the next byte of data that the application can add to the send buffer.
    InitRcvSeqNum
    The first sequence number that was received from the remote stack host when establishing the connection.
    InitSndSeqNum
    The first sequence number that the local stack sent out when establishing the connection.
    CongestionWindow
    The value that is used when congestion is detected in the network to limit the amount of data that is sent by the local stack. This value represents the maximum amount of data that is sent without waiting for an acknowledgment from the remote socket.
    SlowStartThreshold
    The slow-start threshold is used to determine whether the connection is recovering from congestion. If the congestion window is smaller than the slow-start threshold, the connection will take actions to more quickly recover from congestion.
    IncomingWindowNum
    The incoming window number is the maximum sequence number that the remote socket can send until the local application reads more data from the local socket.
    OutgoingWindowNum
    The outgoing window number is the maximum sequence number that can be sent without waiting for the remote socket to read data (see the send window).
    SndWl1
    The sequence number from the segment that last updated the SndWnd field.
    SndWl2
    The acknowledgment number from the segment that last updated the SndWnd field.
    SndWnd
    The amount of available buffer space that is advertised by the remote side into which data can be sent.
    MaxSndWnd
    The largest send window the remote socket has sent to the local socket.
    SndUna
    This value is the sequence number of the first byte of data in the local socket's send buffer that has not been acknowledged by the remote socket.
    rtt_seq
    The sequence number of the byte of data sent in a packet for which the local socket is measuring the round-trip time (the time it takes between the local socket sending a packet and receiving an acknowledgment from the remote socket).
    MaximumSegmentSize
    The largest amount of data the local socket can send in a single packet.
    DSField
    The Differentiated Services Code Point value being used for this connection.

    The DSField represents one of the following values:

    • If there is a Service Policy Agent policy in effect for this entry, one of the following values is used:
      • The ToS value defined by RFC 791 and RFC 1349.
      • The Differentiated Services field value defined by RFC 2474.
    • If there is no Service Policy Agent policy in effect for this entry, the value is 0.
    Round-trip information
    The round-trip time is the amount of time that elapses between the time a packet is sent and the time an acknowledgment for that packet is received.
    Smooth trip time
    The average amount of time it has taken for a packet to be sent and an acknowledgment to be received for this connection, measured in milliseconds.
    SmoothTripVariance
    The average variation in round-trip time, measured in milliseconds.
    ReXmt
    The total number of times a packet has been retransmitted for this connection. This count is historical for the life of the connection.
    ReXmtCount
    The number of times the last packet that was sent has been retransmitted.
    DupACKs
    The total number of duplicate acknowledgments that have been received by this connection.
    RcvWnd
    The amount of available buffer space that is advertised to the remote side into which data can be received.
    SockOpt
    Socket option flag. For TCP/IP stacks that are not IPv6 enabled, it is a one-byte hexadecimal value of common socket options. For IPv6-enabled TCP/IP stacks, it is a one-byte hexadecimal value of common socket options, followed by a one-byte hexadecimal value of IPv6-specific socket options.

    Common socket options:

    80   1... ....
    Indicates that the socket option SO_REUSEADDR has been set for this socket. This socket option allows the socket to be bound to the same port that other sockets are bound to.
    40   .1.. ....
    Indicates that the socket option SO_OOBINLINE has been set for this socket. If this socket option is set, out-of-band data is returned in a normal read operation. If this socket option is not set, out-of-band data can be retrieved only by setting the MSG_OOB flag on a read operation.
    20   ..1. ....
    Indicates that the socket option SO_LINGER has been set for this socket. The SO_LINGER socket option allows an application to specify whether unsent data is discarded when the socket is closed, and how long to wait if the data is not discarded.
    10   ...1 ....
    Indicates that the socket option SO_DONTROUTE has been set for this socket. If this socket option is set, data is sent without regard to routes. This is equivalent to the MSG_DONTROUTE flag on a write operation.
    08   .... 1...
    Indicates the socket option TCP_NODELAY has been set for this socket. Unless this socket option is set, the TCP/IP stack will attempt to optimize the sending of small data packets by holding them briefly in case it has more data to send.
    04   .... .1..
    Indicates that the SO_KEEPALIVE socket option has been set for this socket. If this socket option is set, the TCP/IP stack will periodically send empty packets to the remote stack to make sure the connection is still alive.

    IPv6 socket options:

    80   1... ....
    Indicates that the IPV6_UNICAST_HOPS option has been set for this socket.
    20    ..1. ....
    Indicates that the IPV6_USE_MIN_MTU for unicast option has been set for this socket.
    10   ...1 ....
    Indicates that the IPV6_TCLASS option has been set for this socket.
    08   .... 1...
    Indicates that the IPV6_RECVTCLASS option has been set for this socket.
    04   .... .1..
    Indicates that the IPV6_RECVHOPLIMIT option has been set for this socket.
    02   .... ..1.
    Indicates that the IPV6_V6ONLY option has been set for this socket.
    Any other value
    Used for diagnostic purposes only under the direction of IBM® Service personnel.
    TcpTimer
    TCP timer flag. It is a one-byte hexadecimal value that is used for diagnostic purposes only under the direction of IBM Service personnel.
    TcpSig
    TCP signal flag. It is a one-byte hexadecimal value and can have one of the following values:
    80   1... ...
    Indicates the application has requested to receive the SIGURG signal when urgent data is received on this socket.
    40   .1.. ....
    Indicates the application has requested to receive the SIGIO signal when data is received on this socket.
    Any other value
    Is used for diagnostic purposes only under the direction of IBM Service personnel.
    TcpSel
    TCP select flag. It is a one-byte hexadecimal value that is used for diagnostic purposes only under the direction of IBM Service personnel.
    TcpDet
    Special TCP protocol flag. It is a one-byte hexadecimal value:
    04   .... .1..
    Indicates the TCP_KEEPALIVE socket option has been set for this socket. This socket option is used to set a socket-specific time interval value for use with the SO_KEEPALIVE socket option. See the description of field SockOpt for an explanation of the SO_KEEPALIVE socket option. The TCP_KEEPALIVE time interval value is in effect only if the SO_KEEPALIVE socket option is set for the socket.
    Any other value
    Is used for diagnostic purposes only under the direction of IBM Service personnel.
    TcpPol
    TCP poll flag. It is a one-byte hexadecimal value to be used for diagnostic purposes only under the direction of IBM Service personnel.
    TcpPrf
    A 1-byte hexadecimal TCP performance flag that can have any ofthe following values:
    80 1... ....
    Indicates that this connection is eligible for dynamic right sizing (DRS) optimization support. For more information about DRS, see TCP receive window in z/OS Communications Server: IP Configuration Guide.
    40 .1.. ....
    Indicates that DRS is active for this connection so that the stack automatically tunes the receive buffer size. The ReceiveBufferSize field shows the current size of the receive buffer for this connection.
    02 .... ..1.
    Indicates that DRS was active for this connection, but has been disabled. This is caused by the associated application not reading the data as fast as the data arrives and CSM high virtual common or fixed storage being constrained.
    Any other value
    Used for diagnostic purposes only under the direction of IBM Service personnel.
    TcpPrf2
    A 1-byte hexadecimal TCP performance flag that can have any of the following values:
    40 ..1. ....
    If outbound right sizing (ORS) is active for this connection, the stack expanded the send buffer beyond its original size. For more information about ORS, see TCP send window in z/OS Communications Server: IP Configuration Guide.
    20 ..1. ....
    Indicates that this connection is eligible for ORS optimization support.
    10 ...1 ....
    Indicates that ORS is active for this connection so that the stack automatically tunes the send buffer size. The SendBufferSize field shows the current size of the send buffer for this connection.
    Any other value
    Used for diagnostic purposes only under the direction of IBM Service personnel.
    TcpPrf3
    Used for diagnostic purposes only under the direction of IBM Service personnel.
    DelayAck
    Indicates how the TCP/IP stack controls the transmission of acknowledgments for packets received with the PUSH bit on in the TCP header. This field can have the following values:
    AutoYes
    The TCP/IP stack has autonomically determined to delay transmission of acknowledgments for packets received with the PUSH bit on in the TCP header.
    Yes
    The TCP/IP stack delays transmission of acknowledgments for packets received with the PUSH bit on in the TCP header.
    AutoNo
    The TCP/IP stack has autonomically determined to immediately return acknowledgments for packets received with the PUSH bit on in the TCP header.
    No
    The TCP/IP stack immediately returns acknowledgments for packets received with the PUSH bit on in the TCP header.
    QOSPolicy
    Indicates whether a matching QoS policy rule has been found for this connection. This field can have the following values:
    No
    Indicates that a matching QoS policy rule was not found for this connection.
    Yes
    Indicates that a matching QoS policy rule was found for this connection. When the QOSPolicy field has the value Yes, the following information is displayed:
    QOSRuleName
    The name of the Policy rule that is in use for this connection. This policy is for outbound traffic only.
    TTLSPolicy
    Indicates whether a matching Application Transparent Transport Layer Security (AT-TLS) policy rule has been found for this connection. This set of fields is not displayed if the AT-TLS function was disabled when the connection was established (NOTTLS was specified on the TCPCONFIG statement or is in effect by default) or policy lookup has not yet occurred.
    • TTLSPolicy: No indicates that no matching AT-TLS policy rule was found for this connection. There is no rule or action listed.
    • TTLSPolicy: Yes indicates one of the following cases:
      • A matching AT-TLS policy rule was found for this connection with an indication that AT-TLS should be enabled (TTLSEnabled ON was specified on the TTLSGroupAction). The rule and actions are displayed.
      • A matching AT-TLS policy rule was found for this connection with an indication that AT-TLS should be disabled (TTLSEnabled OFF was specified on the TTLSGroupAction). The rule and actions are displayed.
    TTLSRule
    The name of the AT-TLS policy rule that is in use for this connection, followed by (Stale) when the rule is no longer available for use by new connections. This field is not displayed when the connection does not match a policy rule.
    TTLSGrpAction
    The name of the AT-TLS policy group action that is in use for this connection, followed by (Stale) when the action is no longer available for use by new connections. This field is not displayed when the connection does not match a policy rule.
    TTLSEnvAction
    The name of the AT-TLS policy environment action that is in use for this connection, followed by (Stale) when the action is no longer available for use by new connections. This field is not displayed when the connection does not match a policy rule or when no TTLSEnvironmentAction was specified.
    TTLSConnAction
    The name of the AT-TLS policy connection action that is in use for this connection, followed by (Stale) when the action is no longer available for use by new connections. This field is not displayed when the connection does not match a policy rule or when no TTLSConnectionAction was specified.
    RoutingPolicy
    Indicates whether a matching routing policy rule has been found for this connection. This field can have the following values:
    No
    Indicates that no matching routing policy rule was found for this connection.

    For an Enterprise Extender (EE) UDP socket entry, the RoutingPolicy value is always No. Display the routing policy information for an Enterprise Extender (EE) UDP socket entry by using the DISPLAY NET,EEDIAG,TEST=YES command. See z/OS Communications Server: SNA Operation for details.

    Yes
    Indicates that a matching routing policy rule was found for this connection.

    When the RoutingPolicy value is Yes, the following information is displayed:

    RoutingTableName
    The name of the routing table that was used to find the route for this connection or *NONE* if a route was not found. The value EZBMAIN is displayed when the main routing table was used.
    RoutingRuleName
    The name of the routing policy rule in use for this connection.
    Start of changeZERTPolicyEnd of change
    Start of changeIndicates whether a matching zERT enforcement policy rule has been found for this connection. This set of fields is not displayed if the ZERT function was disabled when the connection was established (NOZERT was specified on the GLOBALCONFIG statement or is in effect by default) or policy lookup has not yet occurred. This field can have the following values.
    No
    Indicates that no matching zERT enforcement policy rule was found for this connection.
    Yes
    Indicates that a matching zERT enforcement policy rule was found for this connection.
    When the ZERTPolicy value is Yes, the following information is displayed:
    ZERTIPSecRule
    The name of the zERT IPsec policy rule that is in use for this IPsec-protected connection, followed by (Stale) when the rule is no longer available for use by new IPsec-protected connections. This field is not displayed when the connection is not protected by IPsec or when the connection does not match a zERT IPsec policy rule.
    ZERTIPSecAction
    The name of the zERT IPsec policy action that is in use for this IPsec-protected connection, followed by (Stale) when the action is no longer available for use by new IPsec-protected connections. This field is not displayed when the connection is not protected by IPsec or when the connection does not match a zERT IPsec policy rule.
    ZERTTLSRule
    The name of the zERT TLS policy rule that is in use for this TLS-protected connection, followed by (Stale) when the rule is no longer available for use by new TLS-protected connections. This field is not displayed when the connection is not protected by TLS or when the connection does not match a zERT TLS policy rule.
    ZERTTLSAction
    The name of the zERT TLS policy action that is in use for this TLS-protected connection, followed by (Stale) when the action is no longer available for use by new TLS-protected connections. This field is not displayed when the connection is not protected by TLS or when the connection does not match a zERT TLS policy rule.
    ZERTSSHRule
    The name of the zERT SSH policy rule that is in use for this SSH-protected connection, followed by (Stale) when the rule is no longer available for use by new SSH-protected connections. This field is not displayed when the connection is not protected by SSH or when the connection does not match a zERT SSH policy rule.
    ZERTSSHAction
    The name of the zERT SSH policy action that is in use for this SSH-protected connection, followed by (Stale) when the action is no longer available for use by new SSH-protected connections. This field is not displayed when the connection is not protected by SSH or when the connection does not match a zERT SSH policy rule.
    ZERTNoProtRule
    The name of the zERT enforcement policy rule that is in use for this connection which has no recognized protection, followed by (Stale) when the rule is no longer available for use by connections with no recognized protection. This field is not displayed when the connection is protected by IPsec, TLS, or SSH or when the connection does not match a zERT enforcement policy rule for connections with no recognized protection.
    ZERTNoProtAction
    The name of the zERT enforcement policy action that is in use for this connection which has no recognized protection, followed by (Stale) when the action is no longer available for use by connections with no recognized protection. This field is not displayed when the connection is protected by IPsec, TLS, or SSH or when the connection does not match a zERT enforcement policy rule for connections with no recognized protection.
    End of change
    ReceiveBufferSize
    The number of bytes received from the remote application that this connection is allowed to maintain in a buffer. All the data that is received is kept in a buffer until the local application reads the data.
    SendBufferSize
    The number of bytes the local application has sent that this connection is allowed to maintain in a buffer. All data that the application has sent is kept in the buffer until the remote side acknowledges receiving the sent data.
    TcpClusterConnFlag
    TCP cluster connection type flag. It is a one-byte hexadecimal field and can have one of the following values:
    80   1... ....
    Indicates that the SO_CLUSTERCONNTYPE socket option or the SIOCGPARTNERINFO ioctl was requested.
    08   .... 1...
    If the SO_CLUSTERCONNTYPE socket option or the SIOCGPARTNERINFO ioctl was issued for this socket, this bit indicates that the communication from this node to the stack hosting the partner application is not sent on links/interfaces exposed outside the cluster (sysplex).
    04   .... .1..
    If the SO_CLUSTERCONNTYPE socket option or the SIOCGPARTNERINFO ioctl was issued for this socket, this bit indicates that the connection partners are in the same MVS™ image.
    02   .... ..1.
    If the SO_CLUSTERCONNTYPE socket option or the SIOCGPARTNERINFO ioctl was issued for this socket, this bit indicates that the connection partners are in the same cluster.
    01   .... ...1
    If the SO_CLUSTERCONNTYPE socket option or the SIOCGPARTNERINFO ioctl was issued for this socket, this bit indicates that the connection partners are not in the same cluster.
    00   .... ....
    If the TcpTrustedPartner flag indicates that the SIOCSPARTNERINFO ioctl has been successfully issued or inherited from the listener socket, this value indicates that the SO_CLUSTERCONNTYPE socket option or the SIOCGPARTNERINFO ioctl has not been issued for this socket.
    Any other value
    Used for diagnostic purposes only under the direction of IBM Service personnel.

    For more information about the cluster connection type, see the z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference. For more information about the SIOCGPARTNERINFO ioctl, see z/OS Communications Server: IP Programmer's Guide and Reference.

    TcpTrustedPartner
    The TCP trusted connection flag is displayed in the following situations:
    • Security credentials of a partner within a sysplex or subplex have been retrieved over a trusted TCP connection using the SIOCGPARTNERINFO ioctl.
    • The SIOCSPARTNERINFO ioctl has been issued for the socket.

    The TCP trusted connection flag is a 1-byte hexadecimal field and can have the following values:

    80   1... ....
    This bit indicates that the partner address-space user ID has been retrieved, as well as the task-level user ID if it is available.
    40   .1.. ....
    This bit indicates that the partner address-space UTOKEN has been retrieved, as well as the task-level UTOKEN if it is available.
    20   ..1. ....
    This bit indicates that the SIOCSPARTNERINFO ioctl has been successfully issued or inherited from the listener socket.

    For information about trusted TCP/IP connections and the SIOCGPARTNERINFO and SIOCSPARTNERINFO ioctl calls, see z/OS Communications Server: IP Programmer's Guide and Reference.

    ReceiveDataQueued
    The number of bytes of data on the receive queue from the remote application yet to be read. This field is not displayed for a connection that is in listen state. The amount of data queued can be up to double the ReceiveBufferSize size. When the number of bytes is not zero, the following information is displayed:
    OldQDate
    The date of the oldest data on the receive queue.
    OldQTime
    The time of the oldest data on the receive queue. This value does not include leap seconds.
    The ReceiveDataQueued information is not displayed for a connection that is in listen state.
    SendDataQueued
    The number of bytes of data on the send queue waiting for the remote side to acknowledge. This field is not displayed for a connection that is in listen state. The amount of data queued can be up to double the size of the SendBufferSize. When the number of bytes is not zero, the following information is displayed:
    OldQDate
    The date of the oldest data on the send queue.
    OldQTime
    The time of the oldest data on the send queue. This value does not include leap seconds.
    The SendDataQueued information is not displayed for a connection that is in listen state.
    SendStalled
    Indicates whether this connection's send data flow is stalled. The send data flow is considered stalled if one or more of the following conditions are true:
    • The TCP send window size is less than 256 or is less than the smaller of the largest send window that has been seen for the connection and the default MTU. The TCP send window size is set based on values provided by the TCP peer. The default MTU for IPv4 is 576. The default MTU for IPv6 is 1280.
    • The TCP send queue is full and the data is not being retransmitted.
    This field is not displayed for a connection that is in listen state. If the value is Yes, then this connection's send data flow is stalled.
    SMC Information
    • For server connections, this section is the SMC information for connections in Listen state. This section is displayed for connections in one of the following situations:
      • At least one Peripheral Component Interconnect® Express (PCIe) function ID (PFID) was defined by using the SMCR parameter of the GLOBALCONFIG statement.
      • The SMCD parameter was defined in the GLOBALCONFIG statement.
      The SMC Information section contains the following information that is related to inbound connections to the server application:
      SMCDCurrConns
      The number of currently established connections, which use SMC-D and have an Start of changeSMCDV1Status|SMCDV2StatusEnd of change of Active, to this server. The value of SMCDCurrConns is a subset of the value of the CurrentConnections field in this report.
      SMCDTotalConns
      The total number of connections to this server that uses SMC-D. The value of SMCDTotalConns is a subset of the value of the ConnectionsIn field in this report.
      SMCRCurrConns
      The number of currently established connections with an Start of changeSMCRV1Status|SMCRV2StatusEnd of change of Active to this server that uses SMC-R. The value of SMCRCurrConns is a subset of the value of the CurrentConnections field in this report.
      SMCRTotalConns
      The total number of connections to this server that uses SMC-R. The value of SMCRTotalConns is a subset of the value of the ConnectionsIn field in this report.
      UseSMC
      Indicates whether SMC is used. This field is displayed only for a connection that is in Listen state when the AUTOSMC monitoring function is enabled. The AUTOSMC monitoring function is enabled by specifying the AUTOSMC subparameter of the SMCGLOBAL parameter on the GLOBALCONFIG profile statement. The AUTOSMC subparameter of the SMCGLOBAL parameter on GLOBALCONFIG is the default setting. For more information about the AUTOSMC monitoring function, see AUTOSMC monitoring function in z/OS Communications Server: IP Configuration Guide.
      Guideline: A client is best suited for both SMC-R and SMC-D communications, or is best suited for neither of the communications. The workload pattern criteria are the same for determining whether a client is best suited for SMC-R and SMC-D communications.
      Yes
      Indicates one of the following situations:
      • This server had SMC configured on its PORT or PORTRANGE statement.
      • The AUTOSMC monitoring function detected during the previous monitoring interval that most client connections that request SMC-R or SMC-D to this server had a workload pattern that was best suited for SMC communications.
      No
      Indicates one of the following situations:
      • This server had NOSMC configured on its PORT or PORTRANGE statement.
      • The AUTOSMC monitoring function detected during the previous monitoring interval that most client connections that request SMC-R or SMC-D to this server did not have a workload pattern that was best suited for SMC communications.
      Source
      Indicates how the value of UseSMC is determined. This field is displayed only for a connection that is in Listen state when the AUTOSMC monitoring function is enabled. The AUTOSMC monitoring function is enabled by specifying the AUTOSMC subparameter of the SMCGLOBAL parameter on the GLOBALCONFIG profile statement. The AUTOSMC subparameter of the SMCGLOBAL parameter on GLOBALCONFIG is the default setting. For more information about the AUTOSMC monitoring function, see AUTOSMC monitoring function in z/OS Communications Server: IP Configuration Guide.
      AUTOSMC
      Indicates that the value of UseSMC was determined by the AUTOSMC monitoring function.
      Config
      Indicates that the value of UseSMC was determined by the configuration of the PORT or PORTRANGE statement for the server.
      AutoSMC%
      The percentage of inbound TCP connections that request SMC-R or SMC-D to this server that had a workload pattern best suited for SMC communications during the last AUTOSMC monitoring interval. An N/A will be displayed if the number of connections to analyze in the last monitored interval is not large enough. Only connections that meet the criteria for SMC-R or SMC-D enablement are monitored. These connections where the peers are SMC-R or SMC-D enabled, can be reached directly over an SMC-R or SMC-D eligible subnet, do not have IPSEC enabled, and do not exploit the Fast Response Cache Accelerator (FRCA) feature. This field is only displayed when the AUTOSMC monitoring function is enabled and Source is AutoSMC. The AUTOSMC monitoring function is enabled by the AUTOSMC subparameter of the SMCGLOBAL parameter on the GLOBALCONFIG profile statement. The AUTOSMC subparameter of the SMCGLOBAL parameter on GLOBALCONFIG is the default setting.
      Guideline: A client is best suited for both SMC-R and SMC-D communications, or is best suited for neither of the communications. The workload pattern criteria are the same for determining whether a client is best suited for SMC-R and SMC-D communications.
    • For client connections, this section is the SMC information for established connections. This section is displayed for connections in one of the following situations:
      • At least one Peripheral Component Interconnect Express (PCIe) function ID (PFID) was defined by using the SMCR parameter of the GLOBALCONFIG statement.
      • The SMCD parameter was defined in the GLOBALCONFIG statement.
      The SMC Information section contains the following information:
      Start of changeSMCDV1Status|SMCDV2Status|SMCStatusEnd of change
      Indicates whether this connection is traversing a Shared Memory Communications - Direct Memory Access (SMC-D) link. Start of changeThe V1 or V2 in the field name indicates the SMC version (SMCDV1Status for SMC version 1 and SMCDV2Status for SMC version 2). SMCStatus means this connection could not use either version of SMC-D and the value will be Inactive. End of changeThis field can have the following values:
      Inactive
      Indicates that this connection does not use an SMC-D link.
      When the Start of changeSMCDV1Status|SMCDV2Status|SMCStatusEnd of change value is Inactive, the following information is displayed:
      SMCReason reasonCode - reasonText
      This field explains why the connection is not using an SMC-D link. The following reason codes are possible values.
      Note: An asterisk (*) might be displayed after the reason code value, for example, 5302*. The asterisk indicates that a previous attempt to establish an SMC-D link to the destination IP address failed and that TCP/IP cached this failure. Therefore, TCP/IP did not attempt to use SMC-D for this connection. For more information about SMC-D caching, see GLOBALCONFIG statement in z/OS Communications Server: IP Configuration Reference.
      Start of change5226 - No SMC-Rv2 route found for remote peerEnd of change
      Start of changeNo route to the SMC-Rv2 IP address for the remote peer is found. As a result, an SMC-Rv2 link is not established.End of change
      5302 - Route not SMC eligible
      SMC-D communications cannot be used for this connection because of connectivity issues or the absence of an active interface that supports SMC-D processing.
      5306 - No storage for SMC negotiation
      Storage for SMC-D negotiation over this TCP connection cannot be obtained.
      5307 - Connection uses lPSec
      SMC-D communications cannot be used for this connection because the connection is using IP security.
      5308 - FRCA server
      SMC-D communications cannot be used for this connection because the connection is used by a Fast Response Cache Accelerator (FRCA) server.
      5309 - Pascal application
      SMC-D communications cannot be used because the connection is used by a Pascal API application.
      530A - NOSMC Port server
      SMC-D communications cannot be used for this connection because the server port was configured with the NOSMC option.
      530C - No prefix on interface
      SMC-D communications cannot be used for this connection because of no valid IPv6 prefixes for the associated OSD or HiperSockets interface.
      530D - AUTOSMC detected workload
      SMC-D communications cannot be used for this connection because of AUTOSMC monitoring. AUTOSMC monitoring detects whether SMC-D is suitable for workload on inbound connections to a particular server. For more information about the AUTOSMC monitoring function, see AUTOSMC monitoring function in z/OS Communications Server: IP Configuration Guide.
      530E - No active ISMs for the PNetID
      No active Internal Shared Memory (ISM) interface is detected for the PNetID.
      Start of change530F - Peer did not request SMC-Dv1End of change
      Start of changeThe remote connection peer is not configured to use SMC-Dv1 communications.End of change
      Start of change5310 - SMC version mismatchEnd of change
      Start of changeThe received SMC proposal did not match the SMC-D version supported at this node. End of change
      Start of change5311 - System EID mismatchEnd of change
      Start of changeThe system generated EID received in the SMC proposal did not match the system generated EID of this node. End of change
      Start of change5312 - Dest IP addr in Exclude listEnd of change
      Start of changeThe connection destination IP address was configured in an SMCGLOBAL SMCEXCLUDE list.End of change
      Start of change5313 - Dest IP addr not in Permit listEnd of change
      Start of changeThe connection destination IP address was not configured in an SMCGLOBAL SMCPERMIT list.End of change
      Start of change5315 - SMC-Dv1 not enabled locallyEnd of change
      Start of changeSMC-Dv1 was not configured or enabled on this node.End of change
      Start of change5316 - Peer did not include SMC optionEnd of change
      Start of changeThe remote connection peer did not request to use SMC for this connection during connection establishment.End of change
      Start of change5322 - SMC EID mismatchEnd of change
      Start of changeThe SMCEIDs received from the remote connection peer did not match any SMCEIDs configured on this node.End of change
      Start of change5325 - Peer did not request SMC-Dv2End of change
      Start of changeThe remote connection peer did not request to use SMC-Dv2 for this TCP connection.End of change
      Start of change5326 - SMCDv2 not enabled locallyEnd of change
      Start of changeSMCDv2 was not configured or enabled on this node.End of change
      5708 - Peer not reachable for SMC-D
      The peer host supports SMC-D, but the peer is not reachable via SMC-D. For example, the peer might be located on a different CEC, the peer might not have SMC-D enabled for the same PNetID, or the defined VLANs for SMC-D are not consistent on both peers.
      5803 - Insufficient virtual storage
      SMC-D communications cannot be used for this connection because TCP private 64-bit virtual storage could not be allocated for a direct memory buffer (DMB).
      5804 - SMCD FIXEDMemory limit exceeded reached
      SMC-D communications cannot be used for this connection because the required SMC-D memory could not be allocated.
      5805 - TCP connection limit reached
      SMC-D communications cannot be used for this connection because another DMB for a new connection could not be obtained.
      5806 - VLAN ID not found
      SMC-D communications cannot be used for this connection because no VLAN that SMC-D enabled was found.
      5809 - No qualifying active ISMs
      No active ISM interfaces are detected in the SMC-D layer that can be used for this TCP connection.
      5819 - Peer is out of synch
      SMC-D communications cannot be used for this connection because of a condition that the peer is out of synchronization during negotiation.
      Start of change581E - Mismatch subnet/no PNetIDEnd of change
      Start of changeSMC-Dv1 communications cannot be used for this connection because the peer does not have an active interface in the same subnet with a PNetID that is eligible for SMC-Dv1.End of change
      5821 - Both peers reside on the same endpoint
      SMC-D communications cannot be used for this connection because both endpoints of the connection reside on the same endpoint. Same LPAR and the same TCP/IP stack instance.
      reasonCode - Internal error
      SMC-D communications cannot be used for this connection because of an internal error.
      reasonCode - *Peer generated*
      SMC-D communications cannot be used for this connection because the peer reported an error. See the peer product's documentation for additional details. A value of NA indicates that the TCP/IP stack could not obtain the reason code from the peer.
      Active
      Indicates that this connection uses an SMC-D link.
      When the Start of changeSMCDV1Status|SMCDV2StatusEnd of change value is Active, the following information is displayed and the Start of changeSMCRV1Status|SMCRV2Status fields areEnd of change not displayed:
      LocalSMCLinkId
      This field identifies the SMC-D link on this TCP/IP stack that this connection traverses. This TCP/IP stack generates the SMC-D link identifier dynamically.
      RemoteSMCLinkId
      This field identifies the SMC-D link on the remote peer that this connection traverses. The remote peer generates this SMC-D link identifier and provides it to this TCP/IP stack during SMC-D link activation.
      LocalSMCRcvBuf
      This field indicates the size of the DMB element that the local host uses for receiving data on this connection from the remote host.
      RemoteSMCRcvBuf
      This field indicates the size of the DMB element that the remote host uses for receiving data on this connection from the local host.
      Start of changeSMCEIDEnd of change
      Start of changeThis field is only valid if the SMC version is 2. The EID that the connection was setup with is displayed here. For SMC-D, this can be either a SYSTEMEID or a user defined SMCEID.End of change
      Start of changeSMCRV1Status|SMCRV2Status|SMCStatusEnd of change
      Indicates whether this connection is traversing a Shared Memory Communications over Remote Direct Memory Access (SMC-R) link. Start of changeThe V1 or V2 in the field name indicates the SMC version (SMCRV1Status for SMC version 1 and SMCRV2Status for SMC version 2). SMCStatus means this connection could not use either version of SMC-R and the value will be Inactive. End of changeThis field can have the following values:
      Inactive
      Indicates that this connection does not use an SMC-R link.
      When the Start of changeSMCRV1Status|SMCRV2StatusEnd of change value is Inactive, the following information is displayed:
      SMCReason reasonCode - reasonText
      This field explains why the connection is not using an SMC-R link. The following reason codes are possible values.
      Note: An asterisk (*) might be displayed after the reason code value, for example, 5013*. The asterisk indicates that a previous attempt to establish an SMC-R link to the destination IP address failed and that TCP/IP cached this failure. Therefore, TCP/IP did not attempt to use SMC-R for this connection. For more information about SMC-R caching, see GLOBALCONFIG statement in z/OS Communications Server: IP Configuration Reference.
      5013 - RDMA connectivity failure
      SMC-R communications cannot be used for this connection because the first attempt to send data over RDMA encountered an error. A likely reason for this error is a configuration problem in the switch that is connected to the RNIC interface. For example, an incorrect VLANID value was configured on the switch port for the RNIC interface.
      5203 - Insufficient virtual storage
      SMC-R communications cannot be used for this connection because TCP private 64-bit virtual storage could not be allocated for an RMB buffer.
      5204 - SMCR FIXEDMemory limit exceeded reached
      SMC-R communications cannot be used for this connection because the required SMC-R memory could not be allocated.
      5205 - TCP connection limit reached
      SMC-R communications cannot be used for this connection because another RMB for a new connection could not be obtained.
      5206 - VLAN ID not found
      SMC-R communications cannot be used for this connection because no VLAN that was enabled by SMC-R was found.
      5209 - No qualifying active RNICs
      No active "RoCE Express®" interfaces are detected in the SMC-R layer that can be used for this TCP connection.
      5219 - Peer is out of synch
      SMC-R communications cannot be used for this connection because the peer is out of synchronization condition during negotiation.
      Start of change521E - Mismatch subnet/no PNetIDEnd of change
      Start of changeSMC-Rv1 communications cannot be used for this connection because the peer does not have an active interface in the same subnet with a PNetID that is eligible for SMC-Rv1.End of change
      Start of change5226 - No route to SMC-Rv2 peerEnd of change
      Start of changeSMC-Rv2 communications cannot be used for this connection because no route was found to the remote SMC-Rv2 address.End of change
      Start of change5301 - Peer did not request SMC-Rv1End of change
      Start of changeThe remote connection peer is not configured to use SMC-Rv1 communications.End of change
      5302 - Route not SMC eligible
      SMC-R communications cannot be used for this connection because of connectivity issues or the absence of an active interface that supports SMC-R processing.
      5303 - No active RNICs for the PNetID
      No active "RoCE Express" features are detected for the PNetID.
      5304 - Connection is local
      The connection peers are on the same TCP/IP stack.
      5306 - No storage for SMC negotiation
      Storage for SMC-R negotiation over this TCP connection cannot be obtained.
      5307 - Connection uses lPSec
      SMC-R communications cannot be used for this connection because the connection is using IP security.
      5308 - FRCA server
      SMC-R communications cannot be used for this connection because the connection is used by a Fast Response Cache Accelerator (FRCA) server.
      5309 - Pascal application
      SMC-R communications cannot be used because the connection is used by a Pascal API application.
      530A - NOSMC Port server
      SMC-R communications cannot be used for this connection because the server port was configured with the NOSMC option.
      530B - Invalid MTU from peer
      SMC-R communications cannot be used for this connection because the peer had an invalid MTU size for this SMC-R link.
      530C - No prefix on interface
      SMC-R communications cannot be used for this connection because of no valid IPv6 prefixes for the associated OSD interface.
      530D - AUTOSMC detected workload
      SMC-R communications cannot be used for this connection because of AUTOSMC monitoring. AUTOSMC monitoring detects whether SMC-R is suitable for workload on inbound connections to a particular server. For more information about the AUTOSMC monitoring function, see AUTOSMC monitoring function in z/OS Communications Server: IP Configuration Guide.
      Start of change5314 - SMC-Rv1 not enabled locallyEnd of change
      Start of changeSMC-Rv1 was not configured or enabled on this node.End of change
      Start of change5316 - Peer did not include SMC optionEnd of change
      Start of changeThe remote connection peer did not request to use SMC for this connection during connection establishment.End of change
      Start of change5321 - SMC-Rv2 not enabled locallyEnd of change
      Start of changeSMC-Rv2 was not configured or enabled on this node.End of change
      Start of change5322 - SMC EID mismatchEnd of change
      Start of changeThe SMCEIDs received from the remote connection peer did not match any SMCEIDs configured on this node.End of change
      Start of change5323 - No v2 support for interfaceEnd of change
      Start of changeNo active SMCRv2 "RoCE Express" interfaces are detected in the SMC-R layer that can be used for this TCP connection.End of change
      Start of change5324 - Peer did not request SMC-Rv2End of change
      Start of changeThe remote connection peer did not request to use SMC-Rv2 for this TCP connection.End of change
      reasonCode - Internal error
      SMC-R communications cannot be used for this connection because of an internal error.
      reasonCode - *Peer generated*
      SMC-R communications cannot be used for this connection because the peer reported an error. See the peer product's documentation for additional details.
      Active
      Indicates that this connection uses an SMC-R link.
      When the Start of changeSMCRV1Status|SMCRV2StatusEnd of change value is Active, the following information is displayed:
      SMCGroupId
      This field identifies the SMC-R link group that includes the individual SMC-R link that this connection traverses. This TCP/IP stack generates the SMC-R link group identifier dynamically.
      LocalSMCLinkId
      This field identifies the SMC-R link on this TCP/IP stack that this connection traverses. This TCP/IP stack generates the SMC-R link identifier dynamically.
      RemoteSMCLinkId
      This field identifies the SMC-R link on the remote peer that this connection traverses. The remote peer generates this SMC-R link identifier and provides it to this TCP/IP stack during SMC-R link activation.
      LocalSMCRcvBuf
      This field indicates the size of the RMB element that the local host uses for receiving data on this connection from the remote host.
      RemoteSMCRcvBuf
      This field indicates the size of the RMB element that the remote host uses for receiving data on this connection from the local host.
      Start of changeSMCEIDEnd of change
      Start of changeThis field is only valid if the SMC version is 2. The EID that the connection was setup with is displayed here.End of change
    Ancillary Input Queue
    Indicates whether this connection is registered to the TCP bulk data ancillary input queue. This field is not displayed for a connection that is in listen state. This field can have the following values:
    N/A
    Indicates that this connection is not registered to the TCP bulk data ancillary input queue.
    Yes
    Indicates that this connection is registered to the TCP bulk data ancillary input queue.
    When the Ancillary Input Queue value is Yes, the following information is displayed:
    BulkDataIntfName
    This field indicates the name of the interface over which the inbound traffic is being received.
    ConnectionsIn
    The number of connections that a server has accepted. This field is displayed only for a connection that is in listen state. Once a connection has been accepted, communication can begin between the client and server applications.
    ConnectionsDropped
    The number of connection requests that have been received by the server and dropped because the maximum number of connection requests was already in the backlog queue. This field is displayed only for a connection that is in listen state.
    MaximumBacklog
    The maximum number of connections that a server maintains on the backlog queue. This field is displayed only for a connection that is in listen state. Connection requests that are received when the maximum number of connections requests is already on the backlog queue are typically discarded. A high maximum backlog queue value causes more simultaneous connection requests than a server can handle without having to drop requests.
    ConnectionFlood
    Indicates whether this server is experiencing a potential connection flood attack. A server is considered under a potential connection flood attack when backlog queue expansion is required to handle the incoming connection requests. The point where a potential connection flood attack is detected is based on the initial size of the backlog queue. A small initial backlog queue (for example, 10 entries) is allowed to expand twice before the server is considered under attack, while a server with a large initial backlog queue (for example, 500 entries) can expand once, up to a maximum of 768 entries, before it is considered under attack. This field is displayed only for a connection that is in listen state. If the value is Yes, then this server is experiencing a potential connection flood attack.
    CurrentBacklog
    The number of connections that are currently in the backlog queue. This field is displayed only for a connection that is in listen state. This value includes connections that are fully established and that are ready to be accepted by the server application; it also includes connections that are not yet fully established (the TCP connection establishment handshake is not yet complete). To determine the number of connections in the backlog queue that are not fully established, subtract the ServerBacklog value from the CurrentBacklog value. If the server application uses the Fast Response Cache Accelerator (FRCA) feature, fully established connections that are being serviced by TCP/IP from the FRCA cache are also included in the CurrentBacklog value. The FRCABacklog value in this report indicates the number of these connections.
    ServerBacklog
    The number of connections currently in the backlog queue that are established and that have not yet been accepted.
    FRCABacklog
    The number of connections currently in the backlog queue that are established FRCA connections and that are being serviced by TCP/IP from the FRCA cache. These connections do not need to be accepted by the server application. This field is applicable only for server applications that use the FRCA feature.
    CurrentConnections
    The number of currently established connections to the server. This field is displayed only for a connection that is in listen state.
    SEF
    The server accept efficiency fraction (SEF) is a measure, calculated at intervals of approximately one minute, of the efficiency of the server application in accepting new connection setup requests and managing its backlog queue. The value is displayed as a percentage. A value of 100 indicates that the server application is successfully accepting all its new connection setup requests. A value of 0 indicates that the server application is not responding to new connection setup requests. This field is displayed only for a connection that is in listen state.

    When using SHAREPORTWLM, the SEF value is used to modify the WLM server-specific weights, thereby influencing how new connection setup requests are distributed to the servers sharing this port. When using SHAREPORT, the SEF value is used to weight the distribution of new connection setup requests among the SHAREPORT servers. Whether SHAREPORT or SHAREPORTWLM are specified, the SEF value is reported back to the distributor to be used as part of the target server responsiveness fraction calculation, which influences how new connection setup requests are distributed to the target servers.

    Quiesced
    Indicates whether this server application has been quiesced for DVIPA sysplex distributor workload balancing. This field is displayed only for a connection that is in listen state. If the value is Dest, then this server will receive no new DVIPA sysplex distributor workload connections until the server application has been resumed. When the server application is resumed, the quiesced value changes to No.
    SharePort
    Indicates that multiple TCP listening servers are sharing the same port. This field is displayed only for a connection that is in listen state. The method used by TCP to distribute incoming connections to the listeners is indicated by Base or WLM described below. See the PORT profile statement in the z/OS Communications Server: IP Configuration Reference for more information on sharing a TCP port.
    Base
    Connections are proportionally distributed among the available shareport listeners using the SEF value. This value corresponds to the SHAREPORT parameter on the PORT profile statement.
    WLM
    Connections are distributed among the available shareport listeners using the normalized WLM server-specific weights. This value corresponds to the SHAREPORTWLM parameter on the PORT profile statement.
    RawWeight
    The raw composite weight for this server. The composite weight is based on the application's general CPU, zAAP, and zIIP processor utilization.
    NormalizedWeight
    The normalized values of the WLM server-specific weights. The original raw weights received from WLM are proportionally reduced for use by the distribution algorithm. Connections are distributed to these servers in a weighted round-robin fashion using the normalized weights if SHAREPORTWLM is specified on the PORT profile statement. The displayed normalized weight is shown after it has been modified by the SEF value. This field is shown regardless of the distribution method (Base or WLM) that is used.
    Abnorm
    Indicates whether the server application is experiencing conditions that cause transactions to complete abnormally. The value represents a rate of abnormal transaction completions per 1000 total transaction completions. It is applicable only for TCP applications that act as Subsystem Work Managers and report transaction status using Workload Management Services, such as IWMRPT. For example, the value 100 indicates that 10% of all transactions processed by the server application are completing abnormally. Under normal conditions, this value is 0. A nonzero value indicates that the server application has reported some abnormal transactions completions to WLM and that WLM has reduced the recommendation provided to sysplex distributor for this server instance. This reduction in the WLM recommendation enables more new TCP connections to be directed to servers that are not experiencing problem conditions that lead to abnormal transaction completions.

    The greater the Abnorm rate field value, the greater the reduction WLM applies to the recommendation for this target instance. For more information about the conditions that cause the abnormal transaction completions for a given server application, see the documentation provided by the server application.

    If applications do not provide this transaction status to WLM or SHAREPORTWLM is not configured, then this field has the value 0. For more information about workload management interfaces, see z/OS MVS Programming: Workload Management Services.

    Health
    The server application health indicator. This health indicator is available only for applications that provide this information to WLM using the IWM4HLTH or IWMSRSRG services. It provides a general health indication for an application or subsystem. Under normal circumstances, the value of this field is 100, indicating that the server is 100% healthy. Any value that is less than 100 indicates that the server is experiencing problem conditions that might prevent new work requests from being successfully processed. A value of less than 100 also causes the WLM to reduce the recommendation provided to the sysplex distributor for this server instance. This reduction in the WLM recommendation enables more new TCP connections to be directed to servers that are not experiencing problem conditions.

    The reduction in the WLM recommendation is proportional to value of the Health indicator. For example, if the health value is 20%, WLM reduces the recommendation for this server by 80%. For more information about the conditions leading to a health indicator of less than 100, see the documentation for the server application.

    If applications do not provide this health indicator to WLM or SHAREPORTWLM is not configured, then the value of this field is 100. For more information about workload management interfaces, see z/OS MVS Programming: Workload Management Services.

    RawCP
    The raw WLM server-specific general CP weight.
    RawzAAP
    The raw WLM server-specific zAAP weight.
    RawzIIP
    The raw WLM server-specific zIIP weight.
    PropCP
    The RawCP value modified by the proportion of CP capacity that is currently being consumed by the application's workload as compared to the other processors (zIIP and zAAP).
    PropzAAP
    The RawzAAP value modified by the proportion of zAAP capacity that is currently being consumed by the application's workload as compared to the other processors (CP and zIIP).
    PropzIIP
    The RawzIIP value modified by the proportion of zIIP capacity that is currently being consumed by the application's workload as compared to the other processors (CP and zAAP).
    ILWeighting
    The weighting factor the workload manager (WLM) uses when it compares displaceable capacity at different importance levels (ILs) in order to determine a SERVERWLM recommendation for each system.
    XcostzAAP
    The crossover cost that is applied to the workload that was targeted to run on a zAAP processor but that ran on the conventional processor.
    XcostzIIP
    The crossover cost that is applied to the workload that was targeted to run on a zIIP processor but that ran on the conventional processor.
    Application Data
    The application data that makes it easy for users to locate and display the connections that are used by the application. The beginning of the application data identifies the format of the application data area. For z/OS® Communications Server applications, see application data in the z/OS Communications Server: IP Programmer's Guide and Reference for a description of the format, content, and meaning of the data supplied by the application. For other applications, see the documentation that is supplied by the application. The data is displayed in character format if application data is present. Non-printable characters, if any, are displayed as dots.
  • The following fields are displayed for a UDP socket entry:
    Client Name
    See the Client name or User ID information in Netstat report general concepts for a detailed description.
    Client ID
    See the Client ID or Connection Number information in Netstat report general concepts for a detailed description.
    Local Socket
    See the Local Socket information in Netstat report general concepts for a detailed description.
    Foreign Socket
    See the Foreign Socket information in Netstat report general concepts for a detailed description.
    BytesIn
    The number of bytes of data the stack has received for this UDP socket. Includes both the total bytes that all applications have received for this socket and the total bytes in stack buffers that have not yet been read by any application.
    BytesOut
    Number of outbound bytes of user data sent from this socket.
    DgramIn
    The number of datagrams the stack has received for this UDP socket. This includes both the total datagrams that all applications have received for this socket and the total datagrams in stack buffers that have not yet been read by any application. A datagram is the group of data bytes contained in a UDP packet.
    DgramOut
    Number of outbound datagrams sent from this socket.
    Last touched time
    See the Last touched time information in Netstat report general concepts for a detailed description.
    MaxSendLim
    Maximum allowed size of a user datagram sent from this socket.
    MaxRecvLim
    Maximum allowed size of a user datagram received on this socket.
    SockOpt
    Socket option flag. For TCP/IP stacks that are not IPv6 enabled, it is a one-byte hexadecimal value of common socket options. For IPv6-enabled TCP/IP stacks, it is a one-byte hexadecimal value of common socket options, followed by a three-byte hexadecimal value of IPv6-specific socket options.
    IPv4 socket options:
    80  1... ....
    Allow use of broadcast address (IPv4 only)
    40  .1.. ....
    Allow loopback of datagrams
    20  ..1. ....
    Bypass normal routing
    10  ...1 ....
    Forward ICMP messages (Pascal API)
    08  .... 1...
    Last sent a multicast packet
    04  .... .1..
    Multicast packets can be received by this socket
    02  .... ..1.
    Reuse address
    other values
    reserved
    IPv6 socket options:
    Byte 1
    80  1... ....
    AF_INET6 socket
    40  .1.. ....
    IPV6_V6ONLY option set
    20  ..1. ....
    IPV6_RECVPKTINFO option set
    10  ...1 ....
    IPV6_RECVHOPLIMIT option set
    08  .... 1...
    IPV6_USE_MIN_MTU for unicast option
    04  .... .1..
    IPV6_PKTINFO src IP@ option set
    02  .... ..1.
    IPV6_PKTINFO interface index option set
    01  .... ...1
    IPV6_UNICAST_HOPS option set
    Byte 2
    80  1... ....
    IPV6_USE_MIN_MTU for multicast option set
    40  .1.. ....
    IPV6_RECVRTHDR option set
    20  ..1. ....
    IPV6_RECVHOPOPTS option set
    10  ...1 ....
    IPV6_RECVDSTOPTS option set
    08  .... 1...
    IPV6_RECVTCLASS option set
    04  .... .1..
    IPV6_NEXTHOP option set
    02  .... ..1.
    IPV6_RTHDR option set
    01  .... ...1
    IPV6_HOPOPTS option set
    Byte 3
    80  1... ....
    IPV6_DSTOPTS option set
    40  .1.. ....
    IPV6_RTHDRDSTOPTS option set
    20  ..1. ....
    IPV6_TCLASS option set
    10  ...1 ....
    IPV6_DONTFRAG option set
    08  .... 1...
    IPV6_RECVPATHMTU option set
    other values
    reserved
    DSField
    The Differentiated Services Code Point value being used for this connection.
    The DSField represents one of the following values:
    • If there is a Service Policy Agent policy in effect for this entry, one of the following values is used:
      • The ToS value defined by RFC 791 and 1349
      • The Differentiated Services field value defined by RFC 2474
    • For UDP entries for which there is no Service Policy Agent policy in effect but the entry is being used for an Enterprise Extender connection, the hexadecimal value of one of the following VTAM® IP Type of Service values is displayed:
      20     Low
      40     Medium
      80     High
      C0    Network
      See the z/OS Communications Server: SNA Network Implementation Guide for additional information.
    • If neither of these is true, this value is 0.
    QOSPolicy
    Indicates whether a matching QoS policy rule has been found for this connection. This field can have the following values:
    No
    Indicates that a matching QoS policy rule was not found for this connection.
    Yes
    Indicates that a matching QoS policy rule was found for this connection. When the QOSPolicy field has the value Yes, the following information is displayed:
    QOSRuleName
    The name of the Policy rule that is in use for this connection. This policy is for outbound traffic only.
    RoutingPolicy
    Indicates whether a matching routing policy rule has been found for this connection. This field can have the following values:
    No
    Indicates that no matching routing policy rule was found for this connection.
    Yes
    Indicates that a matching routing policy rule was found for this connection.
    When the RoutingPolicy field has the value Yes, the following information is displayed:
    RoutingTableName
    The name of the routing table that was used to find the route for this connection or *NONE* if a route was not found. The value EZBMAIN is displayed when the main routing table was used.
    RoutingRuleName
    The name of the routing policy rule in use for this connection.
    ReceiveDataQueued
    The number of bytes of data on the receive queue from the remote application yet to be read. When the number of bytes is not zero, the following information is displayed:
    OldQDate
    The date of the oldest datagram on the receive queue.
    OldQTime
    The time of the oldest datagram on the receive queue.
    ReceiveMsgCnt
    The number of datagrams on the receive queue.
    Multicast Specific
    Indicates that there is multicast data associated with this socket.

    For outgoing multicast data the following field descriptions apply:

    HopLimit
    The time-to-live value.
    LoopBack®
    Indicates whether datagrams are sent to loopback.
    OutgoingIpAddr
    The IPv4 IP address of the link on which the datagrams are sent. The value of this field is 0.0.0.0 if the socket has not been set with the IP_MULTICAST_IF setsockopt option. This field is not applicable for an IPv6 multicast entry.
    OutgoingIntf
    The IPv6 interface name on which the datagrams are sent. The value of this field is blank if the socket has not been set with the IPV6_MULTICAST_IF setsockopt option. This field is not applicable for an IPv4 multicast entry.
    For incoming multicast data the following field descriptions apply:
    Group
    The multicast IP addresses (up to a maximum of 20) for which data is being received.
    IncomingIpAddr
    The IPv4 IP address of the link over which multicast datagrams are accepted. This field is not applicable for an IPv6 multicast entry.
    IncomingIntf
    The IPv6 interface name over which multicast datagrams are accepted. This field is not applicable for an IPv4 multicast entry.
    SrcFltMd
    The source filter mode, which can have a value of either Include or Exclude. A source filter applies only to incoming multicast data. This source filter function is set by an application for the UDP socket. See the information about Designing multicast programs in the z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference for details. The source filter applies to all the IP addresses in the SrcAddr fields for the associated IncomingIPAddr address or IncomingIntf interface.
    Include
    Indicates that the socket receives only multicast datagrams that have a source IP address that matches an IP address indicated in the SrcAddr field.
    Exclude
    Indicates either that the source filter function is not active for the socket or that the application has requested to receive only multicast datagrams that have a source IP address that does not match an IP address indicated in the SrcAddr field. If the source filter function is not active or if the source filter function is active but no SrcAddr value is set, then the SrcAddr field contains the value None.
    SrcAddr
    Source address information for the socket.
    ipaddr
    The source IP addresses (up to a maximum of 64), used in conjunction with the SrcFltMd value, that is used to determine which incoming multicast datagrams should be passed to an application.
    None
    This value is displayed only when the source filter function is not active for the socket or when no source IP address is associated with group multicast address, IncomingIPAddr address, or IncomingIntf interface. The value of the corresponding SrcFltMd field is Exclude.
    StartDate
    See the StartDate information in Netstat report general concepts.
    StartTime
    See the StartTime information in Netstat report general concepts.