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.
The tool currently does not support reporting on tables if they have a clone table defined on them.
The job ends with a code of 8 and message -
ALAA506E-Base/Clone tables not supported
This means that we cannot run a summary or detail report against the base table.
We have a requirement to produce a daily detail report of activity by certain users or plans against the Production schema. This is effectively an audit of those users.
In the job, we specify -
OBJECT FILTERS-BY NAME....
TABLE NAME =%
As it stands, the job fails because the tool doesn't support tables with clones defined on them.
As a workaround, we therefore have to add -
TABLE NAME =Table_with_clone%
We are therefore unable to produce a report that show whether certain users or plans have done any update activity on the base table. We do not have a requirement to report on any activity for certain users against the clone.
Do not place IBM confidential, company confidential, or personal information into any field.