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.
Ability to prune/delete Autonomic Symptoms, Actions, and Utility History table data
There is currently no supported process that will allow a user to cleanup all or selected rows in the Symptoms, Actions, and Utility History tables in the DB2 Autonomics Director for z/OS database DYXDB. These tables are populated by the DB2 Auton...
Copy profiles seamlessly across DB2 subsystems on different LPARs
The export/import functionality in the DB2 Automation Tool can be used to seamlessly copy object, exception, utility, or job profiles from one DB2 subsystem to another as long as both the source and target subsystems are running on the same LPAR. ...
Additional Attributes Needed for Object Prioritization Entries
Object prioritization entries added in the DB2 Automation Tool do not have CREATED USERID, CREATED TS, LAST UPDATED USERID, and LAST UPDATED TS attributes associated with them. This makes it very difficult to determine when an entry was added or l...
Summary Grouping and Detail Breakdown of Autonomics Actions by Symptom
It would be helpful if the Autonomic Console within the DB2 Automation Tool provided the ability to see both a summary grouping and a detail breakdown by symptom of any autonomic actions (either passive or active) within a maintenance window. A si...
Automation Tool incorrectly building RUNSTAT jobs when TS has NPSI being RUNSTAT
Unfortunately the product has been generating jobs incorrectly from the getgo for RUNSTATS. When using load balancing across 20 jobs, the partitions should be spread across the 20 jobs. This works when the NPSI is not having RUNSTATS. When the ...
Option required for viewing complete formatted Advanced SQL in Object Profiles
There is currently no option available to (re)view the complete formatted Advanced SQL in an Automation Tool Object Profile.
The only option that is available is to view this SQL is using PF10 / PF11 from panel HAA£OPRU as 80 bytes or so at a tim...
Need ability to easily copy maintenance window definitions
We would like the ability to easily copy maintenance window definitions from one DB2 subsystem to another. This would include all time periods defined within the window. Typically, maintenance windows are initially set up for a single Db2 subsyst...
Provide the ability to filter Autonomic Execution History by Time of Day
We have many scheduled autonomic-related events/actions that execute throughout a given day, every single day, but at the same time each day. When viewing theses actions in the Autonomic Execution History in the Autonomic Console, there may be hun...
Provide the ability to delete all associated actions when deleting a maintenance window
When testing the generation of autonomic actions into a maintenance window, it is sometimes very helpful to be able to delete all of the actions that have been generated into a maintenance window. This is true even if the actions are generated as ...
Do not place IBM confidential, company confidential, or personal information into any field.