PM78647: TRIGGER SEQUENCING MASKING, TRIGGER OUT OF SEQUENCE, MISSING DEPENDENT PROCEDURE, MISSING DEPENDENT FUNCTION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Trigger sequencing masking, trigger out of sequence,
  missing dependent procedure, missing dependent function
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison           *
  *                 Tool for z/OS who compare DB2                *
  *                 Stored Procedures (NSP),                     *
  *                 User Defined Functions (UDF) and Triggers.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: The following problems exist:           *
  *                                                              *
  *                      1-Dependent User Defined Function       *
  *                      (UDF) is dropped but not recreated      *
  *                      when parent User Defined Function       *
  *                      is dropped and recreated.               *
  *                                                              *
  *                      2- Dependent Stored Procedure(NSP)      *
  *                       is dropped but not recreated when      *
  *                      parent Stored Procedure(NSP) is         *
  *                      dropped and recreated.                  *
  *                                                              *
  *                      3- Existing Trigger is dropped and      *
  *                      recreated but new Trigger is added      *
  *                      before existing Trigger is recreated    *
  *                      causing a Trigger sequence problem.     *
  *                                                              *
  *                      4- A Trigger is dropped/recreated to    *
  *                      maintain the sequence.  The Trigger     *
  *                      was recreated using the source schema   *
  *                      instead of the target schema causing    *
  *                      SQLCODEN601 / SQLCODE=-601:             *
  *                                                              *
  *                      DSNT408I SQLCODE = -601, ERROR:         *
  *                      THE NAME (VERSION OR VOLUME             *
  *                      SERIAL NUMBER) OF THE OBJECT            *
  *                      TO BE DEFINED OR THE TARGET OF          *
  *                      A RENAME STATEMENT IS IDENTICAL         *
  *                      TO THE EXISTING NAME (VERSION OR        *
  *                      VOLUME SERIAL NUMBER)                   *
  *                      >schema<.>name< OF THE OBJECT           *
  *                      TYPE TRIGGER                            *
  *                                                              *
  *                      For the DB2 Object Comparison Tool      *
  *                      for z/OS 10.2 only, if panel GOC5RO     *
  *                      "Specify Compare Reporting Options",    *
  *                      "Only changed objects"= YES is          *
  *                      specified and a procedure has a         *
  *                      change that results in a drop/create,   *
  *                      the change will not be reported in      *
  *                      the "OBJECT COMPARISON REPORT" section  *
  *                      It will, however, still be reported     *
  *                      in the "COMPARISON SUMMARY REPORT"      *
  *                      section, and the change                 *
  *                      will be implemented.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The following problems exist.
  
  1- Dependent User Defined Function(UDF) is dropped but not
  recreated when parent User Defined Function(UDF) is dropped
  and recreated.
  
  2- Dependent Stored Procedure(NSP) is dropped but not
  recreated when parent Stored Procedure(NSP) is dropped and
  recreated.
  
  3- Existing Trigger is dropped and recreated but new
  Trigger is added before existing Trigger is recreated
  causing a Trigger sequence problem.
  
  4- A Trigger is dropped/recreated to maintain sequence.
  The Trigger was recreated using the source schema
  instead of the target schema causing SQLCODEN601/
  SQLCODE=-601:
  
  DSNT408I SQLCODE = -601, ERROR:  THE NAME
  (VERSION OR VOLUME SERIAL NUMBER) OF THE
  OBJECT TO BE DEFINED OR THE TARGET OF
  A RENAME STATEMENT IS IDENTICAL TO THE
  EXISTING NAME (VERSION OR VOLUME SERIAL
  NUMBER) >schema<.>name< OF THE OBJECT
  TYPE TRIGGER
  
  For the DB2 Object Comparison Tool for
  z/OS 10.2 only, if panel GOC5RO
  "Specify Compare Reporting Options",
  "Only changed objects"= YES is
  specified and a procedure has a change
  that results in a drop/create, the
  change will not be reported in the
  "OBJECT COMPARISON REPORT" section.
  It will, however, still be reported
  in the "COMPARISON SUMMARY REPORT"
  section, and the change
  will be implemented.
  

Problem conclusion

• Problem has been resolved.
  APAR PM81415 will address the omission
  from the "OBJECT COMPARISON REPORT" issue.
  

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:

  UK91201 UK91202

Modules/Macros

•    ADB2CMF  ADB2CMR  ADB2CMS
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK91201

     UP13/01/29 P F301

• RA20 PSY UK91202

     UP13/01/29 P F301

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.