RACF subsystem address space considerations

The RACF remote sharing facility requires that the RACF® subsystem address space be active. If you want to use remote sharing functions on an MVS™ system image, you must first activate the RACF subsystem address space. See Activating the RACF subsystem for information on how to do this.

If you already run with the RACF subsystem address space active, you must update your JCL if you want RACF to automatically process a member of the RACF parameter library when the RACF subsystem address space is activated. See The RACF parameter library for information on the RACF parameter library. See The RACF PROC for information on how to update your JCL.

You must ensure that the user ID assigned to the RACF subsystem has access to the resources that remote sharing functions use, including:

Workspace data sets
APPC-related profiles
The RACF parameter library

Guideline: Define this user ID to be trusted or privileged. See Assigning a user ID to the RACF subsystem.

If your RRSF network uses the TCP/IP protocol, the RACF subsystem must be able to use z/OS® UNIX socket APIs. To allow the subsystem to use these APIs, you must ensure that user ID for the RACF subsystem is assigned a UID, and that its default group is assigned a GID.