93 lines
6.3 KiB
HTML
93 lines
6.3 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="QZRCSRVS jobs and their impact on performance" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<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="rzaihwhymonitorimpacts" />
|
||
|
|
<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>QZRCSRVS jobs and their impact on performance</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaihwhymonitorimpacts"><a name="rzaihwhymonitorimpacts"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">QZRCSRVS jobs and their impact on performance</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>QZRCSRVS jobs are not Management Central jobs. They are i5/OS™ TCP Remote
|
||
|
|
Command Server jobs that the Management Central Java™ server uses for calling commands and
|
||
|
|
APIs. In order to process the API calls for the Job Log Messages and Job Status
|
||
|
|
metrics in a timely fashion within the job monitor's interval length, the
|
||
|
|
APIs are called for each job concurrently at interval time.</p>
|
||
|
|
<p>When both metrics are specified on the same monitor, two QZRCSRVS jobs
|
||
|
|
are started for each job. For example, if 5 jobs are monitored for Job Log
|
||
|
|
Messages, 5 QZRCSRVS jobs are started to support the monitor. If 5 jobs are
|
||
|
|
monitored for Job Log Messages and Job Status, then 10 QZRCSRVS jobs are started.</p>
|
||
|
|
<p>Thus, it is recommended that for standard systems, when you are using the
|
||
|
|
Job Log Message and Job Status metrics, you limit the number of jobs monitored
|
||
|
|
on a small system to 40 jobs or less. (With larger systems more jobs may be
|
||
|
|
monitored. However, you should have a clear understanding of the resources
|
||
|
|
that are used when monitoring more jobs and determine the affordable number
|
||
|
|
to monitor. ) Also, severely limit using these two metrics for monitoring
|
||
|
|
subsystems, as doing so can cause a large number of QZRCSRVS jobs to run.
|
||
|
|
(A job monitor that uses just the other metrics and does not use Job Status
|
||
|
|
or Job Log Message, does not use QZRCSRVS jobs.)</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Tuning QZRCSRVS jobs</h4><p> For jobs that pass work to
|
||
|
|
the QZRCSRVS jobs, the subsystem that is specified on the QWTPCPUT API determines
|
||
|
|
where the QZRCSRVS jobs run. QWTPCPUT is called during the processing of the
|
||
|
|
QYSMPUT API. This API retrieves the subsystem information from the QUSRSYS/QYSMSVRE
|
||
|
|
*USRIDX object and uses it on the QWTPCPUT call. As shipped, QZRCSRVS jobs
|
||
|
|
are prestart jobs that run in the QUSRWRK subsystem and this is where the
|
||
|
|
connections are routed. </p>
|
||
|
|
<p>If you end the prestart jobs in QUSRWRK with
|
||
|
|
the ENDPJ command, then the QZRCSRVS jobs start as batch-immediate jobs in
|
||
|
|
the QSYSWRK subsystem whenever a connection is requested. No jobs start in
|
||
|
|
advance of the connection. </p>
|
||
|
|
<p>You can configure your system so that prestart
|
||
|
|
jobs can be run from any subsystem. You can also configure your system to
|
||
|
|
prevent batch-immediate jobs from being used at all. If the Job Monitor server
|
||
|
|
jobs are calling Java Toolbox functions to pass work to QZRCSRVS, then
|
||
|
|
they are using the QYSMPUT API, and the work should run in whichever subsystem
|
||
|
|
is stored in the user index. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">QZRCSRVS cleanup</h4><p>A cleanup thread runs once an hour
|
||
|
|
to determine whether a QZRCSRVS job is still being used by a Job Monitor.
|
||
|
|
It determines if the job was used at least twice within the maximum job monitor
|
||
|
|
interval length. If the job is not used during the previous two hours, it
|
||
|
|
is ended. Java time stamps are used for this comparison, so it
|
||
|
|
is imperative that the time zone value used by Java is correct (system value
|
||
|
|
QTIMZON).</p>
|
||
|
|
<div class="p">QZRCSRVS jobs are automatically removed two hours
|
||
|
|
after the job it supports ends. Likewise QZRCSRVS jobs will end if the Job
|
||
|
|
Monitor that created them stops, or if Management Central ends.<div class="note"><span class="notetitle">Note:</span> Since
|
||
|
|
the Management Central Job Monitor monitors active jobs, you might see messages
|
||
|
|
like "Internal job identifier no longer valid" in the QZRCSRVS job. This normally
|
||
|
|
happens when a monitored job with Job Log Messages or the Job Status metric
|
||
|
|
ends while the monitor is running. </div>
|
||
|
|
</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>
|