Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Created by Guest
Created on Dec 4, 2017

Create 'Blue' hardware error based on channel error threshold being exceeded

We recently has a 'storm' of IFCC errors on a FICON channel over a number of days that ended up causing an outage on a pair of VM SSI LPARs . After the fact, we saw that we'd received hundreds of "Purge Path Extended Data" errors on the channel, but there was never an indication from the processor view that there was an error. Ideally, we'd have seen a blue hardware error days in advance to notify us of an error in the channel path.

Idea priority Medium
  • Guest
    Reply
    |
    Jul 13, 2018

    We reviewed the request to create hardware messages from IFCC errors and have concluded that this is not a viable option for the following reasons:
    IFCC errors are typically related to network problems, but not hardware failures.
    Nearly all client systems generate many IFCCs and hit IFCC thresholds frequently. If we created hardware errors in all these cases then most systems would be creating hardware messages repeatedly for non-hardware errors.
    It is our belief that most clients would not expect or want this behavior.
    Repeated hardware messages for IFCCs we could potentially mask real hardware errors by flooding the hardware messages.
    There are already several notifications for IFCCs and tasks to investigate them.
    Some of the tasks to analyze IFCCs include:
    The "IFCC and other errors task"
    Perform Problem Analysis
    Fiber Channel Analyzer
    Notifications include:
    The background color will change if the acceptable status flag is set for CHPIDs (the default behavior looks for IFCC errors).
    The Operating System shows channel errors.
    Operating system messages are also generated.