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 Ops Monitor for IP 3.9.

Discrepancies in time and duration fields

Discrepancies may occur in the Time and Duration fields on the window information line because these fields reflect the actual data that is displayed, which may not be the same as the data you requested with the TIME command.

Discrepancies occur because data is not always available for the intervals that you request. This might happen because the product address space (PAS) shut down in the middle of a recording interval, creating gaps in the data that is recorded to the historical data set. The data that appears on the window information line represents the data that is actually displayed.

Example

At 9:00 A.M. you want to look at JOBRSPZ to determine the highest response times that occurred between 5:00 A.M. and 8:00 A.M. You display the JOBRSPZ view and type the following command:

Time command

TIME * 8:00 3h

Time command example code

>W1 =JOBRSPZ========SJSC=====*======03FEB2010==8:00=180M====MVIP========59======

The last interval in the duration that you requested is 8:00; the 3-hour period that you are interested in is equivalent to 180 minutes.

The resulting window information line may actually look like this example:

Time command example code result

>W1 =JOBRSPZ========SJSC=====*======03FEB2010==7:15=115M====MVIP========59======

In our example, 7:15 A.M. was the last interval within the time frame for which data was recorded. No data was recorded at 7:30 A.M., 7:45 A.M., or 8:00 A.M., so the window information shows 7:15 A.M. instead of 8:00 A.M.

Other gaps may have occurred in the record between 5:15 A.M. and 7:15 A.M. If so, the gaps were too short to significantly affect the data that is displayed. BMC AMI Ops makes adjustments so that you get the most accurate possible perspective of the data that is actually displayed in the view.

Note

The time field always contains the end of the last interval for which data was available, and the number of intervals for which data was actually available (normalized over the time frame that you requested).

Related topic

Using-the-TIME-command


 

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