Portmapper and rpcbind target assistance

Portmapper and rpcbind assist clients in contacting server programs. Either portmapper or rpcbind can be used on the same host, but not both. If the client sends an RPC with the target program number, version number, procedure number, and arguments to the server listening on port 111 (rpcbind or portmapper), that server locates the target server in its list of registered servers and passes the client’s message to the target server. When the target server returns information to portmapper or rpcbind, the information is passed to the client along with the port number (or universal address, if rpcbind is being used) of the remote program. The client can then contact the server directly.

Requirement: The following apply when the rpcbind server runs on a multilevel secure host.

The rpcinfo utility issues a target assistance request on behalf of the user who invoked it when rpcinfo is invoked with the -b parameter. When the SAF profile BPX.POE is defined on your host and rpcbind is started, the rpcbind user ID must be granted at least READ access to the profile to enable rpcbind to respond to rpcinfo -b requests.
When the SAF profile BPX.POE is defined in class FACILITY and the rpcbind server is in use, the rpcbind user ID must be granted at least READ access to the profile to enable the server to support target assistance requests.

Rules:

The target assistance RPCs: PMAPPROC_CALLIT, RPCBPROC_CALLIT, RPCBPROC_BCAST, and RPCBPROC_INDIRECT, are defined in RFC 1833: Binding Protocols for ONC RPC.
The following RPC library routines issue target assistance requests on behalf of the calling application: pmap_rmtcall() and clnt_broadcast().