Setting the input source

• The log files listed in the BSDS, or a set of BSDSs for a data sharing group this source is the default on the Time Frame Specification panel. BMC AMI Log Master uses this source to locate the log records written for a subsystem or data sharing group within your time frame.
• A set of specific Db2 log files
• A set of specific BMC AMI Log Master logical log control files created by a previous run of BMC AMI Log Master

When you set the input source to Db2 log files or logical log control files, the range of the selected files sets limits on the time frame of your log scan. BMC AMI Log Master resets any predefined start or end point values. The start and end points of the selected input source define the new time frame. You can contract this time frame further, but you cannot extend it past either end of the input source. The content of the selected files, and the Db2 subsystem where the files were created, also determine the domain of your log scan.  

Input source: specific Db2 log files

When you define a specific Db2 log file or set of Db2 log files as input, you must provide at least the Db2 log files that cover the period of your time frame. In some situations, you might need to specify more resources, such as additional Db2 log files or image copies. This requirement occurs for the following reasons:

• When the input source is a logical log control file, BMC AMI Log Master does not access the current Db2 subsystem’s BSDS or Db2 catalog.
• Unless the tables selected by your filter are defined with the Data Capture Changes (DCC) attribute, BMC AMI Log Master attempts to perform row completion processing. To do this, BMC AMI Log Master frequently requires resources other than the Db2 log files covering the period that is defined in your time frame. These resources can include additional Db2 log files from other members in a data sharing group, (for example, when activity on another member affects the table rows selected by your filter), or files that cover periods of time outside of your time frame (for example, log files covering the period between an image copy and the start point of your time frame). For more information, see Row-completion-processing-and-your-jobs.
• input from Db2 log files that you specifyBMC AMI Log Master attempts to create a log mark that corresponds to the end point of the selected time frame in your log scan. If the selected end point falls outside the range of the log files that you specify, BMC AMI Log Master creates a log mark that corresponds to the current RBA when your job is executed.
• If the Db2 objects selected by your filter reside in compressed table spaces, BMC AMI Log Master might require image copies to obtain a valid compression dictionary. Define the location of the image copies by using the Specify Image Copies field on the Work ID Run-Time Options panel.

Input source: Logical log control files

Be aware of the following points when you specify the input source as logical log control files:

• The data in the logical log control file might already be filtered. You can use an additional filter to further restrict the selection of transactions.
• If you specify a generation data group (GDG) base as a logical log control file, BMC AMI Log Master includes all available generations of the file as input.
• If you specify more than one logical log control file as input (directly or by specifying a GDG base), BMC AMI Log Master automatically runs in overtime mode. For more information about overtime mode, see Processing-objects-over-time.
• You cannot define a log scan as ongoing if your input source is logical log control files.
• You cannot create a log mark within a log scan step if the log scan reads input from logical log files. In this situation, BMC AMI Log Master cannot be certain that the logical log file was created on the current Db2 subsystem.