CORBA 2.6.1 Programmer's Reference

Chapter 7. Transaction Service
Chapter 7. Transaction Service
Overview
Transaction Models (1.2.4.1)
Service Architecture: Transaction Context (1.3.2)
Service Architecture: Exceptions (1.3.6)
Current Interface (2.2)
TransactionFactory Interface (2.3)
Coordinator Interface: get_transaction_name (2.6.1.5.)
RecoveryCoordinator Interface: replay_completion (2.7.1)
TransactionalObject Interface (2.11)
The User's View: Application Programming Models (2.13.1)
The User's View: Checked Transaction Behavior (2.13.3)
The User's View: Resume Check (2.13.4.3)
Model Interoperability (2.14.3)
X/OPEN Checked Transactions: Reply Check (2.13.4.1)
XID (B.3.3)
This section applies to the Transaction Service Specification, Version 1.3March 2001 .
Overview
HP NonStop Object Transaction Service (NSOTS) implements the CosTransactions module of the
Transaction Service to provide distributed transactional execution for both C++ and Java CORBA
applications. NSOTS serves in both superior and subordinate roles to HP NonStop Transaction
Management Facility (TMF). NSOTS and TMF communicate through a pseudo file called a recoverable
resource manager file (RM file). NSOTS and TMF exchange signals through this file using Open TMF
APIs. These signals start and terminate transactions. The RM file is also used during the initialization of
NSOTS to recover any in-doubt transactions following a failure. The name of this file has a suffix that is
based on the process name and its opening is logged in the NSOTS log file. For security reasons TMF
must verify the permission to open this file. Therefore, the installation user, the installation prefix, and
the NonStop TS/MP user environment must be consistent or TMF returns error 48 (FESECVIOL).
Unwanted RM files can be destroyed with TMFCOM.