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.
R2PRO00006892 - include a matching timestamp for a given activity record in all the tables
Farmers currently retains 4+1 rolling months of WLM activity data involving the following WLM tables, and we would like to add a 'date' column having a default valude current timestamp in these 3 tables:
- ACTIVITYMETRICS_DB2ACTIVITIES_V97 (Note: No date column)
I would like to get your expert opinion to know if there can be any issue with adding this new column to the 3 WLM tables in the Audit Schema.
Maintenance is handled by a manual process that we would like to automate using range partitioned tables. But since the IBM-supplied WLM tables are not range partitioned, and one of the tables doesn't even have a date column, it has been challenging to implement a workable solution. Would any of these be acceptable (from an IBM standpoint)?
We will add a new column using the following command:
- ALTER ADD a YYYYMM column to each of the 3 WLM tables listed above.
Do not place IBM confidential, company confidential, or personal information into any field.