IBM Support

PH03785: USING SMC-D WITH TLS DSNL511I @ DSNLIENO TCP/IP CONVERSATION FAILED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using SMC with AT-TLS the connection comes up ok and data is
    sent
    over the SMC connection which quickly fails with DSNL511I @
    DSNLIENO TCP/IP CONVERSATION FAILED
    
    TO LOCATION ::xxxx:xx.xx.xx.xx
    IPADDR=::xxxx:xx.xx.xx.xx
    PORT=xxxxx
    SOCKET=SENDMSG RETURN CODE=140 REASON
    CODE=77F37242
    DSNL511I @ DSNLIENO TCP/IP CONVERSATION FAILED
    
    TO LOCATION
    IPADDR=::xxxx:xx.xx.xx.xx
    PORT=xxxx
    SOCKET=CONNECT RETURN CODE=1128 REASON
    CODE=76630291
    
    SMC-R SMCR SMC-D SMCD AT-TLS ATTLS
    ASYNC RECV COMMON BUFFERS
    SHARED MEMORY OBJECTS SMO
    

Local fix

  • turn off TLS for this connection.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server for z/OS Version  *
    * 2 Releases 2 and 3 IP: AT-TLS and SMC                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An async receive using common buffers can cause an AT-TLS    *
    * data decryption failure for an SMC connection.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the PTF                                                *
    ****************************************************************
    The async receive with common buffers caused a recursive call to
    the data decryption routine for the same data. This caused the
    data decryption to fail and the connection to be terminated.
    

Problem conclusion

  • The code was changed to update the data address before the
    recursive call so that the recursive call will decrypt new data.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH03785

  • Reported component name

    TCP/IP MVS

  • Reported component ID

    5655HAL00

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-09

  • Closed date

    2018-10-29

  • Last modified date

    2019-01-02

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

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

    UI59391 UI59393

Modules/Macros

  • EZBTLFWR EZBTCFWR EZBTCFRD EZBLCINB EZBT6FWR EZBTLSRH EZBTLFIO
    EZBT6LWR EZBSCINB EZBTCRD
    

Fix information

  • Fixed component name

    TCP/IP MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R220 PSY UI59391

       UP18/12/11 P F812

  • R230 PSY UI59393

       UP18/12/12 P F812

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

Document Information

Modified date:
02 January 2019