LOGSCAN command file definition
When you generate a command file, Log Master can generate DDL output or a Catalog Activity report, or update the Repository, but it cannot generate other forms of output in the same log scan (such as other reports or SQL). To generate other forms of output in the same job, include an additional log scan step.
Directs Log Master to create BIND commands used for migration, or for replicating the BIND, REBIND, or FREE command that was originally executed. For example, if the original command contains a BIND PLAN statement, the MIGRATE command contains the same command statement.
Directs Log Master to create UNDO commands, reversing the effect of the command that was originally executed. For example, if the original command contains a FREE PACKAGE statement, the UNDO DDL contains a corresponding BIND PACKAGE command statement.
A procedure, function, or trigger package is implicitly created or dropped through DB2 DDL CREATE, DROP PROCEDURE, FUNCTION, or TRIGGER statements. These types of packages cannot be created or dropped with BIND or FREE commands.
(optional) Directs Log Master to embed comments in the generated command file. These comments describe unit of recovery identifier (URID) information along with other information related to the database structures. The comments are not executable command statements, but they contain useful information.