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 Future consideration
Workspace z/OS
Categories ICSF
Created by Guest
Created on May 13, 2020

ICSF Keylabel Alias Support

In order to remove the need to change hard-coded ICSF key label names within applications and the RACF database, we would like to have the ability to assign one-or-more aliases to a keylabel in the CKDS/PKDS.

For example, we might have the following keylabels in the CKDS ...
PING.APP1.V01
PING.APP1.V02
PING.APP1.V03

we would now like to define an alias called PING.APP1 and associate it with the current version of the key (PING.APP1.V03). The alias name can then be hard-coded in application programs and the RACF database and subsequently do not need to be changed when a new version of the key is generated.

This method allows an organisation to rotate operational keys without impacting applications and other system components where keylabel names are hard-coded.

Idea priority High
  • Guest
    Reply
    |
    Aug 6, 2020

    Spoke w/ customer about alternative solution using existing ICSF services which worked out, but agreed to keep this RFE open as a more simple approach.

  • Guest
    Reply
    |
    May 21, 2020

    Email sent to submitter with possible alternative solution to this request.