TMF Application Programmer's Guide (G06.24+)

File System Procedures
HP NonStop TMF Application Programmer’s Guide—522419-004
4-10
ENDTRANSACTION
ENDTRANSACTION
This procedure commits the database changes associated with the current transaction.
The only application process that can execute an ENDTRANSACTION call is the
requester process that initiated the particular transaction.
When a requester calls ENDTRANSACTION, TMF attempts to commit the changes
made to the database by the transaction. If the action completes successfully, the
changes made by the transaction are permanent and the locks held for the transaction
are released. Locks on inserted, updated, or deleted items are held until TMF has
written a commit record to the audit trail.
If the calling process did not explicitly open its TFILE, calls to ENDTRANSACTION are
waited operations: ENDTRANSACTION does not return control to the calling process
until TMF has written a commit record to the audit trail, thereby ensuring that the
transaction will commit. ENDTRANSACTION does not, however, wait for the
transaction’s locks to be released.
If the calling process explicitly opened its TFILE, calls to ENDTRANSACTION are
nowait operations: ENDTRANSACTION returns control immediately to the calling
process and the request must be completed by a subsequent call to the AWAITIO
system procedure.
Syntax for C Programmers
Syntax for TAL Programmers
Parameters
status returned value
INT
is a file system error number:
#include <cextdecs(ENDTRANSACTION)>
short ENDTRANSACTION();
status := ENDTRANSACTION;
0 Successful completion.
30 System unable to obtain message block, or is already using its
maximum number of RECEIVE or SEND message blocks.
75 Current transaction in nil state.
78 Invalid or obsolete transaction identifier.