There are two ways to start rpcbind as a z/OS® UNIX socket
application:
- From the z/OS shell
- As a started task
It cannot be started from TSO.
To start rpcbind from the z/OS shell,
the user ID must be an authorized superuser. The authorized superuser
ID can issue to start rpcbind. For information about assigning superuser attributes, see z/OS UNIX System Services Planning.
You can also start rpcbind as a started task from the MVS™ console with the START command, as follows:
START RPCBIND
You can specify the following options when you are starting rpcbind:
- Specify -d for rpcbind to send trace
information to the daemon facility of syslogd.
- -df sends flow information.
- -dl sends log information of all RPC
procedures called.
- -dx sends XDR information.
- The -i option enables you to specify
the z/OS UNIX file system directory to which the pid
file is written. The pid file name is always rpcbind.pid. If -i is
not specified, the rpcbind process ID is written to /etc/rpcbind.pid.
Restriction: The directory path name must be an absolute path
name. That is, it must begin with the forward slash (/) character,
as shown in the following example:
rpcbind -i /tmp
- The -n option enables you to direct
rpcbind to run in a non-swappable environment. A process might need
to run as non-swappable to ensure that it is available during periods
of high CPU usage. However, a non-swappable process might convert
real storage in the system to preferred storage. Because preferred
storage cannot be configured offline, allowing rpcbind to run in a
non-swappable state can reduce the future ability of your installation
to reconfigure storage.
If you do specify the -n option,
ensure that the user ID associated with rpcbind has at least READ
access to the resource profile BPX.STOR.SWAP in the FACILITY class.
The default is to start rpcbind as swappable.
- The -s option specifies the number of
statistics entries per binding protocol that rpcbind maintains. Valid
values are in the range 113 – 500. Statistics that are maintained
by the rpcbind server are used to reply to the RPCBPROC_GETSTAT request.
For more information about statistics that are maintained by the rpcbind
server, see RFC 1833.
Result: Rpcbind
calculates the number of pages that are needed to store statistics
for the value that is specified, and obtains that number of pages
of shared memory for statistics. Rpcbind rounds up the number of statistics
entries it tracks to fully use the shared memory.
Tip: Rpcbind
does not start unless it can obtain sufficient shared memory to maintain
statistics for the number of entries you specify. You configure the
number of pages of shared memory available to z/OS with the IPCSSHMMPAGES parameter in the
BPXPRMxx member of SYS1.PARMLIB.
- To display help information, specify the -? option.
Restriction: Portmapper and rpcbind cannot be run at the
same time, as they both listen on /etc/services sunrpc
port 111.