We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.
Do not place IBM confidential, company confidential, or personal information into any field.