Step 1: Configuring the PROFILE.TCPIP data set for rpcbind

Guideline: The rpcbind server is a generic server, as described in Generic servers in a CINET environment.

In a single stack environment, you can use the AUTOLOG statement to automatically start generic servers.
In a multiple stack environment, it is not advisable to use the AUTOLOG statement to start generic servers. You can use an operations automation software package that IBM® or other companies provide to automatically start generic servers.

If you want the rpcbind server to start automatically when the TCPIP address space is started, include rpcbind in the AUTOLOG statement in the PROFILE.TCPIP data set.

AUTOLOG
  RPCBIND JOBNAME RPCBIND1
ENDAUTOLOG

To ensure that port UDP 111 and TCP 111 is reserved for the rpcbind server, add the rpcbind server job name to the PORT statement in the PROFILE.TCPIP data set. If you use the sample cataloged procedure, RPCBIND, to start the rpcbind server, the job name is RPCBIND1.

PORT
  111 UDP RPCBIND1     ; rpcbind server
  111 TCP RPCBIND1     ; rpcbind server

If you start the rpcbind server from the z/OS® UNIX shell, the job name is OMVS.

PORT
  111 UDP OMVS         ; rpcbind server OMVS
  111 TCP OMVS         ; rpcbind server OMVS

For more information about the PORT statement, see z/OS Communications Server: IP Configuration Reference.