X hits on this document

825 views

0 shares

0 downloads

0 comments

110 / 236

Using the System Navigator

FIGURE 30. Summary Report of IMS Bottlenecks

EPILOG/IMS CMD==>

01/02/97

17:39

Mode: PAGE

D1

LAST FRAME

*********************************************** +==============================================

******************************** ===============================+

| Group = | Period:

2 14:00 to 15:00 on 01/02/97

+---------------------------------------------- | COMPETING STATES +---------------------------------------------- |DATE__START_END___MAIN_REASON______________%_| |01/02 14:00 14:15 Oth DL/I Iwt 45.0| 61.5| 50.0| 21.1| |D | | 14:15 14:30 Oth DL/I Iwt 14:30 14:45 Oth DL/I Iwt 14:45 15:00 DBPE01

| | -------------------------------+

| -------------------------------+ 0__1__2__3__4__5__6__7__8__9__0| .| .| .| .| ---------====> . . ---------=========> . . . . . . . . . . . . ---------======> ------> . . . . .

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

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

A brief examination shows us that the worst problem was in the 14:15 to 14:30 PM time interval. At this point you might want to see a detailed display of bottlenecks during this interval. This could be done by entering the command:

DIS GRP(2) SDATE(1/02/97) STIME(1415) EDATE(1/02/97) ETIME(1430)

The system navigator simplifies this by allowing you to enter a D (for detailed bottleneck report) in the first column of the appropriate line as shown in Figure 30. This produces the detailed display shown in Figure 31:

FIGURE 31. DETAIL Report Example

EPILOG/IMS CMD==>

01/02/97

17:40

Mode: PAGE

D2

LAST FRAME

************************************************************ +===========================================================

******************* ==================+

| Period: | Group =

2

Symbolic Name = AUTO

14:15 to 14:30 on 01/02/97

Elap

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

| = 15:00 M I51A | ------------------+

|

DEGRADATION DATA

+----------------------------------------------------------- |Competing_State__________________%_|0___1___2___3___4___5___

|Using CPU | RIMS Waits | Using CPU in IMS

. . . . . . . . 15.4|------> (15.4)|------> 61.5|------------===========

| DBPE01 | Other DL/I IWAIT |Database I/O Waits

23.1|---------> . . . (23.1)|---------> . . . (61.5)|------------===========

.

.

.

.

=>

.

.

.

=>

.

.

.

.

.

.

.

.

.

.

.

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

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

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

At this point, you probably want to see some resource data for the IMS Waits bottleneck. Resource data is displayed by the resource panel or panels associated with the bottleneck reason. For example, to see the resources associated with IMS Waits, you could issue the following command:

110

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

Document info
Document views825
Page views825
Page last viewedSat Dec 03 00:49:56 UTC 2016
Pages236
Paragraphs8116
Words69808

Comments