70 lines
4.8 KiB
HTML
70 lines
4.8 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="The QYRMJOBSEL job" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaihcolsvsmonrelshp.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="rzaihqyrmjobsel" />
|
||
|
|
<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>The QYRMJOBSEL job</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaihqyrmjobsel"><a name="rzaihqyrmjobsel"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">The QYRMJOBSEL job</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p></p>
|
||
|
|
<p>The QYRMJOBSEL uses the information that is specified in the General page
|
||
|
|
of the Job Monitor definition (<span class="menucascade"><span class="uicontrol">Management Central</span> > <span class="uicontrol">Monitors</span> > <span class="uicontrol">Job</span> > <span class="uicontrol">Right-click
|
||
|
|
a monitor and click Proprieties</span></span>) with Collection
|
||
|
|
Services data (QYPSPFRCOL) to determine what specific jobs need to be monitored.
|
||
|
|
These jobs are then shown in the bottom half of the Job Monitor status window. </p>
|
||
|
|
<p> Even if only one job is running, QYRMJOBSEL still examines all of the
|
||
|
|
active job data from Collection Services to determine how many jobs are running,
|
||
|
|
if new instances have started or if instances that were running during the
|
||
|
|
previous interval have ended. The QYRMJOBSEL job does this analysis at each
|
||
|
|
interval. Thus, the amount of CPU resource that is needed for QYRMJOBSEL to
|
||
|
|
complete this function is determined by how many active jobs are on the system.
|
||
|
|
The more active jobs, the more jobs for QYRMJOBSEL to analyze. </p>
|
||
|
|
<p>Additionally, the QYRMJOBSEL job registers with Collection Services the
|
||
|
|
needed probe data, but it cannot provide the notification interval. So it
|
||
|
|
is always at the lowest interval at which Collection Services is running.
|
||
|
|
Thus, a smaller collection interval means that this processing is performed
|
||
|
|
more frequently. </p>
|
||
|
|
<p>For example, suppose the job monitor server starts a job monitor at 5 minute
|
||
|
|
collection intervals. Then another monitor that is using Collection Services
|
||
|
|
starts, but uses a smaller interval. As a result, the QYRMJOBSEL receives
|
||
|
|
the data at the smaller or more frequent interval. If the smaller interval
|
||
|
|
is 30 seconds, there will be a 10 time increase in the amount of data QYRMJOBSEL
|
||
|
|
processes, thereby increasing the need for CPU resources. </p>
|
||
|
|
<p>When the job monitor is stopped, its associated QYRMJOBSEL job receives
|
||
|
|
an ENDJOB immediate and terminates with a CPC1125 Completion 50 severity.
|
||
|
|
This is the normal way that the QYRMJOBSEL is removed from the system.</p>
|
||
|
|
<div class="p"><div class="note"><span class="notetitle">Note:</span> For QYRMJOBSEL to work properly, the Java™ time zone must be correctly set. This
|
||
|
|
is done by setting the QTIMZON system value.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaihcolsvsmonrelshp.htm" title="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.">Job monitors and Collection Services</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|