IBM RegTech Ideas Portal

 Welcome!

 

Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.

 

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

 

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

 

The shorter URL for this site is:   http://ibm.biz/WFS-Ideas

IBMers, please visit the WFSS Internal Ideas portal https://ibm.biz/WFS-Internal-Ideas

 

note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

FTM Housekeeping for DNI_A_MSG_PBOU1 table

Our bank performs regular housekeeping on our FTM DNI_A_MSG_PBOU1 table.
However, after applying latest FTM 3.0.0.8 patches,
Our housekeeping jobs don't work anymore.

We opened PMR : 29110,000,778.
L2 support suggested to refer to common solution given : https://www.ibm.com/support/knowledgecenter/SSRH32_3.0.0_SWS/housekeeping_with_data_integrity_framework.html

Which means user need to :
1) drop all triggers that were created for the data integrity framework.
2) Perform housekeeping of FTM tables.
3) Re-create the data integrity triggers.

The solution is unacceptable as user might drop and recreate wrong DB2 triggers and risk jeopardizing our FTM system.

FTM should have functions for user to perform housekeeping of ANY FTM tables without those tedious & dangerous process.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 9 2019
  • Shipped
Component Usability
Priority High - Critical
  • Attach files
  • Admin
    Achim Schneider commented
    31 Jul 09:43am

    Housekeeping has been changed since FixPack9 to include routines (DI_OPEN, DI_CLOSE) to support housekeeping where data integrity is active. This removes the requirement for drop/reactivate triggers