IBM Support

PI71325: EZZ6003I TN3270E QUIESCED ON PORT NNN

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the Telnet Server reaches the maximum number of Sockets
    that it is allowed to open (MAXSOCKETS value), the server will
    issue message:
      EZZ6003I TN3270E QUIESCED ON PORT nnn
    At timed intervals, the server will attempt to create a new
    socket by issuing an ACCEPT. If the ACCEPT works, then the
    Telnet Server issues message:
      EZZ6003I TN3270E RESUMED ON PORT nnn
    At this point, normal operations are back in effect. However,
    if another type error occurred when the server issued an ACCEPT
    it may exit the retry loop in error preventing the server from
    reverting back to normal operations.
    

Local fix

  • Issue an OBEYFILE command to the Telnet Server. When the server
    processes the OBEYFILE command, it will rebuild it's entire
    internal structure including new ports for incoming connection
    requests.
    Additional Symptoms:
    SOMAXCONN MAXSOCKET
    EZZ6012I TN3270E BPX4AIO ACCEPT FAILED, RC = 0000007F
             RSN = 1102024D
    EZZ6003I TN3270E QUIESCED ON PORT nnnn
    .
    ReasonCode: 1102024 ErrnoJr: 589 JRMAXSOCKETS
    Explanation: The number of active sockets is equal to the value
      specified on the MAXSOCKETS parmlib statement.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server                   *
    * z/OS Version 2 Releases 1 and 2: IP Telnet facilities        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Telnet Port hangs when it stops issuing Accepts              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF                                                    *
    ****************************************************************
    The problem may be summarized as follows:
    1. The Telnet server is up and accepting connections
    2. A flood of connections comes in, resulting in a MAXSOCKETS
    error condition
    3. Telnet stops accepting connections on the port and does not
    resume when the MAXSOCKETS condition is alleviated.
    

Problem conclusion

  • EZBTTMST is updated to ensure that Telnet will resume accepting
    connections.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI71325

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-27

  • Closed date

    2016-11-04

  • Last modified date

    2017-05-15

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

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

    UI42316 UI42317

Modules/Macros

  • EZBTTMST
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R220 PSY UI42317

       UP16/12/02 P F612

  • R210 PSY UI42316

       UP16/12/02 P F612

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":"210","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":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 May 2017