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 Planned for future release
Created by Guest
Created on Mar 12, 2021

HMC Security requires pattern matching to support our DevOps model

We need to give appropriate permission to our Linux LPARs to our DevOps community, we have dozens of different use cases with their own DevOps team. Separation of duty is critical, and elevated authority (such as PoR, STP/CTN etc) must be able to be restricted. Given the number of distinct user sets, we require a mechanism to use Pattern Matching on LPRA name to associate roles to the correct LPAR gourp. We anticipate a high volume of Linux LPARs coming and going over the next 12 months, and it is not practical for us to manually manage an HMC custom group that contains the Linux LPARs. We have a naming convention for our Linux LPARs, and the HMC's support for Pattern Match Groups allows us to create a group with dynamic membership consisting of all of our Linux LPARs. However the HMC does not support "child management" permission for pattern match groups. Child management permission for pattern match groups would allow us to provide a secure environment for our Linux LPARs and other z15 estate without having to manually maintain the membership of a custom group.

Idea priority High