X hits on this document

1034 views

0 shares

0 downloads

0 comments

26 / 236

Product Overview

Collector

OMEGAMON IIs standard installation procedure sets the EPILOG collector to start automatically when the OMEGAMON II address space starts. You can also start the EPILOG collector separately with the interface procedure KEICOLmp, which issues the following interface command:

START EPILOG,OPTION=KEIOPTmp Alternatively, you can issue the interface command START EPILOG yourself.

For a specific IMS system, only one collector can be active at a time. The collector gathers resource utilization data and bottleneck data by PSB group.

By default, at the end of each resource measurement facility (RMF) collection interval (typically 15 minutes to one hour), the collector writes the data that it collected during the interval to SMF and the EPILOG datastore (EDS). You can specify another collection interval as described in Options for the EPILOG Collectoron page 43.

EPILOG does not duplicate information collected by either RMF or EPILOG for IMS However, if you do not synchronize on the RMF interval, certain device statistics will not be available.

You can specify that EPILOG write all the collected data to SMF. We recommend that you turn on this option so you do not have to make backup copies of the EPILOG datastore If needed, you can use EDS utilities to recreate the EDS from SMF records.

Reporter

You can use the reporter for interactive inquiry or to generate batch reports. Powerful yet simple commands allow you to request information for a range of times and workloads. These commands represent not so much a group of canned reports as a tool kit for answering questions. Among other things, you can request data for specific time periods, combine and average collection intervals, analyze periods with exceptional conditions, and customize report formats. For example, you can use the reporter to:

review resource usage statistics associated with each degradation reason for that period

identify the worst bottlenecks during periods of high system use

report periods where thread processing time was delayed because of long running batch message processing (BMP) applications

display the average bottleneck profile for threads in a PSB group during the past month

display the bottleneck profile for a PSB group before and after a real storage upgrade was implemented

The EPILOG reporter, operating as a batch job, produces reports equivalent to those run under TSO. The reporter includes a set of standard reports which provide the information you need to improve user service. You can produce

26

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

Document info
Document views1034
Page views1034
Page last viewedSun Dec 11 10:05:18 UTC 2016
Pages236
Paragraphs8116
Words69808

Comments