PH34842: DB2 OBJECT COMPARE: BASIC TRIGGERS WITH SYSTEM_TIME SENSITIVE, BUSINESS_TIME SENSITIVE, ARCHIVE SENSITIVE SET TO NO

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Db2 Object Compare: Basic triggers with SYSTEM_TIME
  SENSITIVE, BUSINESS_TIME SENSITIVE, ARCHIVE SENSITIVE set to NO
  
  When a basic trigger is created in DB2 z/OS V12, the three
  parameters, SYSTEM_TIME SENSITIVE, BUSINESS_TIME SENSITIVE, and
  ARCHIVE SENSITIVE are set to YES for the trigger package.  The
  is no option to set them to NO with the CREATE TRIGGER (basic)
  
  During a compare messages like this may be seen:
  
  Compare Trigger source(A.TRIGGER1)
  and target(A.TRIGGER1)
    Source type : Basic  Target type : Basic
      (A)Field SYSTEM_TIME SENSITIVE changed from YES to NO
      (A)Field BUSINESS_TIME SENSITIVE changed from YES to NO
      (A)Field ARCHIVE SENSITIVE changed from YES to NO
    Trigger will be altered
  
  However, the trigger still ends up with them set to YES.
  

Local fix

• A REBIND TRIGGER PACKAGE can be used to set the parameters to
  no.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Object Comparison Tool for      *
  *                 z/OS.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Informational message ADB7389I          *
  *                      is changed to a warning message.        *
  ****************************************************************
  Compare currently uses ADB7389I as an
  informational message. This message will
  be updated to a warning message and will
  then be seen in the tool and documentation
  as ADB7389W.
  
  For example, this message
  
  Compare Trigger source <trigger name> and target <trigger name>
    Source type : Basic  Target type : Basic
      (A)Field SYSTEM_TIME SENSITIVE changed from YES to NO
      (A)Field BUSINESS_TIME SENSITIVE changed from YES to NO
      (A)Field ARCHIVE SENSITIVE changed from YES to NO
    Trigger will be altered
  
  Would cause an informational message ADB7389I before this apar.
  This message has been changed
  to a warning.
  

Problem conclusion

• The problems have been resolved.
  Search Keywords: MSGADB7389I, MSGADB7389W
  

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:

  UI75676

Modules/Macros

• ADB7000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI75676

     UP21/07/02 P F106

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.