ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaih_5.4.0.1/rzahxmonsystemexample.htm

131 lines
8.4 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="topic" />
<meta name="DC.Title" content="Scenario: System monitor" />
<meta name="abstract" content="See an example system monitor that alerts you if the CPU utilization gets too high and temporarily holds any lower priority jobs until more resources become available." />
<meta name="description" content="See an example system monitor that alerts you if the CPU utilization gets too high and temporarily holds any lower priority jobs until more resources become available." />
<meta name="DC.Relation" scheme="URI" content="rzahxmonexample.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="rzahxmonsystemexample" />
<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>Scenario: System monitor</title>
</head>
<body id="rzahxmonsystemexample"><a name="rzahxmonsystemexample"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Scenario: System monitor</h1>
<div><p>See an example system monitor that alerts you if the CPU utilization
gets too high and temporarily holds any lower priority jobs until more resources
become available.</p>
<div class="section" id="rzahxmonsystemexample__situation"><a name="rzahxmonsystemexample__situation"><!-- --></a><h4 class="sectionscenariobar">Situation</h4><p>As
a system administrator, you need to ensure that the <span class="keyword">iSeries™</span> system
has enough resources to meet the current demands of your users and business
requirements. For your system, CPU utilization is a particularly important
concern. You would like the system to alert you if the CPU utilization gets
too high and to temporarily hold any lower priority jobs until more resources
become available.</p>
<p>To accomplish this, you can set up a system monitor
that sends you a message if CPU utilization exceeds 80%. Moreover, it can
also hold all the jobs in the QBATCH job queue until CPU utilization drops
to 60%, at which point the jobs are released, and normal operations resume.</p>
<p><strong>Configuration
example</strong></p>
<p>To set up a system monitor, you need to define what metrics
you want to track and what you want the monitor to do when the metrics reach
specified levels. To define a system monitor that accomplishes this goal,
complete the following steps:</p>
<ol><li>In <span class="keyword">iSeries Navigator</span>, expand <span class="menucascade"><span class="uicontrol">Management Central </span> &gt; <span class="uicontrol">Monitors</span></span>, right-click <span class="uicontrol">System Monitor</span>, and select <span class="uicontrol">New
Monitor...</span></li>
<li>On the <span class="uicontrol">General</span> page, enter a name and description
for this monitor.</li>
<li>Click the <span class="uicontrol">Metrics</span> tab, and enter the following
values: <ol type="a"><li>Select the <span class="uicontrol">CPU Utilization Basic (Average)</span>, from
the list of Available Metrics, and click <span class="uicontrol">Add</span>. CPU Utilization
Basic (Average) is now listed under Metrics to monitor, and the bottom portion
of the window displays the settings for this metric.</li>
<li>For <span class="uicontrol">Collection interval</span>, specify how often you
would like to collect this data. This will override the Collection Services
setting. For this example, specify <span class="uicontrol">30 seconds</span>.</li>
<li>To change the scale for the vertical axis of the monitor's graph for this
metric, change the <span class="uicontrol">Maximum graphing value</span>. To change
the scale for the horizontal axis of the graph for this metric, change the
value for <span class="uicontrol">Display time</span>.</li>
<li>Click the <span class="uicontrol">Threshold 1</span> tab for the metrics settings,
and enter the following values to send an inquiry message if the CPU Utilization
is greater than or equal to 80%: <ol type="i"><li>Select <span class="uicontrol">Enable threshold.</span></li>
<li>For the threshold trigger value, specify <span class="uicontrol">&gt;= 80</span> (greater
than or equal to 80 percent busy).</li>
<li>For <span class="uicontrol">Duration</span>, specify <span class="uicontrol">1</span> interval.</li>
<li>For the <span class="uicontrol"><span class="keyword">i5/OS™</span> command</span>,
specify the following: <pre>SNDMSG MSG('Warning,CPU...') TOUSR(*SYSOPR) MSGTYPE(*INQ)</pre>
</li>
<li>For the threshold reset value, specify <span class="uicontrol">&lt; 60</span> (less
than 60 percent busy). This will reset the monitor when CPU utilization falls
below 60%.</li>
</ol>
</li>
<li>Click the <span class="uicontrol">Threshold 2</span> tab, and enter the following
values to hold all the jobs in the QBATCH job queue when CPU utilization stays
above 80% for five collection intervals: <ol type="i"><li>Select <span class="uicontrol">Enable threshold</span>.</li>
<li>For the threshold trigger value, specify <span class="uicontrol">&gt;= 80</span> (greater
than or equal to 80 percent busy).</li>
<li>For <span class="uicontrol">Duration</span>, specify <span class="uicontrol">5</span> intervals.</li>
<li>For the <span class="uicontrol"><span class="keyword">i5/OS</span> command</span>,
specify the following: <pre>HLDJOBQ JOBQ(QBATCH)</pre>
</li>
<li>For the threshold reset value, specify <span class="uicontrol">&lt; 60</span> (less
than 60 percent busy). This will reset the monitor when CPU utilization falls
below 60%.</li>
<li>For <span class="uicontrol">Duration</span>, specify <span class="uicontrol">5</span> intervals.</li>
<li>For the <span class="uicontrol"><span class="keyword">i5/OS</span> command</span>,
specify the following: <pre>RLSJOBQ JOBQ(QBATCH)</pre>
<p>This
command releases the QBATCH job queue when CPU utilization stays below 60%
for 5 collection intervals.</p>
</li>
</ol>
</li>
</ol>
</li>
<li>Click the <span class="uicontrol">Actions</span> tab, and select <span class="uicontrol">Log
event</span> in both the <span class="uicontrol">Trigger</span> and <span class="uicontrol">Reset</span> columns.
This action creates an entry in the event log when the thresholds are triggered
and reset.</li>
<li>Click the <span class="uicontrol">Systems and groups</span> tab to specify the
systems and groups you want to monitor.</li>
<li>Click <span class="uicontrol">OK</span> to save the monitor.</li>
<li>From the list of system monitors, right-click the new monitor and select <span class="uicontrol">Start</span>.</li>
</ol>
<p><strong>Results</strong></p>
<p>The new monitor displays the CPU utilization,
with new data points being added every 30 seconds, according to the specified
collection interval. The monitor automatically carries out the specified threshold
actions, even if your PC is turned off, whenever CPU utilization reaches 80%.</p>
<div class="note"><span class="notetitle">Note:</span> This
monitor tracks only CPU utilization. However, you can include any number of
the available metrics in the same monitor, and each metric can have its own
threshold values and actions. You can also have several system monitors that
run at the same time.</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxmonexample.htm" title="Provides scenarios that show how you can use some of the different types of monitors to look at specific aspects of your system's performance.">Scenarios: iSeries Navigator monitors</a></div>
</div>
</div>
</body>
</html>