You can use RACF® (or an equivalent product) to control which user IDs or groups of user IDs are authorized to access DFM. To accomplish this, you need the following information:

• Name of your DFM TP profile
• User IDs that will be authorized EXECUTE access to your APPC/MVS TP
• User IDs that will be authorized as APPC/MVS administrators to read and update DFM TP profile information

The RACF APPCTP resource class controls the use of the APPC/MVS TP. Profiles in this resource class define which user IDs can execute the APPC/MVS TP. The names of these profiles are in the form dbtoken.level.tpname, where

dbtoken

The database token associated with the DFM TP profile (1 to 8 characters). The TP profile must have a database token, or else APPC/MVS cannot call RACF for TP access security. For more information about adding a database token, see z/OS MVS Planning: APPC/MVS Management.

level

This is one of the following:

• The name of your system library (for example, SYS1), if the TP is available to all users who can access the LU
• A group ID, if the TP is available to a group
• A user ID, if the TP is available to just a specific user

tpname

The name of the DFM TP profile, which is always ^X'07'001 (see Adding the TP Profile to the VSAM KSDS)