IBM Support

PI16194: ABEND04E RC00E30072 AT DSNTLQRY WHEN ZPARM PKGREL_COMMIT IS ON

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND04E RC00E30072 AT DSNTLQRY occurred when the zparm
    PKGREL_COMMIT is on.
    

Local fix

  • Turn off zparm PKGREL_COMMIT
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 11 for z/OS users of packages bound  *
    *                 on DB2 9 with bind option                    *
    *                 RELEASE(INHERITFROMPLAN)                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND04E RC00E30072 at DSNTLQRY +0B02   *
    *                      occurred on DB2 11 when both of         *
    *                      the following were true:                *
    *                      - running package that was bound on     *
    *                        DB2 9 with bind option                *
    *                        RELEASE(INHERITFROMPLAN), and         *
    *                        its associated DB2 plan was bound     *
    *                        RELEASE(COMMIT)                       *
    *                      - DB2 11 subsystem parameter / zparm    *
    *                        PKGREL_COMMIT = YES                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For a package bound with option RELEASE(INHERITFROMPLAN), when
    the package is run the RELEASE option behavior used by DB2 for
    the package is actually 'inherited' from the RELEASE behavior of
    the active DB2 plan that is associated with the package.
    The RELEASE bind option controls 'when' DB2 should release
    resources and locks that a program/package uses, either at each
    COMMIT point or when the DB2 thread/plan running the package
    terminates.
    .
    The reported DSNTLQRY ABEND04E occurred during a COMMIT or
    ROLLBACK on DB2 11 when the DB2 subsystem parameter/zparm
    PKGREL_COMMIT=YES (this is the DB2 default value) and the user
    was running a package that was bound on DB2 9 with option
    RELEASE(INHERITFROMPLAN) and its associated DB2 plan was
    bound RELEASE(COMMIT).
    The zparm PKGREL_COMMIT is DB2 11 new function enabled only for
    running packages that use RELEASE(DEALLOCATE) behavior.
    .
    The abend occurred because DB2 did not correctly 'inherit'
    the associated DB2 plan's RELEASE(COMMIT) value and apply it to
    the DB2 9 package when running it. This resulted in DB2
    using RELEASE(DEALLOCATE) behavior for the package at the COMMIT
    or ROLLBACK point which includes PKGREL_COMMIT behavior, which
    was not correct for this package so this DSNTLQRY ABEND04E then
    occurred. DB2 should have instead applied RELEASE(COMMIT)
    behavior 'inherited' from the associated DB2 plan.
    .
    To avoid the reported DSNTLQRY abend for this specific case
    of INHERITFROMPLAN and PKGREL_COMMIT=YES, you can do one of
    the following:
      - Reset zparm PKGREL_COMMIT=NO (PKGREL_COMMIT is an online
        changeable zparm without need to restart the DB2
        subsystem), or
      - REBIND the package on DB2 11
    .
    This problem with INHERITFROMPLAN does not occur for packages
    bound on DB2 10 or 11 later with RELEASE(INHERITFROMPLAN).
    .
    Note that other symptoms or errors are possible for this
    DB2 11 INHERITFROMPLAN problem with DB2 9 packages, even
    with PKGREL_COMMIT=NO.  For those cases, you need only REBIND
    the package on DB2 11 to avoid the problem.
    

Problem conclusion

  • DB2 code for RELEASE(INHERITFROMPLAN) was modified to correctly
    'inherit' the associated DB2 plan's RELEASE(COMMIT) value and
    apply it to the DB2 9 package when running it.
    
    Additional search keywords: OFFSET0B02 AB04E 00E30072
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI16194

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-16

  • Closed date

    2014-05-20

  • Last modified date

    2014-07-01

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

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

    UI18129

Modules/Macros

  • DSNXEAAL DSNXELS1
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI18129

       UP14/06/04 P F406 ½

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

Document Information

Modified date:
01 July 2014