Log Master and tasks associated with auditing
The Log Master online interface guides you through steps for specifying search criteria to select specific log records. Easily constructed filters enable you to narrow searches to specific users, tables, plans, or even column or value changes.
Audits of log information
Log Master generates reports by using a comprehensive reporting facility. You can select from a list of convenient standard default report formats with a choice of presentation, such as by user, job name, plan name, and so on.
All forms of Log Master output (including reports) include log data from transactions that are completed within the time frame that you specify. In this context, completed means either committed or aborted. Log Master also provides reports for situations when you need information about transactions that are not complete at the end of a time frame. For more information, see Auditing data changes.
Creating logical log files
Log Master provides a unique form of output called a logical log file that can help you use DB2 log data.
The format of the logical log is published and includes easy-to-use fields designed for use by application programs. You can create logical logs as the only output of a Log Master job, or in addition to generated SQL and reports.
Use the logical logs as input to application programs, input to report generators, or as permanent records of activity for audit requirements. You can even use logical logs as input to Log Master, saving the time needed to scan the DB2 log subsequent times for the same records. From a logical log, you can generate the same reports and other forms of output as you can from the DB2 log. Optionally, you can direct Log Master to include DDL objects in your logical log files. For more information, see Logical log output files.
Getting performance and statistical information
Log Master performance and statistical features:
Display statistics about log activity
Produce reports about commit, rollback, and image copy frequency
For more information, see Reference of default Log Master reports.
Analysis of data capture changes (DCC)
You can analyze the impact of creating or altering your DB2 tables to use either the data capture changes (DCC) or the data capture none (DCN) attribute.
The Data Capture Changes report displays what was actually found in the log with either of the attributes, and in addition, presents what DB2 would have logged had the data capture attribute been set to its alternate value. For more information, see Data Capture Changes report.
Support for DB2 table-level security
Log Master can honor DB2 table-level security for all Log Master jobs.
You can use installation options to enable this type of security in your environment. For more information, see "Controlled access to the DB2 log" in the Subsystem display, data sharing environments and controlled access topic.