Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Log Master for Db2 13.1.

Log scan example


The following example illustrates how the parts of a log scan relate to a typical work situation.

Assume that you need to audit all of the transactions that were applied to your company’s accounting database since noon yesterday. To do so, you must complete the following steps to define a log scan:

  1. Define a time frame and input source.

    Every time frame has a start point and an end point that define the scan range of the log scan. In this case, you set the start point to noon yesterday, and the end point to the current date and time.

    Define the input source as the boot strap data set (BSDS). The BSDS, which contains information about all log files for a Db2 subsystem, is Log Master’s default input source.

    With this step, you have selected all log records created from noon yesterday to the present time for your entire Db2 subsystem.

  2. Define a filter.

    In this example, you need to audit only transactions that affect the accounting database, so your filter selects log records with a database name of ACCT.

  3. Define the type of report or output file that you need; in this example, define the output to be an Audit report.

When your Log Master job is run, the resulting log scan selects all of the accounting transactions written to the log since noon yesterday, and prints them in an Audit report.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*