The z/OS UNIX orpcinfo/rpcinfo command: Display server information

Use the orpcinfo command to display the servers that are registered and operational with any portmapper on your network. The orpcinfo command makes a remote procedure call (RPC) to an RPC server and displays the results.

RPCINFO can query only hosts that resolve to valid IPv4 addresses.

Tips:

rpcinfo is a synonym for the orpcinfo command in the z/OS UNIX shell. rpcinfo command syntax is the same as that for the orpcinfo command.
You can use the rpcinfo command from another platform to query z/OS® rpcbind servers for information about servers that register with a binding protocol other than Version 2.
You can also use the z/OS rpcinfo command with rpcbind servers that support RPC binding protocol Version 2, such as the z/OS rpcbind server. RPC binding protocol Version 2 is the binding protocol used by the portmapper.
All IPv4 applications can use RPC binding protocol Version 2 to register with an rpcbind server; some applications might register with an rpcbind server using other binding protocols.

Format


>>-rpcinfo------------------------------------------------------>

>--+- - p --+------+---------------------------------------------+-><
   |        '-host-'                                             |   
   +-+- - u --host --prognum--+---------+-+--+-----------------+-+   
   | |                        '-versnum-' |  '- - n --portnum -' |   
   | '- - t --host --prognum--+---------+-'                      |   
   |                          '-versnum-'                        |   
   +- - b --prognum --versnum------------------------------------+   
   +- - d --prognum --versnum------------------------------------+   
   '-?-----------------------------------------------------------'

Parameters

-p host: Queries the portmapper on the specified host and prints a list of all registered RPC programs. If host is not specified, the system defaults to the local host name. For more information about how the local host name is defined, see the z/OS Communications Server: IP Configuration Reference.
-u host prognum versnum: Sends an RPC call to procedure zero of prognum on the specified host using UDP, and reports whether a response is received. The variable prognum is the name or number of the RPC program.
-n portnum: Specifies the port number to be used for the -t and -u options in place of the port number that is given by the portmapper.
-t host prognum versnum: Sends an RPC call to procedure zero of prognum on the specified host using TCP, and reports whether a response is received.
-b prognum versnum: Sends an RPC broadcast to procedure zero of the specified prognum and versnum using UDP, and reports all hosts that respond.
-d prognum versnum: Deletes the registration for the RPC service specified by the prognum and versnum values.
-?: Specifies the command help.

Tip: The versnum value is the version of the prognum value; it is not the RPC protocol version number.

Requirement: The version number is required for the -b parameter. If a version is specified, the rpcinfo command attempts to call that version of the specified program. If a version is not specified, the rpcinfo command prints error information. For example, if -u is specified without a versnum value, the RPC program reports the versions of its program that it supports.

Restrictions:

z/OS UNIX orpcinfo -b (broadcast) displays information with the same network only. The broadcast packets do not pass through gateways.
z/OS UNIX orpcinfo -b (broadcast) works only for the UDP transport services and does not find any TCP-based services.
Only a superuser can use the -d option.
IPv6 applications cannot use RPC binding protocol Version 2 to register with rpcbind.
RPCINFO can query only hosts that resolve to valid IPv4 addresses.
When rpcbind is used in place of the portmapper, rpcinfo can display information only for servers that registered with rpcbind using the Version 2 binding protocol.

Examples

In the following example, the orpcinfo command invokes the nullproc procedure of program 100003 on host mvsx using the TCP protocol. The orpcinfo command invokes the nullproc procedure on all versions of 100003 on host mvsx and reports the result.

# orpcinfo -t mvsx 100003
 EZA4328I program 100003 version 2 ready and waiting
 EZA4328I program 100003 version 3 ready and waiting 
#

Provide security product access to rpcbind server registrations

When you invoke the rpcinfo command with the -d option, a registration from the portmapper or rpcbind server list of registered applications is deleted. You can define the following security product resource profile in the SERVAUTH class to control the ability of a user to delete registrations from the rpcbind list of registered services:

EBZ.RPCBIND.sysname.rpcbindname.REGISTRY

See the sample EZARACF member for examples of the security product commands that you can use to create the resource profile.

Rules:

If the SERVAUTH class is not active or if the security product resource profile is not defined, only UID(0) users can use the -d option to delete registrations from the rpcbind list of registered servers.
In a multilevel secure environment, only users permitted to the resource profile can delete registrations from the rpcbind list of registered servers. If the SERVAUTH class is not active or if the security product resource profile is not defined, no users can delete registrations from the rpcbind list of registered servers.

Restriction: This profile does not control the ability of a user to delete registrations from the portmapper list of registered services.

Provide security product access to rpcbind server target assistance procedures

When you invoke the rpcinfo command with the -b option, a target assistance RPC is sent to all portmapper or rpcbind servers that are in its subnet. When the rpcbind server host is multilevel secure, you can define the following security product resource profile in the FACILITY class to control the ability of a user to run this target assistance procedure on your rpcbind host.

BPX.POE

If the FACILITY class is not active or if the security product resource profile is not defined, all users can use the -b option to execute the target assistance RPC.

Restrictions:

This profile does not control the ability of a user to run target assistance RPCs on a portmapper host.
This profile applies only to rpcbind servers on multilevel secure hosts.