PK40340: SUPPORT DBRM VERSIONING

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• CURRENTLY DB2 packages are delivered with a fixed version name
  'O110_FINAL'. This makes it difficult to maintain datasharing
  systems with non-shared loadlibs. This requirement enables
  different package versions during ptf rollout onto these systems
  
  Additional Keywords
  bind binding version versioning
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   PE Server                                *
  *                 -   EXPLAIN                                  *
  *                 -   ICAT                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Previously, all DB2 packages in a       *
  *                      product version are shipped with the    *
  *                      same package version name, which        *
  *                      might prevent you from rolling out      *
  *                      PTFs successively in a data-sharing     *
  *                      environment.                            *
  ****************************************************************
  * RECOMMENDATION: APPLY THIS PTF.                              *
  ****************************************************************
  Previously, all packages contained the same version name
  O110_FINAL in product version 310 and O410_FINAL in
  product version 410.
  

Problem conclusion

Temporary fix

Comments

• APAR PK40340 introduces a new DB2 package versioning concept.
  In the future, packages that are shipped in a PTF will
  contain APAR-dependent version names. This allows you to run
  and rollout multiple package versions in a data-sharing
  environment, where OMEGAMON XE for DB2 PE runtime load
  libraries are not shared between LPARs.
  You should complete staged rollouts as quickly as possible
  to minimize version compatibility issues.
  
  For more details see the Technote titled "New package
  versioning".
  

APAR Information

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

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

  UK24461 UK24466

Modules/Macros

•    KD260SEX KD260SS3 KD261SEX KD261SS3
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK24461

     UP07/04/28 P F704

• R410 PSY UK24466

     UP07/04/28 P F704

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.