Even when a RAP-processing client recognizes that a permanent connection has been established, the connection may be invalid (such as when the machine on the RAP-processing server side is powered off). In this case, the RAP-processing client may issue dc_rpc_call to send a service request to the RAP-processing server. This can happen even though the service request cannot reach the RAP-processing server, and no reply to the dc_rpc_call returns to the RAP-processing client until a timeout occurs.

To prevent this problem, define the RAP-processing client manager service definition and start up the RAP-processing client manager. The RAP-processing client manager determines whether the current connection is valid before the RAP-processing client issues dc_rpc_call.

When the RAP-processing client manager determines that the current connection is invalid, it releases the unnecessary connection if it is in the automatic connection mode. Then it establishes a connection again, and issues dc_rpc_call to send a service request. If in the non-automatic connection mode, the dc_rpc_call returns an error due to DCRPCER_NET_DOWN.

To set the operating environment of the RAP-processing client manager, execute the rapsetup command. To start up the RAP-processing client manager, execute the rapdfgen command and create a user service definition for the RAP-processing client manager.

Note:

When the RAP-processing client manager is restarted after abnormal termination or when the RAP-processing client manager has terminated normally, a RAP-processing client may forcibly close the current connection, assuming the connection to be invalid. If the forcibly closed connection was valid, OpenTP1 outputs message KFCA26965-E (when the static connection schedule facility is used) or message KFCA26956-W (when the dynamic connection schedule facility is used).

For details on messages KFCA26965-E and KFCA26956-W, see the manual OpenTP1 Messages.