OpenTP1 can perform transaction control in client/server mode. This facility enables the UAP processing over multiple processes to be executed as one transaction. There are two functions for transaction control applicable to OpenTP1 UAPs:

• OpenTP1 specific interface
• TX interface (transaction control conforming X/Open specifications)

This section explains OpenTP1 specific interface. For details on TX interface, see 5.2 TX interface (transaction control).

This section explains transaction control involved in UAPs (SUP, SPP) in client/server mode. For details on transaction control involved in UAPs (MHP) in message exchange mode, see 3.7 MCF transaction control.

• Notes on using UAPs with TP1/LiNK
  To implement transaction control through UAPs used with TP1/LiNK, specify that the transaction facility will be used when setting up a TP1/LiNK execution environment.
  

Organization of this section

2.3.1 Transaction in client/server mode

2.3.2 Acquiring a synchronization point

2.3.3 Specification of transaction attribute

2.3.4 Relationship between remote procedure call modes and synchronization points

2.3.5 Transaction optimization

2.3.6 Posting information about the current transaction

2.3.7 Disposal in case of heuristic situation

2.3.8 Notes on transaction processing