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
Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to 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 Power teams 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.
Specific link you will want to bookmark for future use
IBM Unified Ideas Portal-https://ideas.ibm.com/- Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
Graph History has a defined list of metrics that you can visualize.
However, the historical data collected on the system includes many more metrics than are visualized. This RFE is to request additional metrics be added to the graph history metric selection.
I'd like to see the following: - Number of active threads in the system - Total number of transient threads in the system - Number of active jobs in the system - Total number of transient jobs in the system - Full opens
Also, of particular interest are the metrics in the QAPMHMSQPL file.
Historical data has many valuable use cases; expanding the metrics that are visualized can increase the value of Graph History.
For active jobs and threads, it is helpful to know the overall trend over time to help understand workload growth. Likewise with transient jobs and threads. Db2 and SQL metrics are really needed to help understand workload changes over time, or plan cache efficiency over time. Metrics related to the plan cache, in particular, can be very useful to help identify "When did something change...."
Historical data can be very useful in identifying anomalies, particularly recent issues where the full Collection Services data still exists on the system. The CS data can then be reviewed with PDI to identify what caused the usual event.
Without adding these metrics to Graph History, you have to query the historical data files directly, which can give good insights, but graphs provided in Navigator would make this useful to those that do not understand how to query the historical data directly.
Do not place IBM confidential, company confidential, or personal information into any field.