IBM Support

PM57930: TCPCONN QUERY NETVIEW DISPLAY SHOWS INVALID ACTIVE CONNECTIONS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Connections with a duration equivalent to the MINLIFETIME timer
    are still being reported to Netview's TCPCONN QUERY display
    while in the act of transitioning to the FIN_WAIT_1/CLOSE_WAIT
    state.
    
    
    Additional symptoms:
    
    Connection Duration = MINLIFETIME timer value
    TCPCONN QUERY displays connection as active
    TCPCONN QUERYACT does not display connection
    SMFTYPE119: TCPINIT: NO   TCPTERM:  NO
    
    
    Keywords:
    
    FIN_WAIT_2, CLOSE_WAIT, LAST_ACK
    

Local fix

  • Use TCPCONN QUERYACT display (Recommended Netview Display)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release(s) 12 and 13 IP:  *
    *                 NETMONITOR TCPCONNSERVICE                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: NETMONITOR TCPCONNSERVICE may fail to   *
    *                      report connection termination.  NetView *
    *                      TCPCONN QUERY display shows connections *
    *                      that have terminated.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    NETMONITOR TCPCONNSERVICE may fail to report connection
    termination.  Netview TCPCONN QUERY display shows connections
    that have terminated.
    
    The Network Monitor Interface (NMI) provides the ability to
    receive notifications when connections initiate and terminate.
    A timing condition exists where the connection termination
    notification is not being presented to the NMI.  In order for
    this condition to exist the TCP/IP profile must have
    SMFCONFIG TYPE119 NOTCPTERM coded or defaulted and
    NETMONITOR TCPCONNService MINLIFETime n.  The timing condition
    occurs when the TCP connection is closed by the remote, then
    closed by the local side and the MINLIFETIME timer expires
    while the connection is in the LASTACK state.
    
    The transition to the LASTACK state skips sending the
    termination notification to the NMI if the MINLIFETIME timer
    has not expired and sent the initiation notification.  The
    LASTACK state sets tcb_smfterm_issue whether the termination
    notification was sent or not.  The MINLIFETIME timer expiration
    while the connection is in LASTACK will send the connection
    initiation notification.  The connection will transition to the
    KLOSED state when the final ACK arrives but the termination
    notification will not be sent because tcb_smfterm_issued is set.
    +-------------------------------------------------------------+
    + Please check our Communications Server for OS/390 homepages +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

  • TCSNDINT has been amended to skip setting tcb_smfterm_issued
    when a connection transitions to LASTACK and the MINLIFETIME
    timer has not reported the connection initiation to the NMI.
    
    * Cross Reference between External and Internal Names
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM57930

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1C0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-10

  • Closed date

    2012-03-07

  • Last modified date

    2012-05-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK76891 UK76892

Modules/Macros

  • EZBTCFWR EZBTCSND EZBTLFWR EZBT6FWR EZBT6LWR
    EZBT6SND TCSNDINT T6SNDINT
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1C0 PSY UK76891

       UP12/04/07 P F204

  • R1D0 PSY UK76892

       UP12/04/07 P F204

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1C0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1C0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 May 2012