TMF Introduction (G06.26+)

TMF System Management

HP NonStop TMF Introduction—522414-002

6-5

Tasks for Managing TMF

Managing TMF typically involves:

•

Configuring TMF

•

Designating audited files for TMF protection

•

Specifying compression of selected audit records

•

Managing audit dumps and online dumps

•

Monitoring TMF

•

Managing the TMF catalog

Configuring TMF

Through TMFCOM, you can create, alter, and determine the status of audit trails, data

volumes, and other objects that TMF requires or uses in its operations.

For example, you use the ADD AUDITTRAIL command to configure an audit trail and

to specify whether audit dumping will be performed for the audit trail.

You configure at least one audit trail before starting TMF for the first time, and can add

more anytime thereafter while TMF is running. You configure audited data volumes

and the TMF catalog, and can alter most configuration attributes, while TMF is running.

Designating Audited Files

If TMF is to protect a database file (an SQL table or an Enscribe file), the file must first

be designated as audited.

SQL/MP tables are designated as audited by the AUDIT attribute, used in the standard

SQL statements CREATE and ALTER. By default, these tables are audited. The

SQL/MP data dictionary is always audited.

SQL/MX objects are always audited.

In both SQL/MP and SQL/MX, you use the CREATE statement when you create the

table or the ALTER statement after you create it.

Enscribe files are designated as audited by the File Utility Program (FUP) commands

CREATE and ALTER. By default, Enscribe files are not audited.

Specifying Compression of Selected Audit Records

The disk process can reduce the size of some audit records by including only the

changed fields in each before-image or after-image. In a personnel file, for example, a

transaction might change only the salary field without affecting the name, address, and

other data. With compression, only the salary and some control information are written

to the audit trail; the unchanged fields consume no audit trail space.