PH42301: ADD NEW OPTION UNIQUE-VERSION TO BIND AVOIDANCE PROGRAM ADBBMA3

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Currently, if a package's CONTOKEN has changed, but both the Db2
  catalog and the DBRM have the same package version, bind
  avoidance program ADBBMA3 issues message BND2919I:
  
  BND2919I SYSPACKAGE ENTRY=>PACKAGE_NAME<  WITH VERSION
  >VERSION< HAD CONTOKEN >CONTOKEN< AAD DOES NOT MATCH NEW
  DBRM.
  
  The BIND command for the package in question is still placed in
  the BINDOUT DD, and the job does not end with RC 8.
  
  However, some users may prefer not to bind the package in this
  scenario. With this APAR change, when the new UNIQUE-VERSION
  option is specified in the calling parameter of the ADBBMA3
  module, the new message BND2920E alerts users that the
  message BND2919I condition has occurred.  ADBBMA3 does not
  include a BIND command for this package in BINDOUT DD, and
  continues scanning all bind commands before it ends with RC 8.
  
  
  Keywords: ADBBMA3; MSGBND2919I; BIND AVOIDANCE
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Administration Tool for z/OS    *
  *                 who use the bind avoidance program ADBBMA3   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Currently, if a package's CONTOKEN has  *
  *                      changed, but both the Db2 catalog and   *
  *                      the DBRM have the same package version, *
  *                      the bind avoidance program ADBBMA3      *
  *                      always generates the BIND command.      *
  *                      You do not have the option to avoid     *
  *                      generating a BIND command in this       *
  *                      scenario.                               *
  ****************************************************************
  Currently, if a package's CONTOKEN has changed, but both the
  Db2 catalog and the DBRM have the same package version, the bind
  avoidance program ADBBMA3 issues message BND2919I:
  
  BND2919I SYSPACKAGE ENTRY=>PACKAGE_NAME< WITH VERSION >VERSION<
  HAD CONTOKEN >CONTOKEN< AAD DOES NOT MATCH NEW DBRM.
  
  The BIND command for the package in question is still placed in
  the BINDOUT DD, and the job does not end with RC 8.
  
  However, some users might prefer not to bind the package in
  this scenario. With this APAR change, when the new
  UNIQUE-VERSION option is specified in the calling parameter of
  the ADBBMA3 module, the new message BND2920E alerts users that
  the condition in message BND2919I has occurred. ADBBMA3 does not
  include a BIND command for this package in the BINDOUT DD and
  continues scanning all bind commands before it ends with RC 8.
  
  Keywords: ADBBMA3 MSGBND2919I MSGBND2920E BIND AVOIDANCE
  

Problem conclusion

• The problem has been resolved.
  

Temporary fix

Comments

APAR Information

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

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

  UI79888

Modules/Macros

• ADBBMA3
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI79888

     UP22/03/26 P F203

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.