Skip to content

Commit

Permalink
Update "Defining the RACF ZOWE class"
Browse files Browse the repository at this point in the history
Closes zowe#3868.

Signed-off-by: Andrew Metzger andrew.metzger@ibm.com.

Signed-off-by: Andrew-J-Metzger <128719308+Andrew-J-Metzger@users.noreply.github.com>
  • Loading branch information
Andrew-J-Metzger committed Sep 11, 2024
1 parent 6306bd9 commit 1914f15
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/user-guide/mvd-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -536,6 +536,10 @@ To apply role-based access control (RBAC) to dataservice endpoints, you must ena
You can apply access control to Zowe endpoints and to your app endpoints. Zowe provides endpoints for a set of configuration dataservices and a set of core dataservices. Apps can use [configuration endpoints](../extend/extend-desktop/mvd-configdataservice.md#configuration-dataservice) to store and their own configuration and other data. Administrators can use core endpoints to [get status information](mvd-configuration.md#administering-the-servers-and-plugins-using-an-api) from the App Framework and ZSS servers. Any dataservice added as part of an app plugin is a service dataservice.

### Defining the RACF ZOWE class

> [!NOTE]
> Starting with z/OS V2R5, the ZOWE class has been predefined to RACF. If you have previously defined the ZOWE class manually, this class can be deleted after all of the systems that share the RACF database are upgraded to z/OS V2R5.

If you use RACF security, take the following steps define the ZOWE class to the CDT class:

1. Make sure that the CDT class is active and RACLISTed.
Expand Down

0 comments on commit 1914f15

Please sign in to comment.