Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Workspace AIX
Created by Guest
Created on Nov 10, 2022

Maintain paths returning PQ=1 in Failed status after reboot

At the moment when a LUN inquiry returns Peripheral Qualifier (PQ)=1, the path to the LUN is considered in Failed status. In the event of a LUN path temporarily changing to Unavailable (ASC/ASCQ 0x04/0x0C ) and therefore setting PQ=1, that situation would affect to a number of paths.

If that state changes, the change can be notified to the initiator via UA to a healthcheck operation if using TUR or in the inquiry response itself.

But if that state persists and the AIX system reboots in that period, those paths would transition to Missing state. If at that point the state of the path changes and given that no healthcheck would traverse a Missing path without intervention, the path will require manual intervention to recover.

This behaviour transform a temporary state into a persistent state arbitrarily just by the reboot. We would consider the treatment should be the same and the path in should have the same status (Failed) in both situations, so the OS would recover the path if there is a change in state irrespective of a reboot occurring in the interval. (subject to hcheck_mode)

Idea priority Medium