73 lines
5.1 KiB
HTML
73 lines
5.1 KiB
HTML
<?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="Job monitors and Collection Services" />
|
|
<meta name="abstract" content="In order to avoid creating a negative performance impact on your system, you should understand how the different metrics in the job monitor uses Collection Services." />
|
|
<meta name="description" content="In order to avoid creating a negative performance impact on your system, you should understand how the different metrics in the job monitor uses Collection Services." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxmonparent.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaihqyrmjobsel.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaihwhymonitorimpacts.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahx/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="rzaihcolsvsmonrelshp" />
|
|
<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>Job monitors and Collection Services</title>
|
|
</head>
|
|
<body id="rzaihcolsvsmonrelshp"><a name="rzaihcolsvsmonrelshp"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Job monitors and Collection Services</h1>
|
|
<div><p>In order to avoid creating a negative performance impact on your
|
|
system, you should understand how the different metrics in the job monitor
|
|
uses Collection Services.</p>
|
|
<div class="p">The metrics that are available for a job monitor are:<ul><li>Job count</li>
|
|
<li>Job log message</li>
|
|
<li>Job status</li>
|
|
<li>Job numeric values</li>
|
|
<li>Summary numeric values</li>
|
|
</ul>
|
|
</div>
|
|
<p>The data for the job numeric and summary numeric values metrics come from
|
|
Collection Services. The overhead for obtaining this data is minimal and is
|
|
not affected by the number of specific jobs that are being monitored. It takes
|
|
two intervals of Collection services data before the first point or data metric
|
|
value can be calculated. For example, if the collection interval is 5 minutes
|
|
it will take more than 5 minutes before the first metric value is known. </p>
|
|
<p>The overhead for the job log message and job status metrics is much more
|
|
costly in terms of the CPU resources required to obtain the information. Additionally,
|
|
the number of jobs that are being monitored as well as the collection interval,
|
|
affect the amount of CPU overhead that is required. For example, a
|
|
job Monitor with a 5 minute interval will have six times the amount of overhead
|
|
process to complete versus if the collection interval was set to 30 minutes.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzaihqyrmjobsel.htm">The QYRMJOBSEL job</a></strong><br />
|
|
For every job monitor that runs, a QYRMJOBSEL job starts. This topic explains the purpose of the QYRMJOBSEL job and what causes it to end.</li>
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzaihwhymonitorimpacts.htm">QZRCSRVS jobs and their impact on performance</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
|
Job monitors connect to a QZRCSRVS job for each job that is being monitored for the Job Log Messages and the Job Status metrics. The more jobs that are being monitored for these metrics, the more QZRCSRVS jobs are used.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxmonparent.htm" title="Monitors display current information about the performance of your systems. Additionally, you can use them to carry out predefined actions when a specific event occurs. You can use the system, message, job, file, and B2B transaction monitors to display and monitor information about your systems. The system and job monitors use the performance data collected by Collection Services.">iSeries Navigator monitors</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../rzahx/rzahxcollectdatacs.htm">About Collection Services</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |