You should run one instance of rpcbind per z/OS® image under a user ID with UID(0) and the
SYSMULTI security label. You must define the resource profile EZB.RPCBIND.sysname.rpcbindname.REGISTRY
in the SERVAUTH class. Enable applications to register and unregister
with rpcbind by granting at least READ access to the resource profile
for the user IDs under which the applications run.
Tip: The registration and deregistration procedures PMAPPROC_SET,
PMAPPROC_UNSET, RPCBPROC_SET, and RPCBPROC_UNSET are defined in RFC
1833 Binding Protocols for ONC RPC Version 2.
Requirements: - The rpcinfo utility can list and delete rpcbind registrations.
You cannot delete rpcbind registrations using rpcinfo unless the user
ID has at least READ access to the resource profile.
- Some RPC library calls register and deregister applications with
rpcbind or portmapper. These calls include registerrpc(), svc_register(),
pmap_set(), and pmap_unset(). An application that uses these library
calls must run under a user ID that has been granted at least READ
access to the resource profile.
Client programs can request that rpcbind forward RPCs to registered
server programs. For each of these target assistance requests, the
rpcbind server forks a new process that runs under the security label
of the client's network security zone. The user ID under which rpcbind
runs must have at least READ access to each of these security labels
that you want to support.
Tip: The RPC library routine pmap_rmtcall() issues target
assistance requests on behalf of the caller.