PM83386: DB2 OBJECT COMPARISON TOOL FOR Z/OS PRODUCES CREATE STATEMENTS IN WSL OUT OF SEQUENCE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 Object Comparison Tool for z/OS produces
  CREATE Statements in WSL out of sequence
  .
  OC generates WSL to define all objects on target system. But the
  creates are not generated in correct sequence.
  VIew WPINV.VWIV142_AGG2 refers to   MQT WPINV.TWIV240_WPSEKNODE.
  But
  the CREATE for the MQT is located after the CREATE for the VIEW.
  Therefore WSL abends with SQLCODE204.
  .
  DSNT408I SQLCODE = -204, ERROR:  WPINV.TWIV240_WPSEKNODE IS AN
  UNDEFINED NAME
  DSNT418I SQLSTATE   = 42704 SQLSTATE RETURN
  CODE
  DSNT415I SQLERRP    = DSNXOTL SQL PROCEDURE DETECTING
  ERROR
  DSNT416I SQLERRD    = -500  0  0  -1  0  0 SQL DIAGNOSTIC
  INFORMATION
  

Local fix

Problem summary

•   USERS AFFECTED: Users of the DB2 Object Comparison Tool for
                    z/OS who compare objects that contain a
                    view that relies on a Materialized Query
                    Table (MQT  and the MQT also relies on
                    other views.
  
    PROBLEM DESCRIPTION: DB2 Object Comparison Tool for z/OS
                         produces CREATE Statements in the
                         Work Statement List (WSL  out of
                         sequence.
  
                         Object Compare generates WSL to define
                         all objects on the target system
                         however the CREATE statements are not
                         generated in the correct sequence.
  
                         VIew >VIEW_SCHEMA<.>VIEW_NAME<
                         refers to MQT >MQT_SCHEMA<.>MQT_NAME<.
  
                         As the CREATE statement for the MQT
                         is located after the CREATE statement
                         for the VIEW the WSL ends with a
                         SQLCODE204 / SQLCODEN204:
  
                         DSNT408I SQLCODE = -204,
                         ERROR:  >VIEW_SCHEMA<.>VIEW_NAME< IS
                         AN UNDEFINED NAME
                         DSNT418I SQLSTATE   = 42704
  
    RECOMMENDATION:
  
  Object Compare should generate the correct sequencefor a view
  that relies on an MQT, and the MQT also relies on other views.
  

Problem conclusion

• 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:

Modules/Macros

• ADB2CMP
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK95037

     UP13/06/19 P F306

• RA20 PSY UK95055

     UP13/06/19 P F306

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.