AutoTMF Software User's Guide (Update 12)

NonStop AutoTMF Software Commands
HP NonStop AutoTMF Software User’s Guide—429952-014
6-11
ADD ATMFFILESET
configures files to be accessed by the programs using separate automatic
transactions. Specify SEPARATETX when automatic transactions for a file are
always to be used (even if the process has its own transaction) and the
transaction should be managed separately from transactions for other files.
SKIPNULLRECS
(for entry-sequenced files only)
instructs the NonStop AutoTMF software runtime to ignore zero-length records
when reading sequentially through an audited entry-sequenced file.
If a record is inserted into an audited entry-sequenced file and subsequently
backed out because a transaction is aborted, a zero length record is left in the
file where the record had been inserted. This cannot occur if the file is not
audited and can cause problems for programs that are not expecting to
encounter such records. SKIPNULLRECORDS shelters the application
programs from these unexpected records.
Although automatic transactions are never aborted by NonStop AutoTMF
software, unilateral aborts could leave such gaps in an entry-sequenced file.
By default null records are not skipped.
TXTIMEOUT { value | NEVER | OFF }
(with SEPARATETX only)
specifies how long automatic transactions may live, regardless of the TMF
AutoAbort setting. This feature requires TMF version 3.6 or later.
°
value is n [ SEC[ONDS] | MIN[UTES] ]
value can be between 5 and 510 minutes and overrides the TMF
AutoAbort timer.
°
NEVER specifies that the TMF AutoAbort timer is not in effect.
°
OFF 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 issued, the configuration is updated and the transaction
timeout takes effect when TMF 3.6 is installed.
IF TXTIMEOUT is specified, SEPARATETX must also be specified
WAITEDIO [, WAITTIME 1-to-n-seconds ]
converts NOWAIT I/O operations to WAITED I/O operations.
Note. The AutoTMF AutoCommit timer always applies, regardless of the configured
transaction timeout. If the desired transaction time out value exceeds the default
AutoCommit timer value, the user should adjust the AutoCommit timer accordingly.
See AutoCommit attribute description above on page 6-7
for details.