LOGSCAN SQL file definition
For more information about Unicode characters in SQL output files, see Considerations for output files and Unicode.
The following figure shows the SQL file definition syntax of the LOGSCAN statement.
SQL file definition syntax diagram
SQL type/output definition
The SQL type/output definition defines the type of SQL that Log Master generates and where it writes the generated SQL. For more information, see SQL type/output definition.
Specifies the columns that Log Master includes in the WHERE clauses of generated SQL. By default, Log Master uses available index information to determine what columns to include. To explicitly control the columns used, enter one of the following choices:
Directs Log Master to embed ANSI-standard comments in the generated SQL. These comments describe unit of recovery identifier (URID) information and other information related to the database structures. This information is useful under some circumstances. This keyword is optional.
Regardless of whether you specify this keyword, Log Master can include comments in the generated SQL to provide information about conditions detected during SQL generation.
Specifies how frequently Log Master includes COMMIT statements in the generated SQL. The value can represent a number of SQL statements or a number of transactions. In this context, transactions are considered to be the same as unit of recovery identifiers (URIDs).
Log Master enables you to express commit frequency for SQL generation differently than for DDL generation. You can express the SQL frequency as a number of statements or a number of transactions. You must express the DDL frequency as a number of statements.
If you specify INCLUDE DDL in the SQL type/output definition, Log Master treats the commit frequency value as a number of statements for DDL and a number of transactions or statements for SQL, depending on what you specify.
If you omit the COMMIT FREQUENCY keyword, the default value is equivalent to one transaction (insert COMMIT statements in output at the same points as in the original SQL). If you specify a value without specifying STATEMENTS or TRANSACTIONS, the default value is TRANSACTIONS.
|UPDATE ALL COLUMNS|
Directs Log Master to generate SQL that updates all columns in a table row (whether the column is changed or not). If you omit this keyword, Log Master generates SQL that updates only the changed columns in a row.
Determines which character Log Master uses to represent the decimal point in the generated SQL. Log Master extracts the default character for DECIMAL POINT from the DSNHDECP module of the subsystem for BSDS and DB2 log input.
When Log Master obtains input from a logical log, it uses the same decimal point character that was in use when the logical log was created.
Directs Log Master to generate a SET CURRENT SQLID statement and insert it at the beginning of the generated SQL. When you execute the generated SQL, DB2 runs it under the authority granted to the authorization ID represented by sqlid.
Specify a valid authorization ID that has the appropriate authority in your environment.
Directs Log Master to use the specified characters as the SQL concatenation operator in output SQL statements. Log Master uses a concatenation operator to generate SQL statements that contain any string constants that are longer than the maximum length supported by the current version of DB2 (for example, 255 or 32,704 characters).
|INCLUDE or EXCLUDE INSERT COLUMN NAMES|
Directs Log Master to include or exclude column names in SQL INSERT statements. The default value is INCLUDE INSERT COLUMN NAMES.
By excluding column names and including only the values, SQL files are smaller.
The Column include/exclude definition enables you to control the information in your SQL file based on table columns. For more information, see LOGSCAN column include/exclude definition.
This section contains the following topics: