TMF Application Programmer's Guide (H06.06+, J06.03+)

File System Procedures
HP NonStop TMF Application Programmer’s Guide—540139-009
4-51
Usage Considerations
For a list of file system error numbers, see the Operator Messages Manual.
exttransid input
FIXED:ref:2
or
FIXED .EXT64:ref:2
the transactional identifier returned by TMF_SUSPEND_EXT_ or
GETTRANSINFO.
Usage Considerations
Applications using TMF_JOIN_EXT_ must also use TMF_SUSPEND_EXT_.
TMF_SUSPEND_EXT_ and GETTRANSINFO return exttransid, which is used in
subsequent calls to TMF_JOIN_EXT_.
TMF_JOIN_EXT_ has the same semantics as the implicit transaction propagation
provided by the file system and provides the same function when the file system
propagation is not appropriate to the application.
A joined transaction uses one of the entries in the calling process' TFILE. If the
process has not explicitly opened the TFILE, the joined transaction uses one TFILE
entry that exists for all processes. If there are no available TFILE entries when the call
76 Transaction ending or aborting.
78 Invalid transaction identifier.
82 TMF not running.
83 Too many transactions (a single-threaded requester
tried to initiate a transaction while a transaction is in
progress, or a multithreaded requester attempted to
initiate more concurrent transactions than there
were TFILE entries).
84 TMF not configured.
721 BEGINTRANSACTION not completed.
731 The process has already called TMF_JOIN_ or
TMF_JOIN_EXT_ for this transaction.
This error now always returns when
TMF_JOIN_EXT_ is called and the calling process
has a current transaction.
732 The process has already called TMF_RESUME_
for this transaction.
Note.
EPTAL callers can pass 64-bit pointers by specifying the compiler directives
__EXT64 and SETTOG _64BIT_CALLS before sourcing from the EXTDECS file.