OpenTP1 Version 7 Description

[Contents][Glossary][Index][Back][Next]

3.7.3 Connection mode

There are two permanent connection management modes (automatic connection mode and non-automatic connection mode). These modes differ in the method of establishing and releasing the connection. In the automatic connection mode, OpenTP1 manages establishing and releasing a connection. In the non-automatic connection mode, the user manages establishing and releasing a connection. You can specify the connection mode in the user service definition of the RAP-processing client.

Organization of this subsection
(1) Automatic connection mode
(2) Non-automatic connection mode

(1) Automatic connection mode

In this mode, OpenTP1 manages establishing and releasing a permanent connection. A permanent connection is automatically established when the RAP-processing client issues dc_rpc_call, specifying a service group name that is defined with the -w option in the user service network definition.

A permanent connection starts at issuance of dc_rpc_call to a service group in the user service network definition and ends at issuance of dc_rpc_close for terminating the remote procedure call.

(2) Non-automatic connection mode

In this mode, the user manages establishing and releasing a permanent connection. The user issues the API (dc_rap_connect or dc_rap_disconnect) for establishing or releasing a connection at a RAP-processing client. If the user has not established a permanent connection when the RAP-processing client issues dc_rpc_call with a service group name defined with the -w option in the user service network definition, the dc_rpc_call fails.