PH64989: INTERNAL JANUARY 2025 BUG FIXES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Internal APAR for January 2025 Bug Fixes
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Administration Tool for z/OS    *
  *                 and Db2 Object Comparison Tool for z/OS      *
  *                 PROBLEM DESCRIPTION (39 characters maximum   *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR provides fixes to resolve     *
  *                      the issues described in the problem     *
  *                      summary.                                *
  ****************************************************************
  This APAR fixes the following issues:
  1. When the RTS line command is used in a DDF catalog on an
  index on panel ADB21X, no rows are returned. However, rows do
  exist, as shown by issuing the RTS line command in the system
  where the DDF catalog resides.
  
  2. On panel ADB21K, when line command LP is used on a package
  that is bound with the EXPLAIN(ONLY) option, rows for the
  EXPLAIN(ONLY) BIND PACKAGE command are not displayed. The LP
  line command description does not indicate that only the
  PLAN_TABLE rows for the EXPLAIN(YES) BIND command will be shown.
  To display rows for EXPLAIN(ONLY) BIND PACKAGE, use line command
  LPA.
  
  3. When using the DS line command on panel ADB21D, the archive
  table that resides in the database is not listed in the
  database structure output.  Accelerator-only tables are not
  included in the database structure output either.
  
  4. Object Compare incorrectly reports that a primary index
  does not exist on the target when the index is explicitly
  created on a table in an implicitly created table space. The
  subsequent apply job fails with SQLCODE=-601 on the CREATE
  INDEX statement.
  
  5. When using line command AL on panel ADB21C, if the DEFAULT
  field value in the catalog table for this column is 'U' or
  'S', the 'Invalid value' panel error is displayed with the
  cursor positioned on the field "WITH DEFAULT".
  
  6. When CM analyzes the change for altered views, it
  incorrectly includes the SYSTSTAB catalog table in the object
  comparison.
  
  7. The DDL reader incorrectly processes BX'<value>' values,
  which results in incorrect Object Compare results for BINARY
  WITH DEFAULT columns.
  
  8. When using option 1 on panel ADB2Z2H, if the user specifies
  "I" for the option "Includes obj type", entries with only "T"
  table type rows are incorrectly shown.
  
  
  9. When running Object Compare for a table with schema and table
  names with a length of 128 characters, ADBGAJOB fails with
  RC=30: "FUNCTION = ADBGAJOB, LINE nnnn: If
  tb2db.basetbo.basetbn <> 0 Then"
  

Problem conclusion

• The problems have 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:

  UI99936

Modules/Macros

• ADB21DS  ADB21K   ADB21TAB ADB2314I ADB2314X ADB26CN  ADB2AN
  ADB2CM3  ADB2CMT  ADB2CMU  ADB2REM  ADB2Z2H  ADBCDTS  ADBCVOC
  ADBGAJOB
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RD10 PSY UI99936

     UP25/02/12 P F502

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.