IBM Support

PI89626: 04E-00D3000A DSNLCMT1+00314, AFTER MESSAGE DSNL032I 00D35922 DSNLZSPA0032, FOLLOWED BY DB2 TERMINATION 00E50702

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DB2TCPIP DB2DRDA DB2TERM RTC 67001 d67001
    Abend 04E-00D3000A DSNLCMT1+00314 after message DSNL032I
    Reason 00D35922 Error ID DSNLZSPA0032. This will be followed by
    a DB2 termination with message DSNV086E Reason 00E50702.
    The problem only occurs with respect to DB2 12 for z/OS as a
    server WRT a remote client application environment, and only if
    the remote client application environment is incorrectly
    configured to access the DB2 12 for z/OS server Resync Port
    instead of its SQL port.
    Further, the problem only occurs relative to remote IBM Data
    Server Client/Driver, such as JCC or CLI, requester
    environments and only if they're V11 FP1 or higher.
    ***************************************************************
    Additional Symptoms and Keywords:
     DSNL032I MSGDSNL032I 00D35922 RC00D35922 DSNLZSPA0032
     ABEND04E AB04E S004E 04E
      04E-00D3000A 00D3000A RC00D3000A
       DSNLCMT1 DSNLCMT1+00314 00314 314 OFFSET00314 OFFSET314
        ABNDID0001 ABID0001 VRADC0001
     DSNV086E MSGDSNV086E 00E50702 RC00E50702
    

Local fix

  • Correct remote client configuration to refer to the DB2 SQL
    port (instead of its Resync Port).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Distributed Data Facility (DDF) users.                   *
    * DB2 12 for z/OS users only.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Abend 04E-00D3000A DSNLCMT1+00314                            *
    * after messsage DSNL032I with Reason                          *
    * 00D35922 and Error ID DSNLZSPA0032.                          *
    * The abend leads to a DB2 subsystem                           *
    * termination with reason 00E50702.                            *
    * The problems only occurred due to a                          *
    * mis-configured remote client that                            *
    * incorrectly tries to access the DB2                          *
    * server (for SQL) via its resync port                         *
    * instead of its SQL port.                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    A remote client environment is incorrectly configured to access
    a DB2 12 for z/OS server via its resync port, instead of its
    SQL port.  Message DSNL032I 00D35922 DSNLZSPA0032 is correctly
    issued to the system console to acknowledge the remote client
    configuration error.
    However, in the process of terminating the client's connection
    and associated DB2 thread, an abend 04E-00D3000A DSNLCMT1+00314
    incorrectly occurs during commit processing.  The nature of the
    abend during commit processing leads to a subsystem termination
    which is indicated by message DSNV086E with reason 00E50705.
    This problem occurs in DB2 12 for z/OS only.
    The problem can be avoided by correcting the remote client
    environment to properly access the DB2 server via its SQL port.
    

Problem conclusion

  • DB2 12 for z/OS has been changed such that an incorrect access
    to the resync port will not receive an abend during commit
    processing.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI89626

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-31

  • Closed date

    2017-11-27

  • Last modified date

    2018-01-03

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

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

    UI52143

Modules/Macros

  • DSNLZREX DSNLTEXC DSNLAGNT DSNLTRAG
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI52143

       UP17/12/12 P F712 ¢

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

Document Information

Modified date:
03 January 2018