TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-59
ALTER AUDITTRAIL
RESET FILESIZE
resets the FILESIZE attribute to the originally assigned default, which is as follows:
•
For format 1 files, 100 (resulting in files of 100 MB each).
•
For format 2 files, 1024 (resulting in files of 1024 MB each).
COMMITHOLDMODE
determines whether the specified audit trail is in commit-hold mode.
ON
places the specified audit trail in commit-hold mode. In this mode, if the
hardware components needed to ensure ZLT for this audit trail on the backup
system in an RDF configuration become unavailable, the TMP immediately
stops writing audit (which includes transaction commit and abort records) on
the primary system. This deferral of audit is known as “activating commit-
hold,” because it prevents the completion (commit or abort) of transactions.
Activating commit-hold effectively places transaction completion “on hold” for
the system.
As an example, suppose that your TMF system supports five audit trails (the
master audit trail and the AUX01, AUX02, AUX03, and AUX04 auxiliary audit
trails). You set COMMITHOLDMODE to ON for the master audit trail, AUX01,
and AUX02. Sometime later, an event happens that removes the guarantee of
ZLT on AUX02. This event activates commit-hold, preventing transaction
completion on the entire system, affecting all five audit trails.
As long as the components needed to support ZLT remain available, however,
transactions are allowed to complete (commit or abort) in the normal way.
Before you can turn COMMITHOLDMODE to ON for an auxiliary audit trail, you
must turn COMMITHOLDMODE to ON for the master audit trail. Before you
Note. This option is only available on systems running the HP NonStop™ Remote
Database Facility (RDF) subsystem that guarantees Zero Lost Transactions (RDF/ZLT).
This option is enabled when RDF/ZLT is installed; if RDF/ZLT is present on your system
and this option is not presently enabled, please contact the Global Customer Support
Center (GCSC).
For more information, see COMMITHOLDMODE and COMMITHOLDTIMER Option
Considerations on page 3-68.
Note. If commit-hold is activated, the visible impact to customer applications will be
that any request to commit or abort transactions will not complete until either the
problem that activated commit-hold is corrected, or until you suspend or turn off
COMMITHOLDMODE.