IBM Support

PK62876: PREPARATION FOR A FUTURE RELEASE OF DB2 WHERE DBRMS BOUND DIRECTLY WITHIN A PLAN MUST BE CONVERTED TO PACKAGES

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • Preparation for a future release of DB2 where DBRMs that were
    bound directly from a plan must first be converted to a
    package before use.                                      (DJ435)
    
    Optional Migration PREP work.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users who have Plans with DBRMs      *
    *                 directly bound.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Plans bound directly with DBRMs will    *
    *                      not be supported in future DB2 for z/OS *
    *                      releases.  Plans with DBRMs already     *
    *                      bound are recommended to be converted   *
    *                      into plans with package lists in the    *
    *                      current DB2 for z/OS release.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The support for plans with DBRMs directly bound will be removed
    in future DB2 for z/OS releases.
    
    In order to convert DBRMs bound within plans into packages,
    a new REBIND PLAN option COLLID('collection_id'|*) is introduced
    to do the DBRM TO PACKAGE conversion.  If a user rebinds a
    plan with this new option, DB2 will read from the SYSIBM.SYSDBRM
    table to get all the DBRM records bound with the plan, bind them
    into packages with the specified collection ID or use the
    default collection id (DSN_DEFAULT_COLLID_<planname>), and then
    bind the package list into the plans, and finally delete the
    records in the SYSIBM.SYSDBRM and SYSIBM.SYSSTMT tables.
    After rebinding with the COLLID option, there will not be any
    SYSDBRM or SYSSTMT records left associated with the plan, but
    SYSIBM.SYSPACKAGE and SYSIBM.SYSPACKSTMT will be populated
    with new records.
    
    Users can specify their own collid for converted packages, or
    the '*' to use the default: DSN_DEFAULT_COLLID_<planname>.
    If the plan does not have any DBRMs, this option will not be
    in effect.  If the plan was bound with both DBRMs and a package
    list, only the DBRMs will be converted into packages, and
    appended to the front of the existing package list.
    
    This COLLID option is provided to help users to convert plans
    with DBRMs into plans with a package list.  If it is not
    specified during REBIND PLAN, no conversion will take place.
    REBIND PLAN should continue to work the same way as in the
    current DB2 for z/OS release without this option; no DBRMs
    bound with the plan will be converted into packages.
    

Problem conclusion

Temporary fix

Comments

  • New REBIND PLAN option: COLLID(collection_id|*)
    REBIND PLAN (plan name | plan name,... | *)
           COLLID (collection_id|*) ...
    Note: COLLID can be specified with any other REBIND PLAN options
    options.  There is no default value for this option.  If COLLID
    is not specified, it will not be used, and the REBIND PLAN will
    work the same way as it does in the current release.
    
    Examples:
      REBIND PLAN(X) COLLID(*);
      Use default collection ID name: DSN_DEFAULT_COLLID_X (X is
      the plan name).  This command will allow a user to convert
      DBRMs bound with plan X into packages under collection ID:
      DSN_DEFAULT_COLLID_X.
    
      REBIND PLAN (X) COLLID (my_collection);
      Users can specify collection id as 'my_collection' for the
      new packages converted from DBRMs.  If there are both DBRMs
      and a PACKAGE LIST in plan X, newly converted package entires
      will be inserted into the front of the existing package list.
    
      REBIND PLAN (X1, X2, X3|*) COLLID (collection_id|*) is
      supported:
      Bind will traverse through each Plan specified, or all plans
      in SYSPLAN table if * is used, and do the conversion
      accordingly.
    
      REBIND PLAN (x) COLLID (collection_id|*) PKLIST(Z)
      If plan x has no package list but has DBRMs, then the DBRMS
      will be converted into pacakges and appended to the front of
      package list Z, then Z will be added to plan x.
      If plan x has both a package list and DBRMs, then the DBRMS
      will be converted into packages and appended to the front of
      package list Z, then the original package list will be
      replaced with Z.
      If plan x has only a package list, then package list Z will
      replace the existing one.
    
      REBIND PLAN (x) COLLID (collection_id|*) NOPKLIST.
      Three cases for this example:
      1. Plan x has both DBRMs and PKLIST--the existing package
         list will be deleted, while the new package list
         converted from the DBRMS will be bound into plan x.
      2. Plan x only has DBRMs--DBRMs will be converted into
         packages accordingly, and then added to the plan.
         NOPKLIST will be ignored.
      3. Plan x does not have DBRMs--the existing package list, if
         any, will be deleted.
    

APAR Information

  • APAR number

    PK62876

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function

  • Submitted date

    2008-03-17

  • Closed date

    2009-01-13

  • Last modified date

    2012-02-28

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

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

    UK43291

Modules/Macros

  •    DSNDBPL  DSNDSIB  DSNECPFC DSNECP00 DSNECP08
    DSNECP19 DSNECP40 DSNECP41 DSNECP42 DSNECP44 DSNECP45 DSNECP46
    DSNECP47 DSNECP50 DSNECP51 DSNECP54 DSNECP55 DSNFMDIR DSNFTDIR
    DSNFTDTA DSNTAUTH DSNTBAB  DSNTBAB2 DSNTBAP  DSNTBAPM DSNTBAP1
    DSNTBAP2 DSNTBAR  DSNTBAS  DSNTBAS2 DSNTBAS3 DSNTBBP  DSNTBBP2
    DSNTBCM  DSNTBCM1 DSNTBCM2 DSNTBCM3 DSNTBCM4 DSNTBCM5 DSNTBCM6
    DSNTBFR  DSNTBFR2 DSNTBMSG DSNTBRB  DSNTBRB2 DSNTBSPL DSNTBTRG
    DSNTCPAR DSNTCT   DSNTGEPL DSNTPARS DSNXEBPG HDB9910J
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R910 PSY UK43291

       UP09/02/05 P F902

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: 910

Reference #: PK62876

Modified date: 28 February 2012


Translate this page: