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 Not under consideration
Workspace z/OS
Created by Guest
Created on Apr 2, 2020

DEFINE USERCATALOG and Master Catalog UPDATE Authority Bypass

Storage Administration staff members should be specifically allowed to perform usercatalog recoveries without the provision of master catalog UPDATE authority. Currently, when a Storage Administrator attempts to Define or Connect a Usercatalog, UPDATE access to the Master Catalog is required.

Separation of duties often mandates that only Systems Programmers should have an access level to the Master Catalog that is higher than READ authority. It is too easy for someone who has master catalog UPDATE access to unintentionally pollute the master with non-system catalog entries, as this can ultimately put Systems Programmers into difficult situations, and can also impact performance of the Catalog Address Space.

This is a request to implement a mechanism similar to the existing FACILITY profile STGADMIN.IGG.DEFDEL.UALIAS, where a clerical staff is allowed to update the master catalog with usercatalog alias maintenance without actually having UPDATE access to the master catalog. In present context, the new control point would instead bypass the need for master catalog UPDATE authority for those who are responsible for recovering usercatalogs.

Idea priority Low
  • Guest
    Reply
    |
    Feb 5, 2024
    This item is a valid requirement but unlikely to be given high enough priority to be placed into the product plan. If this requirement is high value, please re-open it, or open a new requirement.