Assigning an RPC program number to DSO

The information in this topic is applicable only for on-premises deployments.

Dedicated (private) remote procedure call (RPC) program numbers are not required by , but you might want to use them in these circumstances:

• You have a large environment with heavy data traffic.
• Your environment distributes large amounts of data.

If you dedicate an RPC program number to , it must be one of these:

• 390600 (administrative queue)

  Success

  Best practice
  We do not recommend assigning the RPC program number 390600 to DSO because the administrative queue is single-threaded.

• 390621 -390634, 390636 -390669, 390680 -390694 (private queue)

The  server uses the assigned RPC program number for all communication with the associated . You must allocate at least one thread to the server queue associated with the RPC program number.

If you do not assign a dedicated RPC program number to , the fast and list queues process all distributed operations.

For more information about threads and queues, see AR-System-server-architecture-and-scalability.

To assign an RPC program number to  on the local 

1. Open the AR System Administration: Server Information form for the appropriate .
2. Click the Ports and Queues tab.
3. Verify that the RPC program number that you want to assign to  is listed in the Server Queue table.
   If the number is not listed, add it. (See the 2024-07-10_01-44-14_Setting ports and RPC numbers)
4. Click the Connection Settings tab.
5. On the Connection Settings tab, click the DSO Server tab.
6. In the DSO Local RPC Program Number field, enter the appropriate RPC program number, and click OK.

7. To make the change take effect, restart the .

   If you reassign the RPC program number while running DSO and then restart the , you do not lose any items in the distributed pending queue.