PH58313: CHANGE IN TRIGGER EXECUTION ORDER IS NOT DETECTED IN CM ANALYZE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When Compare in CMDELTA mode generates drop/create for trigger
  to maintain execution order and table for these triggers in not
  changed, CM Analyze will not detect trigger execution order
  change and report 'No changes' for triggers.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Administration Tool for z/OS    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When Change Management is used to       *
  *                      change trigger execution order, this    *
  *                      change cannot be detected if no change  *
  *                      exists for the table.                   *
  ****************************************************************
  Change to the trigger execution order requires a drop and create
  for triggers. But if the table is not included in the Compare
  scope by Change Management, this change is not detected and
  triggers are reported as objects with 'No changes'.
  

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:

  UI95811 UI95812

Modules/Macros

• ADBCVOC
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI95811

     UP24/02/29 P F402

• RD10 PSY UI95812

     UP24/02/29 P F402

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.