The user ID associated with the RACF address space is not required to be privileged or trusted. However, if the user ID is not privileged or trusted, it must explicitly be given update access to all data sets used by RACF remote sharing facility (RRSF). Failure to do so results in access errors.

The user ID can be made privileged or trusted by activating the STARTED class and defining a profile for the user ID and specifying either privileged or trusted. The RACF address space must then be stopped and restarted. Alternatively, an entry for the user ID specifying either privileged or trusted can be made in the RACF started procedures table. However, the new entry does not take effect until the next IPL.