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.

LOGSCAN column include/exclude definition

This topic describes the Column include/exclude definition syntax of the LOGSCAN statement.

This syntax enables you to explicitly control which table columns appear in the generated output. For example, you can create a report that does not print the information in a sensitive column, or you can generate MIGRATE SQL that duplicates only certain columns into another database.

Column include/exclude definition syntax diagram

Be aware of the following points regarding included or excluded columns:

  • If you include columns in (or exclude columns from) a logical log file, the same columns are included in or excluded from all other forms of output that are defined for the log scan.

    For example, if you request both logical log and SQL output files, and you exclude the ROWID column of a LOB column from the output logical log file, Log Master excludes the LOB column from the output SQL file as well. In this situation, Log Master cannot generate the SQL for the LOB column because the ROWID was removed from the logical log record that it was processing. This limitation also applies to the DOCID column of an XML column.

  • If you exclude columns from an output SQL file, and the Db2 log for your selected objects contains an update action that affects only the excluded columns, Log Master:

    • Does not generate an UPDATE statement

    • Increments the 'updates eliminated' value in message BMC097226

    • Includes an ANSI-standard comment in the SQL file to note the omitted update action

  • Do not confuse the Column include/exclude definition with a filter predicate that selects records based on a specific column. The differences are as follows:

    • A Column include/exclude definition affects the entire column in the output (regardless of the value in the column). If you exclude a column, the output does not contain the specified column at all.

    • A filter predicate based on a column value affects log records in the output (based on the column’s value in the log record). If a filter excludes records based on a column’s value, the output still contains the specified column, only certain log records are missing. For more information, see Filter predicate.


Directs Log Master to generate output that includes or excludes certain columns. You cannot specify an include list and an exclude list for the same table.

INCLUDEDirects Log Master to include only the column or columns specified by the COLUMNS keyword.
EXCLUDEDirects Log Master to exclude the column or columns specified by the COLUMNS keyword. The output contains all of the original table columns except those in the exclude list.
TABLE owner.tableName

Specifies the table that contains the column or columns specified by the COLUMNS keyword. All of the columns in a single column list must be part of the same table. To specify columns from more than one table, you must specify multiple TABLE keywords.

To fully qualify a table, enter the owner of the table. If you do not specify an owner ID, Log Master uses a default value. The default value is the user ID of the batch job that runs Log Master. Separate the owner ID from the table name with a period.

COLUMNS (columnName)

Specifies the column or columns in a given table that Log Master includes in (or excludes from) the generated output. You can specify one or more columns in the table, separated by commas.

Related topic

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