What is causing a Nonzero PACKETS IN ERROR?

Question & Answer

Question

When using a NETSTAT DEVLINKS command, the resultant report will show a nonzero value for Inbound Packets In Error or Outbound Packets In Error value. This is especially troubling if the number is a high percentage of the packets handled, or if it is increasing rapidly/regularly. How do I determine the cause of this?

The report looks similar to this:

    EZZ2350I MVS TCP/IP NETSTAT CS V2R2        TCPIP Name: TCPIP           19:09:52
     ...
    EZZ2778I IntfName: OSAGB1            IntfType: IPAQENET   IntfStatus: Ready
     ...
    EZZ3080I   Interface Statistics:
    EZZ3081I     BytesIn                           = 10046737
    EZZ3082I     Inbound Packets                   = 139140
    EZZ3083I     Inbound Packets In Error          = 2140    <----
    EZZ3084I     Inbound Packets Discarded         = 0
    EZZ3085I     Inbound Packets With No Protocol  = 0
    EZZ3086I     BytesOut                          = 2289270789
    EZZ3087I     Outbound Packets                  = 16252214
    EZZ3088I     Outbound Packets In Error         = 0
    EZZ3089I     Outbound Packets Discarded        = 0

Answer

There are many possible reasons for packets to be discarded by TCPIP. To identify the sources and reasons for these discards, collect a Packet Trace as described in TechNote 1292013. On the PKTTRACE command, specify DISCARD=ALL to record only the affected packets. The resultant data set can be formatted using the IPCS CTRACE facility, specify Report Type SHORT, SUMMARY, or FULL.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

ZOSCS COMMSERVER

Was this topic helpful?

Document Information

Modified date:
13 June 2018

UID

dwa1453263

Tips