Default language.

Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI LOBMaster for Db2 13.1.

Maintaining BMCUTIL and BMCSYNC tables

When a product abends, unwanted rows might remain in the BMCUTIL and BMCSYNC tables.

If you need to control expansion of these tables, use one of the following methods to delete rows:

  • Use the TERM restart parameter on the EXEC statement to delete rows from the BMCUTIL and BMCSYNC tables. Do not delete any rows for instances of utilities that are awaiting restart or executing.

  • Delete invalid rows in the BMCUTIL table. Do not delete any rows for instances of utilities that are awaiting restart or executing.Then use the following SQL statement to delete rows from the BMCSYNC table:

    DELETE
    FROM <creatorName>.CMN_BMCSYNC
    WHERE UTILID NOT IN
    SELECT UTILID FROM <creatorName>.CMN_BMCUTIL);

    Important

    The names of the BMCUTIL and BMCSYNC tables might have been changed at your site during installation.

Related topics

Concurrent-access-control

Overview-of-BMC-AMI-Utilities-concepts

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*