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
Categories TSO
Created by Guest
Created on Jul 6, 2023

Allow definition of user's PREFIX in RACF TSO segment

Currently, a TSO User's prefix defaults to USERID.  This is not suitable in all environments
I would like the ability to specify a PREFIX in the TSO segment (for example, to set this to the user's DEFAULT group).
The prefix is stored in the UPT Control-Block, but this cannot be updated via RACF administration. 

Idea priority Low
  • Guest
    Reply
    |
    Jul 27, 2023
    This item is a valid requirement but unlikely to be given high enough priority to be placed into the TSO/E product plan.
  • Guest
    Reply
    |
    Jul 25, 2023

    The user may have the ability to change their prefix, but security access to that HLQ can be restricted.
    Currently, having the userid as the default requires a unique security profile for each user, and a catalog entry for each user. This is a huge administrative overhead.

    Currently, we set the default prefix via a logon script, but the ability to set this in the RACF profile would be far more appropriate for us.

  • Guest
    Reply
    |
    Jul 24, 2023
    We do not see a Business justification, could you provide one?
    The user has the ability to set and maintain his own prefix, so if the system has set one, they could change it. There currently is no administrator function to set and maintain this field. An exit can be used to implement this.
    At this point this looks like it would be low priority item.