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 z/OSMF
Created by Guest
Created on Mar 17, 2022

Define KEYRING_OWNER in PARMLIB instead of local_override.cfg

If you use a shared KeyRing (one certificate for all services on one LPAR) you have currently to alter /global/zosmf/configuration/local_override.cfg inserting a line
"KEYRING_OWNER_USERID=certOwnerID"
The KEYRING_NAME is configured in IZUPRM00.
This seems strange.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 17, 2022

    We have been trying to get that clear for some time now... not only that same types of configuration is on multiple places, some configs are only supported by "clicking in the gui"... So the more sysplexes you have, the more gui's you have to log on to, to monkey hit the desired preferences/plugins on all of your systems.

    SYS1.PARMLIB is the way to go. (It is z/OS !...) You make changes to your smpe environment, and when upgrading the sysplexes, changes are automatically implemented. Don't even have to stay awake for it to change filesystem content just before or just after upgrades...