IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

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

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Mapping Source Tables to Target Tables using Db2 Administration Tool masking principles

Using Db2 Log Analysis Tool, Classic Menu, option 5  "Execute dynamic SQL in batch", we are able to map from Source Table to Target Table. But table owner and table name of source and target name must be specified at full. If we have 50 tables, where all 50 tables have owner "JOHN" and we want to convert table owner "JOHN" to table owner "BILL", we must specify all 50 tables. 

A workaround is possible. We only specify 1 table, and then manually edit the "FILTER DD" job Card, where we paste the remaining 49 tables into the JCL deck.

This could be done with a REXX, reading the reports from Db2 Log Analysis Tool and creating input to the "FILTER DD" Card, by using our mapping rules.

But we generally do not want to use this kind of "exit" coding, if we are able to avoid this.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 28 2019
  • Planned for future release
Who would benefit from this IDEA? Any user for Db2 Log Analysis Tool, who want to apply UNDO or REDO records into new tables. We have converted customer from CA Log Analyzer and with this tool we are able to use wildcards when mapping source tables to target tables.
How should it work?

The conversion from source table to target table, should be done with the same principles as DB2 Administration Tool uses MASKING.

We would like to set "Table owner" for source table to "JOHN" and "Table owner" for target table to "BILL". Table name for both source and target is specified as "*". In this way, we will be able to convert table owner "JOHN" to table owner "BILL" for all 50 tables, and we do not need to specify any table name.

Idea Priority Medium
Priority Justification Every installation using IBM Log Analysis Tool
Customer Name Jndata
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions