Like a function call, OpenTP1 UAP can request a service to another UAP without recognizing which network node includes the service providing UAP. This interprocess communication is called remote procedure call (RPC). There are three RPCs applicable to OpenTP1 UAPs:

• OpenTP1 specific interface
• XATMI interface (RPCs conforming X/Open specifications)
• TxRPC interface (RPCs conforming X/Open specifications)

When TCP/IP is used as the communication protocol, the above three types of remote procedure calls can be used. When OSI TP is used as the communication protocol, only the XATMI interface can be used. For details on the remote procedure calls available with OSI TP, see 2.10 Client/server mode communication using OSI TP and 5.1 XATMI interface (client/server-mode communication).

This section explains OpenTP1 specific interface RPCs. For details on XATMI interface and TxRPC interface, see 5.1 XATMI interface (client/server-mode communication) and 6.1 Communication through TxRPC interface.

Note

Assume that you want to perform a transactional RPC on an OpenTP1 system other than the domain specified in the all_node clause of the system common definition. In this case, you must ensure that the node identifiers (node_id clause of the system common definition) of all OpenTP1 systems in the local domain and remote domain are unique. In addition, all the OpenTP1 systems must be version 03-02 or later. If these conditions are not met, the transaction may not recover properly.

Organization of this section

2.1.1 How to implement the remote procedure call

2.1.2 Transferring data through the remote procedure call

2.1.3 Outline of remote procedure call modes

2.1.4 Nesting services

2.1.5 Using nontransactional RPC from transaction process

2.1.6 Setting schedule priorities for service requests

2.1.7 Acquiring node address of client UAP

2.1.8 Referencing and changing response waiting intervals of service request

2.1.9 Acquiring descriptor of asynchronous-response-type RPC request which has encountered error

2.1.10 Report data to CUP unidirectionally

2.1.11 Relationship between remote procedure calls and processes for executing services

2.1.12 Notes on using a recursive call

2.1.13 Retrying a service function

2.1.14 User data compression

2.1.15 Monitoring the service function execution time

2.1.16 RPC with the multi-scheduler facility

2.1.17 RPC with a communication destination specified

2.1.18 Service request with domain qualification

2.1.19 Relationship between service functions and stubs