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.

Log Master high-level syntax

To define a Log Master job, enter job-level statements (for example, an OPTION statement), and then specify step-level statements (for example, a LOGSCAN statement).

Job-level statements define conditions for the entire Log Master job. You can enter each statement only once for each job.

Step-level statements define one step within a Log Master job. Enter as many LOGSCAN, LOGMARK, or EXECSQL statements as you need. You can enter only one DROPRECOVERY statement for each job.

Place Log Master syntax in the location specified by the SYSIN DD statement (either in a data set or in-stream in the JCL). For more information about entering comments within your SYSIN syntax, see Specifying Log Master syntax.

The following figure shows the overall, high-level syntax for Log Master:



    OptionDescription

    WORKID

    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.

    OPTION

    Specifies options that are set globally for use in a Log Masterjob 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.

    LOGOPTS

    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.

    STOREOPTS

    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.

    LOBOPTS

    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.

    XMLOPTS

    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.

    SORTOPTS

    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.

    IMAGECOPY

    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.

    LOGSCAN

    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.

    LOGMARK

    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.

    LOGMARK DELETE (PTF BQU2282 applied)

    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).

    EXECSQL

    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.

    DROPRECOVERY

    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 Software Next Generation Technology Recover for DB2 for z/OS 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.

    REPOS DELETE (PTF BQU2282 applied)

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

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

    Comments