HP Integrity NonStop J-Series - Manual (Page 75)

Usage Guidelines
HP NonStop AutoTMF Software User’s Guide—429952-016
5-7
Preparing Third-party Applications

Tracing shows the alteration of the open exclusion and the deblocking operations.
Preparing Third-party Applications
Numerous popular applications from independent software vendors have been
successfully converted to use audited files with AutoTMF. The conversion has not
required vendor source code or product support from the vendors. Contact AutoTMF
product support for technical notes about converting these applications.
Auditing Enscribe Queue Files
An Enscribe Queue File is a special type of key-sequenced file that can function as a
queue. Processes can queue and dequeue records to and from a queue file.
AutoTMF offers basic support for audited queue file.
AutoTMF processes a READUPDATELOCK operation on a Queue File like an
UNLOCKREC or a DELETE operation. Thus, the record is not considered locked,
allowing an automatic transaction to be committed.

Prior to executing the READUPDATELOCK operation, AutoTMF attempts to
commit any outstanding automatic transaction for the Queue File. MAXUPDATES,
MAXTIME, and isolation settings are ignored and the automatic transaction is
committed, if there are no logical locks held by the program.

If the READUPDATELOCK operation times out (error 162), AutoTMF proceeds as
follows:
1. Returns the error 162 to the program, signaling to the program that it should
retry the READUPDATELOCK operation.
2. Commits the current automatic transaction.
3. Begins a new automatic transaction.
See Chapter 7 in the Enscribe Programmer’s Guide for a full description of the
functionality and usage of Queue Files.
NonStop AutoTMF and Process Pairs
In general, NonStop process pairs are used to ensure that critical monitor-type
processing survives CPU halts and other environmental failures. For example,
processes like the Pathway TCP or the AutoTMF monitor are implemented as NonStop
process pairs. But typical database servers are usually not implemented as process
pairs.
Caution. Do not configure SEPARATETX for an audited file that is opened with the exclusion
mode Process Exclusive. Doing so causes the process to deadlock attempting to LOCKFILE
the file twice under different transactions