PM26591: REVOKE IMPACT REPORT DOES NOT CORRECTLY IDENTIFY PACKAGES THAT WILL BE INVALIDATED WHEN BOUND IN A LOWER DB2 LEVEL - DB2 9 & 10

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2 Administration Tool for z/OS, when revoking an
  authorization with cascading revokes, Revoke Impact Report
  does not identify packages that will be invalidated if
  the package is bound in a previous release of DB2.
  Rebinding the package(s) in the new release of DB2 will show
  the package(s) in the Report.
  This APAR addresses the issue when running against DB2 9 and 10.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 z/OS who use the Revoke Impact function in   *
  *                 DB2 9 or above on packages in a catalog      *
  *                 that at some point has been migrated from    *
  *                 DB2 R710.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: The DB2 Administration Tool does not    *
  *                      find all the impacts for a REVOKE on a  *
  *                      package that has been migrated from     *
  *                      DB2 R710.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  DB2 R810 catalog migration did not remove trailing blanks from
  the columns that were converted from CHAR to VARCHAR.  The
  Revoke Impact function did not work correctly on these catalog
  rows.
  

Problem conclusion

• DB2 Administration Tool has been modified so that the Revoke
  Impact function reports the impacts on a DB2 R710 migrated
  catalog correctly. This APAR fixes the problem fixed in PM15989
  for users running on DB2 9 or above.  PM15989 fixed the problem
  for users running on DB2 R810.
  

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:

  UK73287 UK73288

Modules/Macros

•    ADBRIP9
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK73287

     UP11/10/29 P F110

• R720 PSY UK73288

     UP11/10/29 P F110

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.