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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
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 |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
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.
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.