This is the public portal for all IBM Z Hardware and Operating System related offerings. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
In our z/OS V2R5 environment, we observed that RMF MONITOR 3 CF OVERVIEW record couldn't be found which is empty. The Time gap is from 02/16/22 15.17.10 to 02/16/22 16.48.00.
Our JB0 system ran into issue during this time range, but we don't think RMF 3 CF Overview should be missing where other LPARs were still working well and communicating with CF healthily.
In the case, the supporter clarified to us it works as design with the explanation below about Sysplex reporting mechanism for RMF monitor III reporting.
The Sysplex related reports ( e.g. CFOVER ) rely on every single LPAR data to be shown at all time, so
if you have data from 30 days long from all the LPARs in your SYSPLEX and have one single LPAR from which you have just one day of data in your Monitor III datasets, that’s the whole amount of data you’ll get in the CFOVER: 1 day only.
In other words, only if one system is down in the time range which has no MONITOR3 data, then the whole SYSPLEX related records(e.g CF Overview) couldn't be report in RMF for the time range even if other LPARs are healthily working.
In the common understanding, other LPARs are still alive which are communicating with CF, then RMF CF Overview report should be provided. Here shouldn't be based on the minimum set, but the alive set.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.