When a UAP on a client node issues an API, OpenTP1 can transfer the API to the server for processing on the server. This facility is called the remote API facility. A UAP which requests the remote API facility from a client node is called a RAP-processing client. The API issued by the RAP-processing client is accepted by the RAP-processing listener on OpenTP1 and is run on the server node by the RAP-processing server. The RAP-processing listener and RAP-processing server run as user services on OpenTP1. You must set up the operating environment for the RAP-processing listener and RAP-processing server using the rapsetup command.

To use the remote API facility, define the service information (host name and port number) of the communication destination in the user service network definition. Include the -w option in the definition. Create a RAP-processing listener service definition on the server. Also automatically generate user service definitions for the RAP-processing listener and RAP-processing server using the rapdfgen command. The figure below shows the remote API facility.

Figure 2-24 Remote API facility

The following tables show the APIs for which remote execution is possible using the remote API facility for each type of RAP-processing client.

• For RAP-processing clients based on TP1/Server Base or TP1/LiNK
  

  C language library	COBOL-UAP creation program
  dc_rpc_call	CBLDCRPC('CALL ')

  See the TP1/LiNK User's Guide when using TP1/LiNK.
  
• For RAP-processing clients based on TP1/Client/P or TP1/Client/W
  

  C language library	COBOL-UAP creation program
  dc_rpc_call_s	CBLDCRPS('CALL ')
  dc_trn_begin_s	CBLDCTRS('BEGIN ')
  dc_trn_chained_commit_s	CBLDCTRS('C-COMMIT')
  dc_trn_chained_rollback_s	CBLDCTRS('C-ROLL ')
  dc_trn_unchained_commit_s	CBLDCTRS('U-COMMIT')
  dc_trn_unchained_rollback_s	CBLDCTRS('U-ROLL ')

  See the manual OpenTP1 TP1/Client User's Guide TP1/Client/W, TP1/Client/P when using TP1/Client/P or TP1/Client/W.
  
• For RAP-processing clients based on TP1/Client/J
  

  Method
  rpcCall
  trnBegin
  trnChainedCommit
  trnChainedRollback
  TrnUnchainedCommit
  trnUnchainedRollback

  See the manual OpenTP1 TP1/Client User's Guide TP1/Client/J when using TP1/Client/J.
  
• For RAP-processing clients based on TP1/Client for .NET Framework
  

  Method
  Call
  Begin
  CommitChained
  RollbackChained
  Commit
  Rollback

Organization of this section

2.2.1 Application of the remote API facility

2.2.2 Permanent connection

2.2.3 Connection mode

2.2.4 Chained RPCs using the remote API facility

2.2.5 Notes on the remote API facility