Log Master high-level syntax

Defines a unique identifier that Log Master uses to identify a unit of work. Create the work ID using the online interface, or define it explicitly in batch syntax. You can use only one WORKID statement for each Log Master job. For more information, see WORKID-statement.

Specifies options that are set globally for use in a Log Master job or job step. Use the OPTION statement to override installation options for one run of a Log Master job. If needed, use one OPTION statement for each Log Master job. Enter the statement at the beginning of the SYSIN syntax. For more information, see OPTION-statement.

Specifies options that control how Log Master processes Db2 log files. Use the LOGOPTS statement to override installation options for one run of a Log Master job. You can use only one LOGOPTS statement for each job. For more information, see LOGOPTS-statement.

Specifies options that control how Log Master handles internal memory or file structures called key stores. Use the STOREOPTS statement to override installation options for one run of a Log Master job. You can use only one STOREOPTS statement for each job. For more information, see STOREOPTS-statement.

Specifies options that control how Log Master maintains the VSAM files that it uses to store large object (LOB) data. Use the LOBOPTS statement to override installation options for one run of a Log Master job. You can use only one LOBOPTS statement for each job. For more information, see LOBOPTS-statement.

Specifies options that control how Log Master maintains the VSAM files that it uses to store XML data. Use the XMLOPTS statement to override installation options for one run of a Log Master job. You can use only one XMLOPTS statement for each job. For more information, see XMLOPTS-statement.

Specifies options that control how Log Master allocates memory for sort operations and sort work data sets. Use the SORTOPTS statement to override installation options for one run of a Log Master job. You can use only one SORTOPTS statement for each job. For more information, see SORTOPTS-statement.

Specifies exact locations for image copies that Log Master reads for input. Use this statement to specify input image copies that are not currently defined in the Db2 catalog. You can use only one IMAGECOPY statement for each Log Master job. For more information, see IMAGECOPY-statement.

Defines how Log Master reads Db2 log input, how it selects individual log records, and what forms of output it produces. Much of the product’s normal work is controlled using various keywords of the LOGSCAN statement. For more information about the high-level syntax of the LOGSCAN statement, see LOGSCAN-statement.

Directs Log Master to associate the current relative byte address or log record sequence number (RBA/LRSN) value with a name that you enter. You can use the log mark name in subsequent product syntax in place of the RBA/LSRN value. For more information, see LOGMARK-statement.

Directs Log Master to delete current, existing, and all generations of specified log mark entries from the Repository. For more information, see LOGMARK DELETE statement (PTF BQU2282 applied).

Directs Log Master to apply a given set of generated Structured Query Language (SQL) statements to a Db2 database. The SQL statements must be generated by Log Master. For more information, see EXECSQL-statement.

Directs Log Master to obtain information from the Db2 log and generate several forms of output, including a set of recovery syntax that can be passed to the BMC AMI Recover for Db2 product, or DSN1COPY. Using the syntax and information, the Recover utility can recover a Db2 object (for example, a table) that has been dropped from the Db2 catalog.

You can have only one DROPRECOVERY statement for each job. For more information, see DROPRECOVERY-statement.

Directs Log Master to delete rows from supported tables within the Repository. For more information, see REPOS-DELETE-statement.