Netstat ALL/-A report
Displays detailed information about TCP connections and UDP sockets, including some recently closed ones. The purpose of this report is to aid in debugging problems with TCP connections and UDP sockets.
TSO syntax
Modifier
Target
Provide the report for a specific TCP/IP address space by using TCp tcpname. See The Netstat command target for more information about the TCp parameter.
Output
The default output option displays the output on the user's terminal. For other options, see The TSO NETSTAT command syntax or Netstat command output.
Filter
Netstat ALL/-A report z/OS UNIX syntax
Modifier
Target
Provide the report for a specific TCP/IP address space by using -p tcpname. See The Netstat command target for more information about the -p parameter.
Output
The default output option displays the output to z/OS® UNIX shell stdout. For other options, see The z/OS UNIX netstat command syntax or Netstat command output.
Filter
Filter description
- APPLD/-G appldata
- Filter the output of the ALL/-A report using the specified application data appldata. You can enter one filter value at a time and the specified value can be 40 characters in length.
- CLIent/-E clientname
- Filter the output of the ALL/-A report using the specified client name clientname. You can enter up to six filter values and each specified value can be eight characters in length.
- HOSTName/-H hostname
- Filter the output of the ALL/-A report
using the specified host name hostname.
You can enter one filter value at a time and the specified value can
be up to 255 characters in length.
Result: At the end of the report, Netstat displays the host name that the resolver used for the resolution and the list of IP addresses returned from the resolver that it used as filters.
Restrictions:- The HOSTName/-H filter does not support wildcard characters.
- Using the HOSTName/-H filter might cause delays in the output due to resolution of the hostname value depending upon resolver and DNS configuration.
- IPAddr/-I ipaddrIPAddr/-I ipaddr/prefixlengthIPAddr/-I ipaddr/subnetmask
- Filter the report output using the specified IP address ipaddr, ipaddr/prefixlength, or ipaddr/subnetmask. You can enter up
to six filter values. Each specified IPv4 ipaddr value can be up to 15 characters in length and each selected
IPv6 ipaddr value can be 45 characters in
length.
- ipaddr
- Filter the output of the ALL/-A report using the specified IP address ipaddr. For IPv6 addresses, the default prefixlength 128 is used.
- ipaddr/prefixlength
- Filter the output of the ALL/-A report using a specified IP address and prefix length ipaddr/prefixlength. For an IPv4 address, the prefix length range is 1 – 32. For an IPv6 address, the prefix length range is 1 – 128.
- ipaddr/subnetmask
- Filter the output of the ALL/-A report
using the specified IP address and subnet mask ipaddr/subnetmask. The IP address ipaddr in this
format must be an IPv4 IP address. Guidelines:
- The filter value ipaddr can be either the local or remote IP address.
- For an IPv6-enabled stack:
- Both IPv4 and IPv6 ipaddr values are accepted and can be mixed on the IPAddr/-I option.
- An IPv4-mapped IPv6 address is accepted as a valid ipaddr value and usually provides the same result as its IPv4 address.
Restrictions:- For an IPv4-only stack, only IPv4 ipaddr values are accepted.
- The filter value for an IPv6 address does not support wildcard characters.
- For a UDP endpoint socket, the filter value applies only to the local or source IP address.
- IPPort/-B ipaddr+portnum
- Filter the report output of the ALL/-A report using the specified IP
address and port number. You can enter up to six filter values. Each specified IPv4
ipaddr value can be up to 15 characters in length, denoting a single IPv4
IP address; each specified IPv6 ipaddr value can be up to 45 characters in
length, denoting a single IPv6 IP address. Valid portnum values are in the
range 0 – 65535. The filter values ipaddr and
portnum will match any combination of the local and remote IP address and
local and remote port.
Guidelines:
- The filter value ipaddr can be either the local or remote IP address.
- For an IPv6-enabled stack, the following apply:
- Both IPv4 and IPv6 ipaddr values are accepted and can be mixed on the IPPort/-B option.
- An IPv4-mapped IPv6 address is accepted as a valid ipaddr value and usually provides the same result as the IPv4 address.
Restrictions:- The ipaddr value in the IPPort/-B filter does not support wildcard characters.
- For an IPv4-only stack, only IPv4 ipaddr values are accepted.
- An entry is returned only when both the ipaddr and portnum values match.
- For a UDP endpoint socket, the filter value applies only to the local or source IP address and port.
- NOTN3270/-T
- Filter the output of the ALL/-A report, excluding TN3270 server connections.
- POrt/-P portnum
- Filter the output of the ALL/-A report
using the specified port number portnum.
You can enter up to six filter values. For all portnum values that were reserved by the same PORTRANGE profile
statement, only one output line is displayed.
Guideline: The port number can be either a local or remote port.
Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port. - SMCID/-U smcid
- Filter the output of the ALL/-A report by using the specified Shared Memory Communications over Remote Direct Memory Access (SMC-R) link, SMC-R link group, or Shared Memory Communications - Direct Memory Access (SMC-D) link identifier smcid. If an asterisk (*) is specified for the filter value, Netstat provides output only for the entries that are associated with SMC-R links, SMC-R link groups, and SMC-D links. You can enter one filter value at a time.
The filter value for CLIent/-E, IPAddr/-I, and APPLD/-G can be a complete string or a partial string using wildcard characters. A wildcard character can be an asterisk (*), which matches a null string or any character or character string, at the same position. A wildcard character can be a question mark (?), which matches any single character at the same position. For example, a string searchee matches with *ar?he*, but the string searhee does not match *ar?he*. To use the wildcard character on the IPAddr/-I filter, specify the value in the ipaddr format. The wildcard character is not accepted for the ipaddr/prefixlen or ipaddr/subnetmask format of IPAddr/-I values.
When you use z/OS UNIX netstat/onetstat command in a z/OS UNIX shell environment, take care if you use a z/OS UNIX MVS™ special character in a character string. It might cause an unpredictable result. To be safe, if you want to use a z/OS UNIX MVS special character in a character string, surround the character string with single (') or double (") quotation marks. For example, to use an asterisk (*) in the IP address, 10.*.0.0 for the -I filter, issue the command as: netstat -A -I '10.*.0.0'.
Command syntax examples
From TSO environment
NETSTAT ALL
Display detailed information about TCP connections and UDP sockets in the default
TCP/IP stack.
NETSTAT ALL TCP TCPCS6
Display detailed information about TCP connections and UDP sockets in TCPCS6 stack.
NETSTAT ALL TCP TCPCS8 (IPADDR 9.43.1.1 9.43.2.2
Display detailed information about those TCP connections and UDP sockets in TCPCS8
stack whose local or remote IP addresses match the specified filter IP address values.
NETSTAT ALL (PORT 2222 6666 88
Display detailed information about those TCP connections and UDP sockets in the
default TCP/IP stack whose local or remote ports match the specified filter port
numbers.
NETSTAT ALL SERVER TCP TCPCS
Display detailed information about those TCP connections in listen state on
TCP/IP stack TCPCS
NETSTAT ALL TCP TCPCS (IPPORT 127.0.0.1+21
Display detailed information about connections using ip address 127.0.0.1 and
port 21 on TCP/IP stack TCPCS
From UNIX shell environment
netstat -A
netstat -A -p tcpcs6
netstat -A -p tcpcs6 -I 9.43.1.1 9.43.2.2
netstat -A -P 2222 6666 88
netstat -A SERVER -p tcpcs
netstat -A -B 127.0.0.1+21 -p tcpcs
Report examples
The following examples are generated by using TSO NETSTAT command. Using the z/OS UNIX netstat command displays the data in the same format as the TSO NETSTAT command.
Not IPv6 enabled (SHORT format)
NETSTAT ALL MVS TCP/IP NETSTAT CS V2R2 TCPIP Name: TCPCS 22:24:30
Client Name: FTPD1 Client Id: 000000F9
Local Socket: 9.42.104.43..21 Foreign Socket: 9.42.103.165..1035
BytesIn: 0000000035 BytesOut: 0000000265
SegmentsIn: 0000000017 SegmentsOut: 0000000014
StartDate: 01/09/2012 StartTime: 22:04:11
Last Touched: 22:04:18 State: Establsh
RcvNxt: 0214444666 SndNxt: 0216505563
ClientRcvNxt: 0214443596 ClientSndNxt: 0216504670
InitRcvSeqNum: 0214443560 InitSndSeqNum: 0216504404
CongestionWindow: 0000007336 SlowStartThreshold: 0000065535
IncomingWindowNum: 0214477396 OutgoingWindowNum: 0216538247
SndWl1: 0214444666 SndWl2: 0216505563
SndWnd: 0000032684 MaxSndWnd: 0000032768
SndUna: 0216505563 rtt_seq: 0216505479
MaximumSegmentSize: 0000000524 DSField: 00
Round-trip information:
Smooth trip time: 102.000 SmoothTripVariance: 286.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000 RcvWnd: 0000032730
SockOpt: 85 TcpTimer: 00
TcpSig: 84 TcpSel: 60
TcpDet: E0 TcpPol: 00
TcpPrf: C0 TcpPrf2: 70
TcpPrf3: 00
DelayAck: AutoYes
QOSPolicy: No
TTLSPolicy: Yes
TTLSRule: server
TTLSGrpAction: group_action1
TTLSEnvAction: Environment1
RoutingPolicy: No
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
ReceiveDataQueued: 0000000000
SendDataQueued: 0000000000
SendStalled: No
Ancillary Input Queue: Yes
BulkDataIntfName: OSAQDIO4
Application Data: EZAFTP0S C USER1 PTS305
----
Client Name: US16SVR Client Id: 0000000D
Local Socket: 0.0.0.0..10007 Foreign Socket: 0.0.0.0..0
BytesIn: 0000024000 BytesOut: 0000032000
SegmentsIn: 0000000900 SegmentsOut: 0000001000
StartDate: 03/20/2014 StartTime: 17:53:16
Last Touched: 17:53:16 State: Listen
RcvNxt: 0000000000 SndNxt: 0000000000
ClientRcvNxt: 0000000000 ClientSndNxt: 0000000000
InitRcvSeqNum: 0000000000 InitSndSeqNum: 0000000000
CongestionWindow: 0000000000 SlowStartThreshold: 0000000000
IncomingWindowNum: 0000000000 OutgoingWindowNum: 0000000000
SndWl1: 0000000000 SndWl2: 0000000000
SndWnd: 0000000000 MaxSndWnd: 0000000000
SndUna: 0000000000 rtt_seq: 0000000000
MaximumSegmentSize: 0000000536 DSField: 00
Round-trip information:
Smooth trip time: 0.000 SmoothTripVariance: 1500.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000 RcvWnd: 0000131072
SockOpt: 00 TcpTimer: 00
TcpSig: 00 TcpSel: 20
TcpDet: C0 TcpPol: 00
TcpPrf: 00
QOSPolicy: No
RoutingPolicy: No
ReceiveBufferSize: 0000065536 SendBufferSize: 0000065536
ConnectionsIn: 0000000010 ConnectionsDropped: 0000000000
MaximumBacklog: 0000000004 ConnectionFlood: No
CurrentBacklog: 0000000000
ServerBacklog: 0000000000 FRCABacklog: 0000000000
CurrentConnections: 0000000005 SEF: 100
Quiesced: No
SMC Information:
SMCDCurrConns: 0000000002 SMCDTotalConns: 0000000015
SMCRCurrConns: 0000000004 SMCRTotalConns: 0000000008
UseSMC: Yes Source: AutoSMC
AutoSMC%: 090
----
Client Name: FTPD1 Client Id: 000000F6
Local Socket: 0.0.0.0..21 Foreign Socket: 0.0.0.0..0
BytesIn: 0000000000 BytesOut: 0000000000
SegmentsIn: 0000000000 SegmentsOut: 0000000000
StartDate: 01/09/2012 StartTime: 22:04:11
Last Touched: 21:41:09 State: Listen
RcvNxt: 0000000000 SndNxt: 0000000000
ClientRcvNxt: 0000000000 ClientSndNxt: 0000000000
InitRcvSeqNum: 0000000000 InitSndSeqNum: 0000000000
CongestionWindow: 0000000000 SlowStartThreshold: 0000000000
IncomingWindowNum: 0000000000 OutgoingWindowNum: 0000000000
SndWl1: 0000000000 SndWl2: 0000000000
SndWnd: 0000000000 MaxSndWnd: 0000000000
SndUna: 0000000000 rtt_seq: 0000000000
MaximumSegmentSize: 0000000536 DSField: 00
Round-trip information:
Smooth trip time: 0.000 SmoothTripVariance: 1500.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000 RcvWnd: 0000032768
SockOpt: 80 TcpTimer: 00
TcpSig: 00 TcpSel: 20
TcpDet: C0 TcpPol: 00
TcpPrf: 40
QOSPolicy: No
TTLSPolicy: No
RoutingPolicy: No
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
ConnectionsIn: 0000000001 ConnectionsDropped: 0000000000
MaximumBacklog: 0000000010 ConnectionFlood: No
CurrentBacklog: 0000000000
ServerBacklog: 0000000000 FRCABacklog: 0000000000
CurrentConnections: 0000000001 SEF: 98
Quiesced: No
SharePort: WLM
RawWeight: 63 NormalizedWeight: 15
Abnorm: 10 Health: 100
RawCP: 060 RawzAAP: 000 RawzIIP: 040
PropCP: 040 PropzAAP: 000 PropzIIP: 023
ILWeighting: 1 XcostzAAP: 001 XcostzIIP: 001
Application Data: EZAFTP0D
----
Client Name: TCPCS Client Id: 0000000C
Local Socket: 9.67.115.5..23 Foreign Socket: 9.27.11.182..4665
BytesIn: 0000001062 BytesOut: 0000000480
SegmentsIn: 0000000019 SegmentsOut: 0000000019
StartDate: 01/09/2012 StartTime: 16:46:15
Last Touched: 16:46:15 State: Establsh
RcvNxt: 3296375906 SndNxt: 3296308452
ClientRcvNxt: 3296375906 ClientSndNxt: 3296308452
InitRcvSeqNum: 3296374843 InitSndSeqNum: 3296307971
CongestionWindow: 0000340353 SlowStartThreshold: 0000016384
IncomingWindowNum: 3296408638 OutgoingWindowNum: 3296341180
SndWl1: 3296375906 SndWl2: 3296308452
SndWnd: 0000032728 MaxSndWnd: 0000032768
SndUna: 3296308452 rtt_seq: 3296308412
MaximumSegmentSize: 0000065483 DSField: 00
Round-trip information:
Smooth trip time: 37.000 SmoothTripVariance: 101.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000
SockOpt: 00 TcpTimer: 00
TcpSig: 00 TcpSel: C0
TcpDet: F0 TcpPol: 00
TcpPrf: 40
QOSPolicy: Yes
QOSRuleName: QosRule1
TTLSPolicy: Yes
TTLSRule: TTLSRule1
TTLSGrpAction: TTLSGrpAction1
TTLSEnvAction: TTLSEnvAction1
TTLSConnAction: TTLSConnAction1 (Stale)
RoutingPolicy: Yes
RoutingTableName: prTabl
RoutingRuleName: SecLow2
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
ReceiveDataQueued: 000000002C
OldQDate: 09/15/06 OldQTime: 03:36:32
SendDataQueued: 000002C000
OldQDate: 09/15/06 OldQTime: 03:36:32
SendStalled: No
SMC information:
SMCDStatus: InActive
SMCReason: 0000530F - Peer did not accept SMC-D request
SMCRStatus: Active SMCGroupId: 00000100
LocalSMCLinkId: 00000101 RemoteSMCLinkId: 00000301
LocalSMCRcvBuf: 64K RemoteSMCRcvBuf: 64K
Ancillary Input Queue: N/A
Application Data: EZBTNSRV TCPM1001 TSO10002 ET ST14S
----
Client Name: TCPCS1 Client Id: 0000000D
Local Socket: 9.67.115.5..23 Foreign Socket: 9.27.12.170..4999
BytesIn: 0000001062 BytesOut: 0000000480
SegmentsIn: 0000000019 SegmentsOut: 0000000019
StartDate: 01/09/2012 StartTime: 16:46:15
Last Touched: 16:46:15 State: Establsh
RcvNxt: 3296375906 SndNxt: 3296308452
ClientRcvNxt: 3296375906 ClientSndNxt: 3296308452
InitRcvSeqNum: 3296374843 InitSndSeqNum: 3296307971
CongestionWindow: 0000340353 SlowStartThreshold: 0000016384
IncomingWindowNum: 3296408638 OutgoingWindowNum: 3296341180
SndWl1: 3296375906 SndWl2: 3296308452
SndWnd: 0000032728 MaxSndWnd: 0000032768
SndUna: 3296308452 rtt_seq: 3296308412
MaximumSegmentSize: 0000065483 DSField: 00
Round-trip information:
Smooth trip time: 37.000 SmoothTripVariance: 101.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000
SockOpt: 00 TcpTimer: 00
TcpSig: 00 TcpSel: C0
TcpDet: F0 TcpPol: 00
TcpPrf: 40
QOSPolicy: Yes
QOSRuleName: QosRule1
TTLSPolicy: Yes
TTLSRule: TTLSRule1
TTLSGrpAction: TTLSGrpAction1
TTLSEnvAction: TTLSEnvAction1
TTLSConnAction: TTLSConnAction1 (Stale)
RoutingPolicy: Yes
RoutingTableName: prTabl
RoutingRuleName: SecLow2
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
ReceiveDataQueued: 000000002C
OldQDate: 09/15/06 OldQTime: 03:36:32
SendDataQueued: 000002C000
OldQDate: 09/15/06 OldQTime: 03:36:32
SendStalled: No
SMC information:
SMCDStatus: Active
LocalSMCLinkId: 00000101 RemoteSMCLinkId: 00000301
LocalSMCRcvBuf: 64K RemoteSMCRcvBuf: 64K
Ancillary Input Queue: N/A
Application Data: EZBTNSRV TCPM1001 TSO10002 ET ST14S
----
Client Name: APPV4 Client Id: 00000015
Local Socket: 0.0.0.0..2049 Foreign Socket: 9.42.103.99..1234
BytesIn: 0000000200 BytesOut: 0000000100
DgramIn: 0000000010 DgramOut: 0000000005
StartDate: 06/16/2011 StartTime: 22:53:55
Last Touched: 16:00:29
MaxSendLim: 0000065535 MaxRecvLim: 0000065535
SockOpt: 00 DSField: 00
QOSPolicy: Yes
QOSRuleName: QosRule2
RoutingPolicy: Yes
RoutingTableName: prTab4
RoutingRuleName: SecLow4
ReceiveDataQueued: 0000000000 ReceiveMsgCnt: 0000000000
----
Client Name: SYSLOGD1 Client Id: 00000010
Local Socket: 0.0.0.0..514 Foreign Socket: *..*
BytesIn: 0000000000 BytesOut: 0000000000
DgramIn: 0000000000 DgramOut: 0000000000
StartDate: 06/16/2011 StartTime: 23:33:52
Last Touched: 16:46:29
MaxSendLim: 0000065535 MaxRecvLim: 0000065535
SockOpt: 00 DSField: 00
QOSPolicy: No
RoutingPolicy: No
ReceiveDataQueued: 0000000000 ReceiveMsgCnt: 0000000000
----
IPv6 enabled or request for LONG format
NETSTAT ALL
MVS TCP/IP NETSTAT CS V2R2 TCPIP Name: TCPCS 22:06:44
Client Name: FTPD1 Client Id: 0000006D
Local Socket: ::1..21
Foreign Socket: ::1..1026
BytesIn: 00000000000000000035
BytesOut: 00000000000000000265
SegmentsIn: 00000000000000000015
SegmentsOut: 00000000000000000015
StartDate: 01/09/2012 StartTime: 22:04:11
Last Touched: 22:05:51 State: Establsh
RcvNxt: 0634886921 SndNxt: 0634950319
ClientRcvNxt: 0634885851 ClientSndNxt: 0634949426
InitRcvSeqNum: 0634885815 InitSndSeqNum: 0634949160
CongestionWindow: 0000299155 SlowStartThreshold: 0000065535
IncomingWindowNum: 0634919651 OutgoingWindowNum: 0634983003
SndWl1: 0634886921 SndWl2: 0634950319
SndWnd: 0000032684 MaxSndWnd: 0000032768
SndUna: 0634950319 rtt_seq: 0634950235
MaximumSegmentSize: 0000065463 DSField: 00
Round-trip information:
Smooth trip time: 81.000 SmoothTripVariance: 270.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000 RcvWnd: 0000032730
SockOpt: 8500 TcpTimer: 00
TcpSig: 85 TcpSel: 64
TcpDet: E0 TcpPol: 00
TcpPrf: C0 TcpPrf2: 70
TcpPrf3: 00
DelayAck: AutoYes
QOSPolicy: No
TTLSPolicy: Yes
TTLSRule: server
TTLSGrpAction: group_action1
TTLSEnvAction: Environment1
RoutingPolicy: No
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
ReceiveDataQueued: 0000000000
SendDataQueued: 0000000000
SendStalled: No
Ancillary Input Queue: Yes
BulkDataIntfName: OSAQDIO4
Application Data: EZAFTP0S C USER1 PTS305
----
Client Name: US16SVR Client Id: 0000000D
Local Socket: 0.0.0.0..10007 Foreign Socket: 0.0.0.0..0
BytesIn: 0000024000 BytesOut: 0000032000
SegmentsIn: 0000000900 SegmentsOut: 0000001000
StartDate: 03/20/2014 StartTime: 17:53:16
Last Touched: 17:53:16 State: Listen
RcvNxt: 0000000000 SndNxt: 0000000000
ClientRcvNxt: 0000000000 ClientSndNxt: 0000000000
InitRcvSeqNum: 0000000000 InitSndSeqNum: 0000000000
CongestionWindow: 0000000000 SlowStartThreshold: 0000000000
IncomingWindowNum: 0000000000 OutgoingWindowNum: 0000000000
SndWl1: 0000000000 SndWl2: 0000000000
SndWnd: 0000000000 MaxSndWnd: 0000000000
SndUna: 0000000000 rtt_seq: 0000000000
MaximumSegmentSize: 0000000536 DSField: 00
Round-trip information:
Smooth trip time: 0.000 SmoothTripVariance: 1500.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000 RcvWnd: 0000131072
SockOpt: 00 TcpTimer: 00
TcpSig: 00 TcpSel: 20
TcpDet: C0 TcpPol: 00
TcpPrf: 00
QOSPolicy: No
RoutingPolicy: No
ReceiveBufferSize: 0000065536 SendBufferSize: 0000065536
ConnectionsIn: 0000000010 ConnectionsDropped: 0000000000
MaximumBacklog: 0000000004 ConnectionFlood: No
CurrentBacklog: 0000000000
ServerBacklog: 0000000000 FRCABacklog: 0000000000
CurrentConnections: 0000000005 SEF: 100
Quiesced: No
SMC Information:
SMCDCurrConns: 0000000002 SMCDTotalConns: 0000000015
SMCRCurrConns: 0000000004 SMCRTotalConns: 0000000008
UseSMC: Yes Source: AutoSMC
AutoSMC%: 090
----
Client Name: FTPD1 Client Id: 0000005B
Local Socket: ::..21
Foreign Socket: ::..0
BytesIn: 00000000000000000000
BytesOut: 00000000000000000000
SegmentsIn: 00000000000000000000
SegmentsOut: 00000000000000000000
StartDate: 01/09/2012 StartTime: 22:05:11
Last Touched: 22:05:41 State: Listen
RcvNxt: 0000000000 SndNxt: 0000000000
ClientRcvNxt: 0000000000 ClientSndNxt: 0000000000
InitRcvSeqNum: 0000000000 InitSndSeqNum: 0000000000
CongestionWindow: 0000000000 SlowStartThreshold: 0000000000
IncomingWindowNum: 0000000000 OutgoingWindowNum: 0000000000
SndWl1: 0000000000 SndWl2: 0000000000
SndWnd: 0000000000 MaxSndWnd: 0000000000
SndUna: 0000000000 rtt_seq: 0000000000
MaximumSegmentSize: 0000000536 DSField: 00
Round-trip information:
Smooth trip time: 0.000 SmoothTripVariance: 1500.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000 RcvWnd: 0000032768
SockOpt: 8000 TcpTimer: 00
TcpSig: 01 TcpSel: 20
TcpDet: C0 TcpPol: 00
TcpPrf: 40
QOSPolicy: No
TTLSPolicy: No
RoutingPolicy: No
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
ConnectionsIn: 0000000001 ConnectionsDropped: 0000000000
MaximumBacklog: 0000000010 ConnectionFlood: No
CurrentBacklog: 0000000000
ServerBacklog: 0000000000 FRCABacklog: 0000000000
CurrentConnections: 0000000001 SEF: 100
Quiesced: No
SharePort: WLM
RawWeight: 63 NormalizedWeight: 15
Abnorm: 10 Health: 100
RawCP: 060 RawzAAP: 000 RawzIIP: 040
PropCP: 040 PropzAAP: 000 PropzIIP: 023
Application Data: EZAFTP0D
----
Client Name: TCPCS Client Id: 0000001E
Local Socket: 9.67.115.5..23
Foreign Socket: 9.27.11.182..4665
BytesIn: 00000000000000001062
BytesOut: 00000000000000000480
SegmentsIn: 00000000000000000019
SegmentsOut: 00000000000000000018
StartDate: 01/09/2012 StartTime: 14:27:37
Last Touched: 14:27:37 State: Establsh
RcvNxt: 2776729719 SndNxt: 2776682484
ClientRcvNxt: 2776729719 ClientSndNxt: 2776682484
InitRcvSeqNum: 2776728656 InitSndSeqNum: 2776682003
CongestionWindow: 0000340353 SlowStartThreshold: 0000016384
IncomingWindowNum: 2776762451 OutgoingWindowNum: 2776715212
SndWl1: 2776729719 SndWl2: 2776682484
SndWnd: 0000032728 MaxSndWnd: 0000032768
SndUna: 2776682484 rtt_seq: 2776682444
MaximumSegmentSize: 0000065483 DSField: 00
Round-trip information:
Smooth trip time: 100.000 SmoothTripVariance: 163.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000
SockOpt: 0000 TcpTimer: 00
TcpSig: 00 TcpSel: C0
TcpDet: F0 TcpPol: 00
TcpPrf: 40
QOSPolicy: Yes
QOSRuleName: QosRule1
TTLSPolicy: Yes
TTLSRule: TTLSRule1
TTLSGrpAction: TTLSGrpAction1
TTLSEnvAction: TTLSEnvAction1
TTLSConnAction: TTLSConnAction1 (Stale)
RoutingPolicy: Yes
RoutingTableName: prTabl
RoutingRuleName: SecLow2
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
ReceiveDataQueued: 0000000000
SendDataQueued: 0000000000
SendStalled: No
SMC information:
SMCDStatus: Active
LocalSMCLinkId: 00000101 RemoteSMCLinkId: 00000301
LocalSMCRcvBuf: 64K RemoteSMCRcvBuf: 64K
Ancillary Input Queue: N/A
Application Data: EZACICSO CSKL 0000038 CICSUSER CICP
Client Name: TCPCS Client Id: 0000001E
Local Socket: 9.67.115.5..23
Foreign Socket: 9.27.11.182..4665
BytesIn: 00000000000000001062
BytesOut: 00000000000000000480
SegmentsIn: 00000000000000000019
SegmentsOut: 00000000000000000018
StartDate: 01/09/2012 StartTime: 14:27:37
Last Touched: 14:27:37 State: Establsh
RcvNxt: 2776729719 SndNxt: 2776682484
ClientRcvNxt: 2776729719 ClientSndNxt: 2776682484
InitRcvSeqNum: 2776728656 InitSndSeqNum: 2776682003
CongestionWindow: 0000340353 SlowStartThreshold: 0000016384
IncomingWindowNum: 2776762451 OutgoingWindowNum: 2776715212
SndWl1: 2776729719 SndWl2: 2776682484
SndWnd: 0000032728 MaxSndWnd: 0000032768
SndUna: 2776682484 rtt_seq: 2776682444
MaximumSegmentSize: 0000065483 DSField: 00
Round-trip information:
Smooth trip time: 100.000 SmoothTripVariance: 163.000
ReXmt: 0000000000 ReXmtCount: 0000000000
DupACKs: 0000000000
SockOpt: 0000 TcpTimer: 00
TcpSig: 00 TcpSel: C0
TcpDet: F0 TcpPol: 00
TcpPrf: 40
QOSPolicy: Yes
QOSRuleName: QosRule1
TTLSPolicy: Yes
TTLSRule: TTLSRule1
TTLSGrpAction: TTLSGrpAction1
TTLSEnvAction: TTLSEnvAction1
TTLSConnAction: TTLSConnAction1 (Stale)
RoutingPolicy: Yes
RoutingTableName: prTabl
RoutingRuleName: SecLow2
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
ReceiveDataQueued: 0000000000
SendDataQueued: 0000000000
SendStalled: No
SMC information:
SMCDStatus: InActive
SMCReason: 0000530F - Peer did not accept SMC-D request
SMCRStatus: Active SMCGroupId: 00000100
LocalSMCLinkId: 00000101 RemoteSMCLinkId: 00000301
LocalSMCRcvBuf: 64K RemoteSMCRcvBuf: 64K
Ancillary Input Queue: N/A
Application Data: EZACICSO CSKL 0000038 CICSUSER CICP
----
Client Name: APPV4 Client Id: 00000015
Local Socket: 0.0.0.0..2049
Foreign Socket: 9.42.103.99..1234
BytesIn: 00000000000000000200
BytesOut: 00000000000000000100
DgramIn: 00000000000000000010
DgramOut: 00000000000000000005
StartDate: 06/17/2011 StartTime: 16:00:29
Last Touched: 16:00:29
MaxSendLim: 0000065535 MaxRecvLim: 0000065535
SockOpt: 00000000 DSField: 00
QOSPolicy: Yes
QOSRuleName: QosRule2
RoutingPolicy: Yes
RoutingTableName: prTab4
RoutingRuleName: SecLow4
ReceiveDataQueued: 0000345655 ReceiveMsgCnt: 0000045644
OldQDate: 09/15/06 OldQTime: 03:36:32
Multicast Specific:
TimeToLive: 0000000001 Loopback: Yes
OutgoingIpAddr: 199.1.2.3
Group IncomingIpAddr SrcFltMd
----- -------------- --------
224.8.8.8 193.1.1.94 Exclude
SrcAddr: 20.20.20.20
22.22.22.22
----
Client Name: APPV6 Client Id: 00000016
Local Socket: ::..2050
Foreign Socket: 12AB::1..1235
BytesIn: 00000000000000000200
BytesOut: 00000000000000000100
DgramIn: 00000000000000000010
DgramOut: 00000000000000000005
StartDate: 06/17/2011 StartTime: 16:00:29
Last Touched: 16:00:29
MaxSendLim: 0000065535 MaxRecvLim: 0000065535
SockOpt: 00000000 DSField: 00
QOSPolicy: No
RoutingPolicy: No
ReceiveDataQueued: 0000000000 ReceiveMsgCnt: 0000000000
Multicast Specific:
HopLimit: 0000000001 Loopback: Yes
OutgoingIntf:
Group: ff03::333
IncomingIntf: LINK6 SrcFltMd: Exclude
SrcAddr: 2e00::7
2e00::8
----
Client Name: SYSLOGD1 Client Id: 0000002C
Local Socket: 0.0.0.0..529
Foreign Socket: *..*
BytesIn: 00000000000000000000
BytesOut: 00000000000000000000
DgramIn: 00000000000000000000
DgramOut: 00000000000000000000
StartDate: 06/17/2011 StartTime: 14:27:42
Last Touched: 14:27:42
MaxSendLim: 0000065535 MaxRecvLim: 0000065535
SockOpt: 00000000 DSField: 00
QOSPolicy: No
RoutingPolicy: No
ReceiveDataQueued: 0000345655 ReceiveMsgCnt: 0000004564
OldQDate: 09/15/06 OldQTime: 03:36:32
ReceiveBufferSize: 0000016384 SendBufferSize: 0000016384
----
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.
- If there is a Service Policy Agent policy in effect for this entry,
one of the following values is used:
- 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 valueEZBMAIN
is displayed when the main routing table was used. - RoutingRuleName
- The name of the routing policy rule in use for this connection.
- 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.
- 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.
- 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.
- 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.
- SMCDCurrConns
- The number of currently established connections, which use SMC-D and have an SMCDStatus 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 SMCRStatus 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.
- SMCDStatus
- Indicates whether this connection is traversing a Shared Memory Communications - Direct
Memory Access (SMC-D) link. This field
can have the following values:
- Inactive
- Indicates that this connection does not use an SMC-D link.When the SMCDStatus 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.
- 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.
- 530F - Peer did not accept SMC-D request
- The remote connection peer is not configured to use SMC-D communications.
- 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.
- 581E - Peer subnet/prefix mismatch
- SMC-D communications cannot be used for this connection because the peer does not have an active interface in the same subnet that is eligible for SMC-D.
- 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 SMCDStatus value is Active, the following information is displayed and the SMCRStatus field is 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.
- SMCRStatus
- Indicates whether this connection is traversing a Shared Memory
Communications over Remote Direct Memory Access (SMC-R) link. This field
can have the following values:
- Inactive
- Indicates that this connection does not use an SMC-R link.When the SMCRStatus 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.
- 521E - Peer subnet/prefix mismatch
- SMC-R communications cannot be used for this connection because the peer does not have an active interface in the same subnet that is eligible for SMC-R.
- 5301 - Peer did not accept SMC-R request
- The remote connection peer is not configured to use SMC-R communications.
- 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.
- 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 SMCRStatus 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.
- 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:
- 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 LowSee the z/OS Communications Server: SNA Network Implementation Guide for additional information.
40 Medium
80 High
C0 Network - If neither of these is true, this value is 0.
- If there is a Service Policy Agent policy in effect for this entry,
one of the following values is used:
- 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 valueEZBMAIN
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
orExclude
. 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.