IBM Support

PM67130: DSNL511I SOCKET=SENDMSG RETURN CODE=3448 REASON CODE=00000000 12/08/01 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DB2TCPIP defect pm67130 dpm67130
    A CAF application may experience DSNL511I SOCKET=SENDMSG
    RETURN CODE=3448 REASON CODE=00000000 when then do an
    implicit disconnect.
    **********************************************************
    Additional Symptoms and Keywords:
     DSNL511I MSGDSNL511I SOCKET SENDMSG RECV
      RETURN CODE 3448 REASON CODE 00000000 or
      RETURN CODE  140 REASON CODE 76697242
     Call Attach Facility CAF explicit DISCONNECT not driven
    

Local fix

  • local fix/work around: to avoid the DSNL511I message,
    application should issue a CAF DISCONNECT which results in
    an explicit disconnect
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: After APAR PM54383, message DSNL511I    *
    *                      with RETURN CODE 3448 or 140 may occur  *
    *                      when an application ends normally.      *
    *                      Message DSNL425I or DSNL406I may also   *
    *                      be observed.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A user has a Call Attach Facility (CAF) application that uses
    the CAF CONNECT API to access a DB2 subsystem. The application
    then executes SQL that accesses a remote system (via DDF). When
    the application completes, it fails to execute an explicit CAF
    DISCONNECT API but instead leaves this to be performed
    implicitly by DB2.
    Similarly, implicit disconnection behavior may also be expected
    from applications using other attachments, such as RRS or TSO.
    If the DB2 (DDF) communications Data Base (CDB) is configured
    to access the remote system via TCP/IP network protocols,
    message DSNL511I with RETURN CODE 3448 or 140 may occur during
    implicit disconnection processing after APAR PM54383. This
    message occurs at the DB2 for z/OS requester system on behalf
    of the application allied thread. This may further lead to the
    following:
    o If a commit of the SQL work was also being implied as part of
      the implicit disconnection, depending on the attachment being
      used, the commit may fail and the SQL activity will be
      aborted. In this case, message DSNL425I may also be issued.
      This condition is known to occur only for CAF application
      environments.
    o If the application explicitly commits its work prior to the
      implicit disconnection, the commit will succeed but a
      DSNL406I message may also be issued.
    The problem occurs because APAR PM54383 made a change to DB2
    allied thread Abnormal Termination processing that incorrectly
    impacted applications that complete normally.
    In most cases, the problem can be avoided by changing the
    application to obey good programming practice behavior by
    explicitly invoking disconnection APIs, such as CAF DISCONNECT.
    
    Additional Keywords:
    IDAAV2R1/K IDAAV3R1/K
    

Problem conclusion

  • DB2 has been changed to distinguish allied thread abnormal
    termination processing from the normal termination of an
    application that implicitly disconnects from a DB2 subsystem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM67130

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-19

  • Closed date

    2012-07-17

  • Last modified date

    2012-10-19

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

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

    UK80357 UK80358

Modules/Macros

  • DSNVDISC
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK80357

       UP12/08/01 P F207

  • R910 PSY UK80358

       UP12/08/01 P F207

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
19 October 2012