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.

Maintaining the Repository

Log Master uses the tables in the Repository in the same way that an application program uses any group of Db2 tables.

To maintain the Repository, perform the following standard practices of recoverable Db2 operation.

Regular backups

Routinely create image copies of the Repository table spaces. Use a Db2 Modify utility regularly.

A sample job that backs up the Repository is included in the BMC AMI Copy for Db2  sample library downloaded from the installation tape. The name of the member is HLQ.DBSAMP(ALP$BKUP). The HLQ value represents a high-level qualifier that your environment assigns during installation. This sample job uses BMC AMI Copy for Db2 .

Regular maintenance of Repository tables

Routinely run a Db2 Runstats utility on the Repository table spaces and indexes. Use the information reported by this utility to determine when to run a Db2 Reorg utility to reorganize table spaces and associated indexes. If you fail to maintain Repository table spaces and indexes, the performance of the product might degrade over time.

Reduce Repository size when required

The product stores information in the Repository each time it runs a job. Over time, the Repository grows in size. To reduce the size of the Repository, use one of the following methods:

  • Reduce the size of Old Objects (ALPOLDO) or Open Unit of Recovery (ALPURID) tables of the Repository. With PTF BQU1717 applied, you can also reduce the size of SYSCOPY (ALPSYSCP) or history tables of the Repository.

    (PTF BQU2282 applied) To reduce the size of one or more of these tables, use the REPOS DELETE statement. For more information, see REPOS DELETE statement.

    (PTF BQU2282 not applied) To reduce the size of one or more of these tables, use the REPOS DELETE keyword of the LOGSCAN statement. For more information, see REPOS DELETE.

    You can also use options on the Main Menu of the product’s online interface to generate JCL that deletes information from these tables, or to delete or display information interactively.

  • Reduce the size of Open Unit of Recovery (ALPURID) and Work ID Log Scan History (ALPWLSH) tables of the Repository.

    The RESET PURGE keywords of the LOGSCAN statement reduce the size of both the ALPURID and ALPWLSH tables. However, these keywords operate on only one combination of user ID, work ID, and ongoing handle ID at a time. 

  • (PTF BQU2282 applied) Reduce the size of the LOGMARK table (ALPMARK) by using the LOGMARK DELETE statement. For more information, see LOGMARK DELETE.

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