Note the following points when using the remote API facility:

• Do not use an asynchronous-response-type RPC with the remote API facility. If this type of RPC is used, the remote API facility is ineffective and the RPC works as a normal RPC.
• Do not use the XATMI interface with the remote API facility. Operation of OpenTP1 is unpredictable if the XATMI interface is used.
• If a RAP-processing client uses the remote API facility to call the function dc_rpc_call() from within a transaction, the requested service is not run as a transaction.
• You cannot acquire RPC trace information on communication that was performed using the remote API facility. However, information on the function dc_rpc_call() that was executed on the RAP-processing server is obtained in the RPC trace information area.
• The response statistical information and communication delay time statistical information do not include information on services and results that were communicated using the remote API facility.
• When executing an RPC via the gateway of an application gateway-type firewall, you might use the remote API facility with the -w option specified in the dcsvgdef definition command of the user service network definition. In this case, even if you call the function dc_rpc_call() with the transaction attribute, it is not regarded as a transaction. Therefore, when you have used the remote API facility, the operation for starting chained RPCs from within a transaction and terminating the chained RPCs by means of synchronization point processing does not execute properly. Terminate the chained RPCs explicitly by calling the function dc_rpc_call() with DCNOFLAGS specified in flags.
• Normally, the RAP-processing server is started automatically by the RAP-processing listener. Do not independently terminate (by executing the dcsvstop command) or start (by executing the dcsvstart command) the RAP-processing server. However, in the following cases, use the dcsvstart command to start the RAP-processing server.
  

  When the RAP-processing server fails to start due to a definition error:

  Even when you cannot start the RAP-processing server due to a definition error or other problem, the RAP-processing listener cannot detect the failure to start the RAP-processing server. The system therefore remains in the status that indicates preparation of the remote API service (the status when the message KFCA26950-I is output). If the message KFCA01812-E with the error reason code CONFIGURATION is output when the RAP-processing listener starts the RAP-processing server, check the definition of the RAP-processing server and use the dcsvstart command to start the RAP-processing server. Note that the message KFCA00244-E cannot detect a definition error for the RAP-processing server.

  When the RAP-processing listener goes down while the RAP-processing listener and the RAP-processing server are terminating:

  After the RAP-processing listener goes down, even if you start the RAP-processing listener using the dcsvstart command, the RAP-processing server outputs the KFCA26950-I message and the system may remain in the status that indicates preparation of the remote API service. If the RAP-processing server is not started, start it by executing the dcsvstart command.

• Do not execute the scdhold command for the RAP-processing server while the RAP-processing server is online.
• Do not call a service request that uses the remote API facility for a UAP on the same node as the RAP-processing server. Processing cannot be guaranteed in such a case.