TMF Reference Manual (G06.24+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-002
3-120
DISABLE DATAVOLS
If you want to disallow audited updates on a volume that is already being processed by
the DISABLE DATAVOLS command (entered without the ABRUPT option), issue a
second DISABLE DATAVOLS command with ABRUPT specified. This second
command overrides the first and prevents further audited activity on the volume.
Much work on behalf of the DISABLE DATAVOLS command is done by the operating
system’s disk process. When the disk process successfully completes, in an orderly
way, all work that should be done during a transaction processing shutdown, the
volume specified enters the disabled-clean state. If this orderly shutdown does not
occur, however, the volume is placed in the disabled-dirty state. Specifying the
ABRUPT option is likely to place a volume in the disabled-dirty state, but this result is
not guaranteed. Whether the state is disabled-clean or disabled-dirty, the result is the
same: transaction processing is disabled for the specified volume. Regardless of
whether the state is disabled-clean or disabled-dirty, volume recovery will return the
volume to a consistent state after it is again enabled.
Examples
The following DISABLE DATAVOLS command shuts down transaction processing for
the volume named $DATA2, but allows transactions in progress on the volume to
complete:
TMF 27> DISABLE DATAVOLS $DATA2
$DATA2 -- disabling datavol.
TMF 28>
The next DISABLE DATAVOLS command shuts down transaction processing on two
data volumes, $DATA3 and $DATA4, and abruptly terminates any such processing now
in progress on those volumes:
TMF 28> DISABLE DATAVOLS ($DATA3, $DATA4), ABRUPT
$DATA3 -- disabling datavol.
$DATA4 -- disabling datavol.
TMF 29>
Caution. Leaving data volumes disabled for long durations can cause audit-trail files to
accumulate. This accumulation, in turn, can potentially cause TMF to reach the
OVERFLOWTHRESHOLD and BEGINTRANSDISABLE limits.