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 Submitted
Created by Guest
Created on Oct 9, 2024

Add options for connecting to a decommissioned CPC

When a CPC has been removed (i.e. moving from z15 to z16), it stays in the network for a little while.  When doing the HWILIST such as by Broadcom's BCPii feature, it gets this decommissoned CPC and tries to connect.   Once it tries the RESTful interface, it tries 6 times with 5 min. waits in-between.  This can really drag out the time it takes to initialize. Like 25 min. per CPC.  I checked with Broadcom and they are not specifying any # of retries or wait time when trying to connect.  Ideas are numbered below:

1) Support a way for HWILIST to exclude CPCs that are in a "no longer being monitored" status as seen by new D BCPII,ALL command.

2) Allow an option on a connect for REST to reduce the # of re-tries and/or the wait time in-between tries.

Idea priority Low