ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahx_5.4.0.1/rzahxcollservscenario.htm

59 lines
5.7 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="System and job monitor interaction with Collection Services" />
<meta name="abstract" content="Collection services is both a valuable tool for performance analysis as a stand alone application and as a utility used by other applications for the collection of performance data." />
<meta name="description" content="Collection services is both a valuable tool for performance analysis as a stand alone application and as a utility used by other applications for the collection of performance data." />
<meta name="DC.Relation" scheme="URI" content="rzahxcollectdatacs.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzahxcollservscenario" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>System and job monitor interaction with Collection Services</title>
</head>
<body id="rzahxcollservscenario"><a name="rzahxcollservscenario"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">System and job monitor interaction with Collection Services</h1>
<div><p>Collection services is both a valuable tool for performance analysis as a stand alone application and as a utility used by other applications for the collection of performance data.</p>
<p>Sometimes, performance analysis causes confusion when trying to determine which application is responsible for activity you may see on your system. One easy rule to remember for this issue is that even
if it looks like those other applications are busy, there is one and only one data collection occurring on the system at any given time.</p>
<p>The following scenarios explain the different combinations between system monitors and job monitors and Collection Services and what Collection Services displays.</p>
<div class="section"><h4 class="sectiontitle">Collection Services is collecting data using the default values</h4><p>In this scenario, there are no system monitors or job monitors active on the system. When viewing the Collection
Services properties page and the *MGTCOL object properties view, you see something similar to the following:</p>
<br /><img src="rzahx509.gif" alt="Collection Services collecting data by using default values" /><br /></div>
<div class="section"><h4 class="sectiontitle">Both Collection Services and a system monitor are started</h4><p>This scenario shows that Collection Services had already started at some point, and later someone started a system monitor
to collect CPU Utilization (Average) metric data at 30-second intervals. Notice in the *MGTCOL object properties view that the collection interval for System Level Data, Job MI Data, and Job
OS Data categories changed from 15 minutes to 30 seconds. This demonstrates that the same *MGTCOL object is being used, and only those categories necessary to calculate information for a given metric were
changed to collect at the new interval.</p>
<br /><img src="rzahx507.gif" alt="Collection Services and a system monitor are running and collecting data." /><br /></div>
<div class="section"><h4 class="sectiontitle">Collection Services stopped and system monitor remains started</h4><p>In this scenario, Collection Services was stopped and the system monitor remains started and continues to collect
data necessary to calculate the graph metrics.</p>
<p>Observe the following:</p>
<ul><li>The Collection Services properties page shows a status of <span class="uicontrol">System collection stopped. Collecting for applications only</span>.</li>
<li>The *MGTCOL object properties page shows that data collection has ended for all categories except for those necessary to calculate the graph metric data.</li>
<li>The Collection Services list view shows the *MGTCOL object with a status of <span class="uicontrol">Collecting...</span>. This might be confusing; therefore, to get the status of Collection Services, look at
the Collection Services Properties page.</li>
</ul>
<br /><img src="rzahx508.gif" alt="Collection Services has stopped, but the system monitor remains started." /><br /></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxcollectdatacs.htm" title="Use Collection Services to collect performance data for later analysis by the Performance Tools for iSeries licensed program or other performance report applications, iSeries Navigator monitors, and the graph history function. (If you prefer viewing real-time performance data, system monitors provide an easy-to-use graphical interface for monitoring system performance.)">Collection Services</a></div>
</div>
</div>
</body>
</html>