HP Integrity NonStop J-Series User Manual
Page 94
NonStop AutoTMF Commands
HP NonStop AutoTMF Software User’s Guide—429952-016
6-18
ADD ATMFPROGRAMS
suppresses the use of TMF in programs. When specified,
SUPPRESSUSERTX has the following effects:
All BEGIN and ENDTRANSACTION operations requested by the
application are ignored.
All transactions inherited from requesters through messages on
$RECEIVE are ignored.
FILEINFO requests for audited files report that files are not audited.
This facility is for testing only. Programs that make use of TMF may depend on
the correct operation of the calls that are eliminated by setting this option.
Enabling this option may cause program failures and data corruption.
TMF operations may be suppressed for a program by specifying the class map
define
.
TXTIMEOUT { value | NEVER | OFF }
sets the maximum duration of an automatic transaction, regardless of the TMF
AutoAbort setting. This feature requires TMF version 3.6 or later.
value: is n [ SEC[ONDS] | MIN[UTES] ], between 5 and 510 minutes.
value overrides the TMF AutoAbort timer setting. A value entered as
n SEConds is rounded up to minutes.
NEVER: the transactions is never aborted by TMF due to a timeout.
OFF: the default, specifies that the TMF AutoAbort is in effect.
If TXTIMEOUT is configured on a system that is not running TMF 3.6 or later, a
warning message is displayed, the configuration is updated and the transaction
timeout takes effect when TMF 3.6 is installed.
WAITEDIO
converts NOWAIT I/O operations to WAITED I/O operations.
If WAITEDIO is specified for a NOWAIT file open, AutoTMF automatically
performs an AWAITIO operation immediately following the various forms of
READ and WRITE. After the AWAITIO completes, AutoTMF commits any
outstanding transactions using the usual algorithms as directed by the
configuration.
AutoTMF saves the values returned by AWAITIO, and returns control to
program as if the READ or WRITE operation were still in progress. For a
READ, the data buffer contains the input data.
Note. The AutoTMF AutoCommit timer always applies, regardless of the configured
transaction timeout. If the desired transaction time out value exceeds the configured
AutoCommit timer value, the user should adjust the AutoCommit timer accordingly.
See AutoCommit attribute description above on page
for details.