Work ID contents

Most tasks require that you scan the log for certain types of transactions, and then generate reports and output.

Log Master stores this type of activity in the work ID as part of the log scan step. A work ID typically contains only a single log scan step unless you create or modify it by using the Create or Edit Work IDs option.

The log scan step can include time frame, filter, report, output file, and optional log mark specifications. The log scan step includes all of the information that Log Master needs to perform a log scan, and generate reports and other output. You can also use the log scan step to update the Old Objects Table in the Repository.

Your work ID can contain a single log scan step or multiple log scan steps. The choices listed under the Actions category on the Main Menu guide you through the steps for creating a work ID with a single step.

You can also add a log scan step so that you simultaneously read the log with two different log scans, and generate two different streams of output. Work IDs that contain multiple log scan steps must use the same input source. For example, you cannot scan a logical log file and use the bootstrap data set (BSDS) to locate Db2 logs at the same time.

Be aware of the following points as you add log scan steps to a work ID:

• The Work ID Maintenance panel does not automatically generate reports and outputs. You can generate default reports and output automatically by using the task dialogs that are listed under the Actions category on the Main Menu.
• When you generate a Catalog Activity report or an output DDL file, or update the Repository, Log Master cannot generate other forms of output in the same log scan, such as other reports or SQL. To generate any other forms of output that you need in the same work ID, add an additional, separate log scan step in your work ID.
• Log Master processes log scan steps simultaneously. For example, you can add two log scan steps to a work ID that simultaneously scan two different portions of the Db2 log, and generate two different streams of output.
• Log scan parameters enable you to process Db2 catalog records, or to perform overtime processing tasks.

For more information about the topics in this section, see the following references: 

Log mark step

Use log marks to identify a point in the Db2 log for reference. You can create log marks as part of a log scan step, or in a separate log mark step, and then save them as part of a work ID.

You can also create, delete, or view information about a log mark directly from the online interface by using the Create or Delete Log Marks choice on the Log Master Main Menu.

For more information about the topics in this section, see the following references: 

Execute SQL step

You can open a new work ID or modify an existing work ID to add an execute SQL step that executes previously generated SQL.

This step enables you to use the High-speed Apply Engine to execute and monitor a set of SQL statements as part of your Log Master job or job step. After you add an execute SQL step, you can generate the JCL to run the work ID.

Be aware of the following points as you add an execute SQL step to your work ID:

• In many cases, you must add an execute SQL step to a new work ID to execute SQL that you generated under a different work ID.
• Before you select an SQL data set to execute, review its status and study its statistics. For example, you can examine the type of SQL and the number of database changes that the data set contains before you attempt to execute it.

For more information about the topics in this section, see the following references: 

Automated drop recovery step

The Log Master automated drop recovery feature works with the BMC AMI Recover product or DSN1COPY to recover dropped Db2 objects, such as tables or table spaces.

You can specify different types of output for this step, depending on the type of recovery operation that you want to perform. If you execute the generated outputs in sequence, you can recover dropped objects with a minimum of time and investigation.

For more information about the topics in this section, see the following references: 

High-speed Apply JCL generation step

You can use the Log Master online interface panels to specify configuration parameters for the High-speed Apply Engine, then generate JCL for a separate job that runs High-speed Apply using your parameters.

As you learn more about High-speed Apply, you can edit the JCL to define more parameters and use more High-speed Apply features.

For more information about the topics in this section, see the following references: 

Repository maintenance step

Log Master uses the Repository to support many types of processing, including overtime processing, which affects the Old Objects table (ALPOLDO), and ongoing processing, which affects the Open Unit of Recovery table (ALPURID).

Log Master supports completion processing, which affects the SYSCOPY table (ALPSYSCP). You can also delete the previously created output data set history tables (ALPWHIS, ALPWLSH, ALPSQLF, ALPRPTF, ALPLODF, ALPDDLF, ALPCMDF, ALPADRF, ALPLOGF).

A Repository maintenance step generates a Log Master job that performs one of the following actions:

• Updates the ALPOLDO table with object structure definitions or compression dictionaries
• Updates the ALPSYSCP table with records from SYSIBM.SYSCOPY
• Deletes information from one or more of the following tables when the information is no longer required:
  • ALPOLDO
  • ALPURID
  • ALPSYSCP
  • Output data set history tables

When you create a Repository maintenance step by using the Log Master online interface, the generated JCL actually contains specialized LOGSCAN statements.

For more information about the topics in this section, see the following references: