RACF® does not need a TP profile within a TP profile data set. But in order for the RACF subsystem address space to register as an APPC server (see Providing security for server access to specific LU or TP names), a DBTOKEN must be associated with a TP profile data set. You can use a DBTOKEN associated with a TP profile data set that is already in use for APPC/MVS, such as the one being used by the APPC/MVS scheduler (ASCH). If you need to create a TP profile data set and get a DBTOKEN, see z/OS MVS Planning: APPC/MVS Management for additional information. No APPC side information profile is needed for RACF, and no profiles are required in the TP profile data set for RACF.