Nonstop Database, HiRDB Version 9 UAP Development Guide
When a UAP commits a transaction in a process different from the process in which the UAP accessed HiRDB, the commitment processing is called moving the transaction.
The UAP referenced is a UAP that connects itself to HiRDB via the HiRDB XA library.
When the transaction-move function is used, 1 must be specified in the PDXAMODE operand of the client environment definition. For details about the PDXAMODE operand, see 6.6.4 Environment definition information.
The specification of the PDXAMODE operand affects the scope of the LOCK TABLE UNTIL DISCONNECT specification, as explained as follows:
The following table shows the scope of the LOCK TABLE UNTIL DISCONNECT specification when OpenTP1 is used.
Table 3-7 Scope of the LOCK TABLE UNTIL DISCONNECT specification when OpenTP1 is used
PDXAMODE specification | OpenTP1 specification | Scope of LOCK TABLE UNTIL DISCONNECT | |||
---|---|---|---|---|---|
0 | trn_rm_open_close_scope=process | Effective until Resource Manager is closed. | |||
trn_rm_open_close_scope=transaction | Effective within a global transaction. | ||||
1 | trn_rm_open_close_scope=process | -d option specified in trnstring operand | Effective until the Resource Manager is closed. | ||
-d option not specified in trnstring operand | A single AP comprises a global transaction in the OpenTP1 system. | ||||
Multiple APs comprise a global transaction in the OpenTP1 system. | A single AP links to the HiRDB XA library. | ||||
Multiple APs link to the HiRDB XA library. | Effective within the global transaction. | ||||
trn_rm_open_close_scope=transaction |
All Rights Reserved. Copyright (C) 2011, Hitachi, Ltd.