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 BCP_WLM
Created by Guest
Created on Jun 23, 2023

Expand RACF resource OPERCMDS MVS.VARY.WLM to improve protection of WLM application-environments

V WLM,APPLENV=<name>,refresh|quiesce|resume command can be protected by OPERCMDS MVS.VARY.WLM resource. If a userID has this resource permitted, he can issue the "v wlm,applenv..." commands to every application-environment with any operation, which is not a good solution, because this includes production and none production apple-envs and all "v wlm" operations.

So SAF resource cheching OPERCMDS MVS.VARY.WLM should be expanded by the name or pattern name of the application-environment. 

Accesslevels should be used to protect the "v wlm" operation.
acc(read) only for REFRESH operation
acc(update) all operations (REFRESH,QUIESCE,RESUME etc.)

Example:
user1 should only be able to only refresh applenv r0gdwlm0 via mvs command
MVS.VARY.WLM.R0GDWLM+ acc(READ)

admin user2 should only be able to refresh,quiesce,resume all applenv's (begining with R) via mvs command
MVS.VARY.WLM.R+++++++ acc(UPDATE)

I know, that there is a way to do this by MVS Commands Exits. But in general, we don't like to implement assemblers anymore, because the people who can do it won't be available in the future.

So it would be the better way, if the checking of resource mvs.vary.wlm would be expanded as mentioned above.

 


 

Idea priority Medium