Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Controlling access to DBC resources
The DBC subsystem always issues a Security Access Facility (SAF) security call for internal resource names. By default, if those resource names are not defined to an ESM, access to undefined DBC resources (internal functional control points) is granted for all users who can communicate to the DBC service address space. This behavior occurs because the value of the DBC <ALLOW_SAF_RC4> security parameter defaults to YES.
If you want to restrict access to DBC services that have not been defined as a resource to SAF, you must set the value of the <ALLOW_SAF_RC4> security parameter to NO. Doing so denies access to all undefined resources.
The following figure shows an example of the ALLOW_SAF_RC4 value.
You control this value through DBC security parameters defined in a file identified through the DBCSECUR DD statement in the JCL procedure for the DBC started task.
