93 lines
6.4 KiB
HTML
93 lines
6.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="concept" />
|
|
<meta name="DC.Title" content="Work with monitors" />
|
|
<meta name="abstract" content="Use Management Central monitors to check on your system performance, your jobs and servers, your message queues, and changes to selected files." />
|
|
<meta name="description" content="Use Management Central monitors to check on your system performance, your jobs and servers, your message queues, and changes to selected files." />
|
|
<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="rzaihmonitors" />
|
|
<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>Work with monitors</title>
|
|
</head>
|
|
<body id="rzaihmonitors"><a name="rzaihmonitors"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Work with monitors</h1>
|
|
<div><p>Use Management Central monitors to check on your system performance,
|
|
your jobs and servers, your message queues, and changes to selected files.</p>
|
|
<p>You can specify thresholds for various metrics on these monitors, and then
|
|
specify actions to be taken whenever a monitor detects that a threshold has
|
|
been triggered. For example, you can run an i5/OS™ command or start a program when the
|
|
threshold is triggered. For specific examples that describe how you can use
|
|
these monitors, see the related concept Scenarios: Performance.</p>
|
|
<p>You can use a <dfn class="term">system monitor</dfn> to see detailed graphs that monitor
|
|
the real-time performance of multiple iSeries™ servers. In the Graph History
|
|
window, you can see a graphical view of the metrics that have been collected
|
|
for an extended period of time by Collection Services. You can contrast this
|
|
data with the real-time data for the last hour shown in a System Monitor window.</p>
|
|
<p>You can monitor your jobs and servers with a <dfn class="term">job monitor</dfn>.
|
|
For example, you might want to monitor a job's CPU usage, job status, or job
|
|
log messages. For each of those metrics, you can specify a threshold and
|
|
actions to take when that threshold is triggered. For example, you could set
|
|
up your monitor to send a message to the system operator whenever the CPU
|
|
usage exceeds a certain threshold. In addition to the i5/OS commands, you can use the Advanced
|
|
Job Scheduler Send Distribution using JS (SNDDSTJS) command to notify someone
|
|
by e-mail when the threshold is exceeded, if the Advanced Job Scheduler licensed
|
|
program 5722-JS1 is installed on the endpoint system.</p>
|
|
<p>You can create a <dfn class="term">message monitor</dfn> to take action on a list
|
|
of messages that are important to you. For example, when the message monitor
|
|
detects CPI0953 (threshold of a disk pool is exceeded), you could specify
|
|
to run a command that would delete objects that you no longer need from the
|
|
disk pool.</p>
|
|
<div class="p">You can use a <dfn class="term">file monitor</dfn> to monitor for a specified text
|
|
string or for a specified size. Or, you can monitor for any modification to
|
|
one or more selected files. You can select one or more files to be monitored,
|
|
or you can select the History log option, which will monitor the i5/OS history
|
|
log (QHST).<div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />Integrated file system treats
|
|
QSYS physical files as directories, with the physical file members actually
|
|
treated as files.<img src="./deltaend.gif" alt="End of change" /></div>
|
|
</div>
|
|
<p>You can use a <dfn class="term">B2B activity monitor</dfn> to view a graph of active
|
|
transactions over time, and you can run commands automatically when thresholds
|
|
are triggered. You can search for and display a specific transaction as well
|
|
as view a bar graph of the detailed steps of that specific transaction.</p>
|
|
<p>You can start any Management Central monitor, and then turn to other tasks
|
|
on your server, in iSeries Navigator, or on your PC. You can choose
|
|
to be informed by an audible or visible alarm on your PC when important thresholds
|
|
are reached. The monitor will continue to run and perform any threshold commands
|
|
or actions you specified. Your monitor will run until you decide to stop it.
|
|
You can view all your monitors, as well as all your Management Central tasks,
|
|
remotely with iSeries Navigator
|
|
for Wireless.</p>
|
|
<p> In the Management Central properties, you can specify whether you want
|
|
the central system to automatically attempt to restart your monitors on endpoint
|
|
systems where they failed to start. If you select to have the system automatically
|
|
attempt to restart your monitors, you may also specify how long you want the
|
|
central system to keep trying to restart the monitors and how often you want
|
|
the system to try during that time period. For example, if you want the system
|
|
to try to restart monitors every five minutes for a period of 3 hours, you
|
|
would select <span class="uicontrol">Automatically restart monitors on failed systems,</span> and
|
|
then specify 180 minutes for <span class="uicontrol">How long to attempt restart</span> and
|
|
5 minutes for <span class="uicontrol">How often to attempt restart.</span></p>
|
|
<p>The steps to create and run a monitor are basically the same for whichever
|
|
type of monitor you choose to run. </p>
|
|
<p>Printable PDF of the section, <a href="rzaih.pdf" target="_blank"><strong>Work
|
|
with montiors</strong></a> (about 194 KB)</p>
|
|
</div>
|
|
|
|
</body>
|
|
</html> |