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 MainView Middleware Monitor 9.2.

Accounting for time-zone differences

The time stamps on monitored information are set by the MainView Middleware Monitor (MVMM) Services system. If the services are on several systems, the MVMMHistory Service sets the time stamp.

If any of your MVMMcomponents (services, agents, or clients) exist in different time zones, the differences can cause reports and charts to appear inaccurate.

Related topics

Defining-data-rules-and-templates 

Using

You can choose from the following two options to resolve this problem:

  • Set all your MVMMsystem clocks to one standard time zone, such as GMT.
  • Add the time zone difference as a fixed value in the report. Although the report is not actually current, it does have the values adjusted for time. Remember that if your agents are in different time zones than your services, you might need to perform more than one calculation.

 

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