To control which remote users or applications can access the local RRSF system, define APPCPORT profiles with the names of the remote LUs, and selectively give READ access to the user ID associated with the remote RACF® subsystems. This is an optional step which you might or might not choose to do depending on whether you are protecting access to your LUs today. For example:

RDEFINE APPCPORT partner-luname UACC(NONE)

PERMIT partner-luname CLASS(APPCPORT) ID(userid or group)
       ACCESS(READ)

SETROPTS CLASSACT(APPCPORT) RACLIST(APPCPORT)

The userid or group parameter specifies the user ID associated with the incoming request. The partner-luname parameter specifies the locally known name of the partner LU. If the APPC LUADD statement for the LU specifies the NQN option, the partner LU name is a network-qualified name of 1 to 17 characters in the form netid.luname. If the APPC LUADD statement does not specify the NQN option, the partner LU name is an unqualified LU name of 1 to 8 characters. Any time an APPCPORT profile is changed, SETROPTS RACLIST processing for the APPCPORT class must be refreshed in order for the change to take effect.