OpenTP1 Version 7 Programming Guide

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

5.2.3 Restrictions on using TX_ functions

Organization of this subsection
(1) Use of OpenTP1 functions when using TX_ functions
(2) Relationship between dc_rpc_open() and tx_open()
(3) Difference between dc_rpc_close() and tx_close()
(4) Relationship between tx_open()/tx_close() and open/close functions specific to RM

(1) Use of OpenTP1 functions when using TX_ functions

OpenTP1 functions can be used along with TX_ functions. However, do not use TX_ functions together with the transaction control functions (dc_trn_ ~) of OpenTP1. Transaction control cannot be performed with mixed use of both facilities.

(2) Relationship between dc_rpc_open() and tx_open()

Call the function dc_rpc_open() before tx_open(). If tx_open() is called without the function dc_rpc_open(), error is returned with TX_ERROR.

(3) Difference between dc_rpc_close() and tx_close()

The function dc_rpc_open() cannot be called after the function dc_rpc_close() is called. However, tx_open() can be called after tx_close() is called. When the UAP is to be placed in dormant state due to traffic, call tx_close(), then recall tx_open().

(4) Relationship between tx_open()/tx_close() and open/close functions specific to RM

tx_open() and tx_close() are the functions which inform each RM that access was requested by UAP or it ended. By using tx_open() or tx_close(), processing requests from UAP are posted to each RM.

The open and close functions specific to RM (e.g., dc_dam_open(), dc_dam_close()) indicate the start and end of actual processing. If tx_open() or tx_close() is called, the open and close functions specific to RM do not become unnecessary.