Space announcements

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

INPUT statement

The INPUT statement specifies the source where Log Master reads DB2 log records. This statement defines the input source for all log scans within the current work ID.

The following figure shows the INPUT statement syntax.

Note

For compatibility with earlier versions, Log Master also supports an INPUT keyword on the LOGSCAN statement. This keyword is deprecated and might be removed from future versions. (It defines the input source for an individual log scan, but the input source must always be the same for all log scans within a job step.)


BSDS

Directs Log Master to scan the current DB2 log files that are listed in the bootstrap data set (BSDS) of DB2. This is the default value.

LLOG (cntlDataSetName)

Directs Log Master to read log records from one or a set of logical log files previously created by Log Master or an application program that conforms to the published format. Enter the name of the data set that contains the control file of the logical log. Log Master uses information in the control file to locate and read the logical log data file, and any other files associated with the logical log.

Enter a name that follows conventional guidelines for data set names. Separate multiple logical log data sets with commas. Be aware of the following points as you specify input logical log files:

  • If you enter a GDG base as cntlDataSetName, Log Master includes all available generations of the file in the input.

  • If you specify more than one logical log control file as input (directly or by specifying a GDG base), Log Master automatically runs in overtime mode.

  • If you specify input logical log files, you cannot define an ongoing log scan.

DB2LOG

Directs Log Master to read log records from a specific DB2 log file or set of DB2 log files. You can define the exact location of the DB2 log files. For more information about specifying the DB2 log files, see DB2 log input definition.

DB2 log input definition

Use this syntax to define a specific DB2 log file or set of DB2 log files where Log Master obtains DB2 log records.

The following figure shows the DB2 log input definition syntax used in the INPUT statement.


You can define the exact location of the DB2 log files. If you specify more than one log file, you must specify the files in the order defined by the ULOGORD installation option. For more information, see ULOGORD=ASCENDING.

Log Master either sorts input DB2 log files or processes them concurrently (performs a merge action) depending on the following criteria:

  • Whether you are running in a data sharing environment

  • The settings of the Log Master LOGSORT and LOGTAPES values

  • Whether you specify a member name to group each member’s DB2 log files

Criteria for either sort or merge of DB2 log files

Group files with member name?

Data sharing environment

Non-data sharing environment

Yes

Merge

No

Merge (unless LOGSORT is NEVER; see LOGSORT in LOGOPTS statement)

Merge

When you define a specific DB2 log file or set of DB2 log files as input, you might need to specify more resources than you expect (such as additional DB2 log files or image copies). This requirement occurs for the following reasons:

  • Unless the tables selected by your filter are defined with the Data Capture Changes (DCC) attribute, Log Master frequently requires resources other than your selected DB2 log files for row completion processing. The resources can include

    • Additional DB2 log files from other members in a data sharing group (for example, if activity on another member affects the table rows selected by your filter)

    • Additional DB2 log files that cover periods of time outside of your range definition (for example, log files covering the period between an image copy and the start point of your range)

  • If the DB2 objects selected by your filter reside in compressed table spaces, Log Master can require image copies to obtain a valid compression dictionary. You can define the location of the image copies by using the IMAGECOPY statement. Log Master can also store copies of compression dictionaries in the Old Objects Table of the Repository. For more information, see INCLUDE DICTIONARY in LOGSCAN statement.

dataSetName

Specifies a data set containing DB2 log records. The name that you enter must follow conventional guidelines for data set names. To specify DB2 log files from a non-data sharing system (or from only one member of a data sharing group), do not enter a memberName value.

If you list multiple DB2 log files, specify them in the correct order. The correct order depends on the setting of the ULOGORD installation option. Log Master always expects to read log files from the lowest RBA/LRSN value to the highest. If you specify a list of log files that is not in RBA/LRSN order after Log Master applies the ULOGORD setting, you can encounter errors. For more information about the correct order with the ULOGORD installation option, see ULOGORD=ASCENDING.

DEVT deviceType

Specifies the type of device that contains the DB2 log data set. Enter a site-specific name for a type of storage device (for example, 3390 for a DASD device or TAPE for a magnetic tape device).

VOLUME (volser)

Specifies the VOLSER where the DB2 log data set is located. Separate multiple VOLSERs with commas.

memberName

Specifies the name of a member in a data sharing group. Use this keyword to specify DB2 log files that come from more than one member in a data sharing environment. Group the log files from each member together, preceding the group with the member name. Within each member, specify the log files in the correct order. For more information, see dataSetName. For example, if two members of a data sharing group are DHF1 and DHF2, a correct INPUT statement would be:

INPUT DB2LOG
(
DHF1( DSNDHF.DHF1.ARCLOG1.A0005229,
      DSNDHF.DHF1.ARCLOG1.A0005230 )
DHF2( DSNDHF.DHF2.ARCLOG1.A0005849,
      DSNDHF.DHF2.ARCLOG1.A0005850 )
)


Was this page helpful? Yes No Submitting... Thank you

Comments