Increased processing requirements

In overtime mode, Log Master must keep track of the different instances of each Db2 object. Because of this and other overhead, an overtime job typically uses more resources and experiences more processing overhead than a job that runs in current mode. The additional requirements of overtime mode cause Log Master to:

• Examine every log record in the log scan for the object name (because it cannot rely on the current OBIDs from the Db2 catalog)

• Generate an additional log scan to search for any Db2 catalog activity that affects the objects in the filter

• Examine the Db2 catalog, the Db2 EDM pool, and the Log Master Repository tables for information about all of the objects that it encounters in the log records

In overtime mode, Log Master uses other sources to obtain structure definitions of old objects. To make this possible, you must perform extra processing to update these sources, such as:

• Running periodic (or ongoing) jobs that update the Log Master Repository with structure definitions for your old objects

  Use either of the following methods to perform this processing:

  • Generate JCL that updates the Repository by using the Generate REPOS UPDATE JCL choice on the Main Menu

  • Add a Repository maintenance step to an existing work ID, or add Repository update function to an existing log scan step

• Performing an extra, often extensive log scan that updates the Repository with structure definitions for your old objects