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 Delivered
Workspace PowerHA for AIX
Created by Guest
Created on May 30, 2018

Add cancel option if an RG handling failed

Today, if a RG processing fails. After a manual fix all remaining tasks mast be finished to get the cluster to a stable state.
I would be good to have a cancel option.
So that after, manually removing the reason why it failed, the RG handling can be restated.

Idea priority High
  • Guest
    Jun 13, 2019

    .( Feature included from 7.2.3)
    Feature contains below
    ??? pre/post/notify events can be specified for individual events - new option can be set for individual events as well
    ??? default will be "false" which preserves the existing behavior - failure of any of the optional methods will not affect the exit code from the event
    ??? If set to true, the following new behaviors will occur:
    ??? failure of a pre, post or notify event will be treated the same as a failure in the "main" event
    ??? non-zero return code will be returned to clstrmgr and the node will go to RP_FAILED state -manual intervention will be required.
    Pre and post run in foreground ??? notify always run in background