PI87675: DURING RE-MIGRATION, NONDATASHARING OR ABIND=YES CASES SHOULD NOT AUTOBIND A PACKAGE/PLAN THAT WAS BOUND AT A LOWER LEVEL

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• During re-migration, nondatasharing or ABIND=YES cases should
  not autobind a package/plan that was bound at a lower level.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 11 and 12 for z/OS users.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In a data sharing environment with                           *
  * Db2 10 and 11 coexistence, running a                         *
  * package/plan on Db2 10 triggers an                           *
  * automatic bind of the package/plan if                        *
  * the package/plan was last bound in                           *
  * Db2 11.  After this automatic bind,                          *
  * running the package/plan on Db2 11                           *
  * triggers another automatic bind when                         *
  * the subsystem parameter ABIND=YES.                           *
  * This automatic bind on Db2 11 is not                         *
  * necessary. Db2 11 and 12 coexistence                         *
  * data sharing system has the same                             *
  * problem.                                                     *
  *                                                              *
  * In a migration case, a Db2 10 system                         *
  * migrates to Db2 11 system. For some                          *
  * reason, the Db2 system falls back to                         *
  * Db2 10. Running a package/plan on Db2                        *
  * 10 triggers an automatic bind of the                         *
  * package/plan if the package/plan was                         *
  * last bound in Db2 11. After the                              *
  * system remigrates to Db2 11, running                         *
  * the package/plan on Db2 11 triggers                          *
  * another automatic bind                                       *
  * (remigration autobind) if the                                *
  * subsystem parameter ABIND=YES.                               *
  * This remigration autobind is not                             *
  * necessary. Migration from Db2 11 to                          *
  * Db2 12 has the same problem.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  The automatic bind in the higher release of Db2 in the above
  two cases is not necessary. The higher release Db2 can run
  the package/plan bound in the lower release. If new functions
  in the higher release is desired, users can rebind the
  package/plan to gain the new functions.
  
  Additional Keywords:
  DB2MIGV11/K DB2MIGV12/K DB2COEXIST/K
  

Problem conclusion

Temporary fix

Comments

• Db2 code has been changed so that when subsystem parameter
  ABIND=YES,
  (1) running a package/plan in the higher release of Db2 in a
      data sharing coexistence system does not trigger an
      automatic bind if the package/plan was last automatically
      bound on the lower release of Db2; and
  (2) the remigration autobind does not happen when the
      package/plan was last automatically bound in the fallback
      release of Db2.
  With this APAR, ABIND=YES and ABIND=COEXIST have the same
  behavior.
  

APAR Information

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

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

  UI52931 UI52932

Modules/Macros

• DSNXEAAL DSNTBAB2 DSNTAAL  DSNTBAB
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI52931

     UP18/01/12 P F801

• RB10 PSY UI52932

     UP18/01/12 P F801

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.