Before you begin
When a Local OS Registry is chosen for z/OS, the started task identity is chosen as the server identity. Thus, a user ID and password is not required to configure the server.
Note: Each started task, (for example, controller, servant, node agent, and so on) might have a different identity.
For all servers in a given cell to have the authority needed by the administrative subsystem, they must be part of a common configuration group. This customization is generally provided by the configuration dialogs when WebSphere Application Server for z/OS is initially customized.Why and when to perform this task
The following steps are needed to perform this task initially when setting up security for the first time.Steps for this task
SMF records access violations no matter what value is
specified for this new property. This property affects access violation message
generation for both application-defined roles and for WebSphere runtime-defined
roles for the naming and administrative subsystems. EJBROLE profile checks
are done for both declarative (deployment descriptors) and programmatic checks:
If your changes are not validated, the server might not restart.
Results
The Local OS user registry has been configured.What to do next