IBM Z Software
This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - zSeries Software
Product - Tivoli OMEGAMON XE on z/OS
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Performance Monitoring
Product - Tivoli OMEGAMON XE on z/OS
Currently there is an API where OMEGAMON XE on z/OS pulls data from RMF. Targeted data and metrics collected from RMF for spin locks, waits removes the burden of double data collection. Over time OMEGAMON XE will establish more use cases to collect more metrics to avoid double collections where the data between RMF and OMEGAMON XE is normalized or collecting is the same. Based on the current plans and priorities, this will be improved based on both RMF development plans and OMEGAMON XE as it takes both development groups. An API is already being used and for this reason, no work to establish another API would be needed. For this reason, this is being rejected.
Attachment (Use case): RMFIII metrics that we would need to see from OM/XE