Specify whether to ignore any SQL statements within comments enclosed by /* */, // and –- found in the source code. By default, the scanning algorithm will search for any SQL statements contained in comments.

Specify whether to ignore any VALUES command, such as: VALUES CURRENT SCHEMA.

Specify to search for SELECT, INSERT, UPDATE or DELETE as a whole word; the keyword must be preceded and followed by a space. The SQL Scanner therefore will not find the word INSERT in something like PROCEDUREINSERT and attempt to build a SQL statement from it.

Specify whether the scanning algorithm will automatically create temp table during scanning when a declare temp table statement is scanned. This option will not override any temp tables created in User-Defined Temp Tables window.

Specify whether Scanner Temp Table will include data. If this option is selected, the SQL Scanner will automatically execute any INSERT, DELETE, and UPDATE SQL statement that modifies Scanner Temp Table.

Note: Selecting the Include data option may affect the total scanning time.

Specify whether to override a previous Scanner Temp Table if it scans another declare temp table statement using the same table name. This option will not override any temp tables created in User-Defined Temp Tables window.

If selected, a previous User-Defined Temp Table is overwritten if the SQL Scanner finds another create temporary table statement using the same table name. This option will not override any temporary tables created in the SQL Scanner.

Specify the user temporary table space used to create the temp table for the Trigger Conversion. If no user temporary table space is specified then the database default user temporary table space will be used.

Note: To create or modify temporary tables in the SQL Scanner the logon user needs the following privileges:

• Connection to DB2 LUW 7 or above

• USE privilege on the USER TEMPORARY table space or SYSADM or DBADM authority

When a file is scanned, the SQL Scanner skips the specified number of characters at the beginning of every line.

If the text of the SQL statement is on more than one physical line and there is a continuation character at the end of each physical line of the SQL text, then specify what the continuation character is so that it will be skipped. If this character is not skipped, it may cause the SQL Scanner to miss part of the SQL statement. Three options are included: <Do not use>, / (forward slash character), and _ (underscore character). In addition, you may add your own character. This character will be saved in the box as long as it is the selected character. Once you make another selection, your own character will not be remembered.