IBM Z Hardware and Operating Systems Ideas Portal
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).
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.
Thankyou for submitting this requirement. Although HealthChecker is limited in passing PARMS to the checks, we think this is a reasonable request that we can look into for the future.
I work with the Ben that has opened this RFE. Wanted to explain the reason we do not duplex these structures. One is a structure used by a product that has its own recover mechanism to reprocess the data should we have a CF or LPAR failure causing us to loose data. Also we chose this because the impact of duplexing was not able to be tolerated by the application. The second is an MQ structure used to store data for inquire only transactions. If messages are lost they choice was made to let this occur. This again was chosen only because the structure duplexing was not able to be tolerated by the application.
The availability to process this exclusions allows us to get the benefit of the check for all other structures but allows legitimate exclusions. I think the check environment as a whole would benefit from allowing an exclusion list for each check.
Thanks, Casey Rhodes
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - BCP_XCF/XES
Operating system - IBM z/OS
Source - Other
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - Other
Operating system - IBM z/OS
Source - Other
Attachment (Description): Heath Check for nonvolatile