IBM Support

PM40872: PREPARATION FOR APAR PM42237

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • DB2DDF defect pm40872 dpm40872
    Preparation for APAR PM42237.
    .
     FIXCAT KEYWORDS:
     DB2MIGV10/K  DB2COEXIST/K
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users    *
    *                 using IBM Data Server Driver for JDBC and    *
    *                 SQLJ Type 4 Connectivity to access a DB2 for *
    *                 z/OS data sharing group.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Preparation for APAR PM42237.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR operates in conjunction with APAR PM42237 to control
    how PM42237 behaves relative to a member of a data sharing
    group. See APAR PM42237 for more information.
    

Problem conclusion

  • The changes made by this APAR, PM40872, work in conjunction
    with the changes made in APAR PM42237. When properly applied,
    the two APARs will ensure that a DB2 10 for z/OS member
    behaves correctly when accessed by IBM Data Server Driver for
    JDBC and SQLJ Type 4 Connectivity clients in a coexistence
    environment.
    Please see APAR PM42237 for more information.
    APAR PM42237 corrects an incorrect output condition related to
    stored procedures that are invoked in DB2 10 for z/OS data
    sharing coexistence environments. The incorrect output
    condition only occurs with respect to remote IBM Data Server
    Driver for JDBC and SQLJ Type 4 Connectivity application
    environments. To correct the incorrect output condition, the
    changes in the two APARs, PM40872 and PM42237, should be
    applied according to the recommendations described by PM42237.
    It is important to understand the details described by PM42237
    before applying the PM40872 change to any DB2 10 for z/OS
    member of a data sharing group.
    This APAR, PM40872, also provides PM42237 preparation changes
    for DB2 V9 and V8 members of the group. However, the change for
    APAR PM40872 can be applied to V9 and V8 members without any
    consideration for APAR PM42237.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM40872

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-06

  • Closed date

    2011-07-20

  • Last modified date

    2011-09-01

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

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

    UK69944 UK69945 UK69946

Modules/Macros

  •    DSNDBMEM DSNDLCOM DSNLZD00 DSNRNTFY DSNRRGRI
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK69944

       UP11/08/04 P F108

  • R810 PSY UK69945

       UP11/08/04 P F108

  • R910 PSY UK69946

       UP11/08/04 P F108

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.



Document information

More support for: DB2 for z/OS

Software version: A10

Reference #: PM40872

Modified date: 01 September 2011


Translate this page: