IBM Support

How RPC Works



How RPC Works


How does RPC work?

OS: <None> - <None>
DATABASE: <None> - <None>
WEB SERVER: <None> - <None>
WEB BROWSER: <None> - <None>


Resolving The Problem


Client Side

There are RPC clients that wish to make a remote procedure call to a different machine. These clients need to know the RPC number for the requested service to be able to make the call. (This data is stored in the Registry for DCS Manifest Client.)

A connection is made to a known RPC query daemon brought up on all servers supporting RPC. (This is documented in /etc/services as port 111.) Once the connection is made to port 111 of the destination IP, the client queries it as to what port to ask for service for "MyRpcNumber". The Server at port 111 replies this query with "MyPCPortNumber" for "MyRPCNumber". The Client then makes a connection to the port "MyRPCPortNumber" and starts communication.

Server Side

Programs which are RPC service providers register with "portmap" (the querying daemon). While registering, the program provides the "MyRPCNumber" and can optionally request for itself to be assigned a specific port for listening. If the requested port is free, "portmap" acknowledges the registry for future connections. If no specific port number is requested, "portmap" assigns a random port number for the Service.

When any client desires to execute an RPC, it first checks against "portmap" at port 111 and asks for the port number where the RPC number is available.

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number


Product Synonym


Document Information

Modified date:
16 June 2018