IBM Support

PI40931: LOOP IN MODULE EZBTTSND PREVENTS ANY FURTHER CONNECTIONS FROM BEING ACCEPTED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Timing issue while sending data to the terminal causes EZBTTSND
    to loop calling the Build_IOV routine.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server                   *
    * for z/OS Version 2 Release 2: Telnet                         *
    * Server                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Loop in EZBTTSND after a rare                                *
    * timing issue.                                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF                                                    *
    ****************************************************************
    The problem may be summarized as follows:
    1. There is a connection between the Telnet server
    and a client.
    2. Data is being sent and received.
    3. One process gets control to send data to the client.
    4. A second process updates the state of the client's
    connection.
    5. After the first process does the send, it enters a
    looping condition because of the changed state.
    

Problem conclusion

  • Telnet code is updated to not allow one process to
    loop because the other process updated the state.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI40931

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-12

  • Closed date

    2015-06-04

  • Last modified date

    2015-07-01

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

    PI39792

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

    UI28245

Modules/Macros

  • EZBTTSND
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R220 PSY UI28245

       UP15/07/01 P F506

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

Document Information

Modified date:
01 July 2015