TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-115
ALTER TMF
that can range up to approximately 2 GB and 1024 GB in size, respectively. These
formats support audit-trail files of up to 2047 MB and 1048575 MB, respectively.
You must use the STOP TMF command to stop TMF in a clean state before issuing the
ALTER TMF command with the ATFORMAT option. However, this stoppage is
generally required only once, because the format change is typically a one-time
operation done only to move from format 1 files to format 2 files.
The new file format takes effect immediately in the configuration, but format 2 files are
only created as audit-trail files are renamed forward during audit-trail rollover. During
the subsequent START TMF operation, TMF forces rollover of each configured audit
trail. In many cases, the next audit-trail file used for a specific audit trail will be a
format 2 file. But if an audit-trail file in the prepared state exists in this audit trail, the
next file may still be a format 1 file. Nevertheless, for all later rollovers, TMF creates
format 2 files and purges the old format 1 files.
Always keep in mind that the ATFORMAT value applies to your entire TMF
configuration, but the FILESIZE value specified in an ADD AUDITTRAIL or ALTER
AUDITTRAIL command applies to the particular audit trail identified in that command.
Requesting Performance-Tuning Operations
The ALTER TMF command provides several performance-tuning functions. These
operations are very powerful, most are potentially dangerous, and all require a high
level of TMF background and often the assistance of the Global Customer Support
Center (GCSC) or your service provider. These operations were previously available
only through the SNOOP utility, a support tool provided with the TMF product and
documented in the file named $SYSTEM.SYSnn.SNOOPDOC. In the ALTER TMF
command, these operations are selected through the following options:
TRANSACTIONPROTOCOL
RESET TRANSACTIONPROTOCOL
GOREMOTE
RESET GOREMOTE
Caution. Changing from format 1 to format 2 audit-trail files may make falling back to an
earlier TMF RVU difficult; prior TMF releases cannot read format 2 audit-trail files. Thus, you
should not move to format 2 files until you are confident of the stability of this RVU in your
system environment. Once format 2 files are in use, if problems occur, you may need to delete
your TMF configuration to fall back to an earlier RVU that does not support format 2 files.
To use the ATFORMAT option, you must first stop TMF cleanly; otherwise, you cannot alter the
audit-trail file format. A clean stop provides a stable point to which you can recover should you
need to fall back to your previous format. If you have stopped TMF by using the STOP TMF,
ABRUPT command, you cannot issue the ALTER TMF, ATFORMAT command with successful
results.
For more information, see the discussion of fallback considerations in the TMF Planning and
Configuration Guide.