Using Responder User Profile Facility

Using the platform server user profile responder facility requires only two steps.

1. Define a remote user ID/password combination for a particular node.
   You must also define the local RACF user ID that is used when a match is found. For more information, see Managing User Profiles.
2. Specify in the platform server GLOBAL or node parameter: RESPONDER_PROFILE=YES or RESPONDER_PROFILE=DUAL.
   When the platform server accepts a request, it first determines if there is an enabled node definition for the system that initiated the request. Then it scans the user profile data space for a match on the following information:

   • User ID of the remote user that submitted the transfer request.
   • Password entered by the remote user that submitted the request (this field is optional).
   • Node name, IP address, or IP name.

   If a match is found, the platform server substitutes the local user defined in the user profile for the user ID/password defined by the user that initiated the request. If a match is not found, the platform server terminates the request with a return code, and a message is returned to the user that submitted the file transfer request.

   Note: If RESPONDER_PROFILE=DUAL is specified, the request is not terminated even if a match is not found, the processing continues and the request is checked for trusted user ID (ACCEPT_VERIFIED_USER), and if necessary, the RACF or ACF2 or Top Secret user ID is validated.

   When a user on a remote system submits a request to the platform server, the user enters a remote user ID and a remote password. This user ID/password is compared against the profile REMOTE_USER and REMOTE_PASS parameters for a match. When a match is found, and the node name matches as well, the profile LOCAL_USER becomes the RACF user that is associated with the transfer request.