Availability Guide for Application Design

Data Protection and Recovery
Availability Guide for Application Design—525637-004
4-10
Interfaces From a NonStop Tuxedo Client Process
transaction. This design empowers developers to protect all critical data while
minimizing the scope of the transaction.
Most supported languages provide an interface to these features. Not only are these
features available to programmers writing code to use HP interfaces on an HP
NonStop system, but they can also be accessed indirectly from client processes.
Access from a client process can use the NonStop Tuxedo /WS product or the Remote
Server Call/MP (RSC/MP) product for applications that exclusively use the Pathway
transaction-processing environment.
Interfaces From a NonStop Tuxedo Client Process
NonStop Tuxedo client processes can use either the Application Transaction
Management Interface (ATMI) standard interface or the TX standard interface to
provide indirect access to the transaction-control features of the TMF product.
Table 4-1 lists the statements used to start, commit, or abort a transaction using these
interfaces.
Refer to Section 5, Increasing the Availability of Tuxedo Applications, for more
information on availability for this type of application. For details of the NonStop
Tuxedo programmatic interface, refer to the NonStop Tuxedo System Application
Development Guide.
POET Interface (D-Series only)
The POET Gateway provides an application program interface (API) that allows you to
call the TMF transaction control features from a client process running in a Microsoft
Windows environment.
Table 4-2 lists the statements to start, commit, or abort a transaction using the POET
API.
Table 4-1. NonStop Tuxedo Interfaces to Transaction Control Facilities
Function... Is provided by the ATMI statement...
Is provided by the TX
statement...
To start a
transaction
tpbegin() txbegin()
To commit a
transaction
tpcommit() txcommit()
To abort a
transaction
tpabort() txabort()