X hits on this document

1493 views

0 shares

0 downloads

0 comments

86 / 236

Miscellaneous Keywords

As convenient as this type of synchronization is, the RMF interval is not always the most desirable unit in which to obtain performance data. RMF data broken down to the RMF interval level may provide more detail than you really need.

To give more reporting versatility, EPILOG shows degradation and resource displays either in an RMF single-interval state or combined into multi-intervals. The keywords SINGLE and COMBINE are mutually exclusive; SINGLE is the default. COMBINEd records are kept in memory and are not part of the EDS.

For example, to generate a SUMMARY report for a 2-hour time span for a given number of days, you could use the command

DISPLAY SUMMARY SYS SDATE(01/02/97) STIME(10) EDATE(01/06/97) ETIME(12)

to generate the report shown in Figure 16 on page 86.

FIGURE 16. Single-Interval Summary Display

EPILOG/IMS 01/30/97 CMD==> **************************** +=========================== | System Wide | Period: 10:00 on 01/02/97 +--------------------------- | +--------------------------- |DATE__START_END___MAIN_REAS |01/02 10:00 10:15 DBP015 | | | | | | | 10:15 10:30 10:45 11:00 11:15 11:30 10:30 DBP015 10:45 DBP015 11:00 DBP018 11:15 DBP015 11:30 DBP015 11:45 DBP015 11:45 12:00 DBP015

|01/03 10:00 10:15 DBP015 | | | | | | | 10:15 10:30 10:45 11:00 11:15 11:30 10:30 DBP018 10:45 DBP015 11:00 DBP018 11:15 DBP018 11:30 DBP018 11:45 DBP018 11:45 12:00 DBP015 |01/04 . |. |. +===========================

10:55

Mode:

PAGE

******************* ===================

to 10:45 on 01/04/ ------------------- COMPETING STATES ------------------- ON______________%_| 27.4| 18.5| 29.6| 22.5| 20.2| 22.3| 18.0| 21.7| 26.8| 20.5| 16.6| 36.0| 41.3| 27.7| 37.4| 23.1| | | | ===================

-------->.

.

.

.

.

.

.

------> .

.

.

.

.

.

.

------> .

.

.

.

.

.

.

------> .

.

.

.

.

.

.

----->. .

.

.

.

.

.

.

------> .

.

.

.

.

.

.

-------->.

.

.

.

.

.

.

------>

.

.

.

.

.

.

.

----> .

.

.

.

.

.

.

.

******************

**************

==================

=============+

97

| |

------------------

-------------+

==================

=============+

------------------ 0__1__2__3__4__5__

  • --------

    >. . .

  • -----

    >.

.

.

.

---------=> .

.

---------===>

.

-------->. .

.

---------==>.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

  • ------

    >

.

.

.

. . . . . . . 6 _ _ 7 _ _ 8 _ . . | -------------+ _ 9 _ _ 0 | . . .| .| .| .| .| .| .| .| .| .| .| .| .| .| .| .| | | |

In its default single-interval form, this report is too long to be of general use. Instead, you can specify that the data be combined in larger intervals to see a

86

OMEGAMON II for DBCTL Historical Component (EPILOG) Reference Manual Version 510

Document info
Document views1493
Page views1493
Page last viewedMon Jan 23 05:38:08 UTC 2017
Pages236
Paragraphs8116
Words69808

Comments