This portal is to open public enhancement requests against IBM Z Software products. 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.
Shipped in zSecure 3.1 SSE2 on October, 25, 2024.
Hi Linnea, you did not author this idea, but your vote has been registered.
We hope/assume that management of departmental CSDATA isn’t done via System-Wide SPECIAL. That’s what RACF field level access checking is for. Such that only people with appropriate field access can manage only certain fields. Unless somebody implemented something like USER.CSDATA.** UACC(UPDATE), which is also somewhat unwise.
The main purpose of the SEGMENT management policy profiles in CV is an extra layer to prevent System-SPECIAL users managing certain segments, or to apply a segment-related scope on the target profiles for group-special and regular users (RACF already provides an all-segments scoping policy on the target profiles).
Basically, FIELD profiles already provide for the use case as you formulate it.
Currently we use READ and UPDATE for the segment management:
READ= list command allowed
UPDATE=add/change/delete is allowed
What is the business need to distinguish 'delete' from 'change'?