89 lines
5.2 KiB
HTML
89 lines
5.2 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="Alerts" />
|
|
<meta name="abstract" content="An alert is a message that has several benefits." />
|
|
<meta name="description" content="An alert is a message that has several benefits." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzahbmsy.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzahbala.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzahbala.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="rzahbalr" />
|
|
<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>Alerts</title>
|
|
</head>
|
|
<body id="rzahbalr"><a name="rzahbalr"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Alerts</h1>
|
|
<div><p>An alert is a message that has several benefits.</p>
|
|
<div class="section"><p>An alert is automatically sent from any system in the network
|
|
to the system that is designated to manage problems.</p>
|
|
<p>An alert provides
|
|
a quick, initial assessment of a problem and gives the network operator guidance
|
|
on corrective actions. For those problems that a network operator cannot correct,
|
|
the alert provides information that a specialist can use to isolate the source
|
|
of the problem.</p>
|
|
<p>Alerts inform the operator of problems with hardware
|
|
resources, such as local devices or controllers, communications lines, or
|
|
remote controllers or devices. Alerts can also notify the operator of software
|
|
errors that are detected by the system or application programs. If the system
|
|
is part of a communications network, alerts can be created and sent through
|
|
the network to the problem-managing system.</p>
|
|
<div class="p">You can use alerts to perform
|
|
the following management activities: <ul><li>Monitor systems and devices that operate unattended.</li>
|
|
<li>Manage situations in which the local operator does not know how to handle
|
|
the problem.</li>
|
|
<li>Maintain control of system resources and expense.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Benefits of alerts</h4><p>Use alerts to manage your network
|
|
and systems more effectively.</p>
|
|
<div class="p">The following situations are examples
|
|
of when you might use alerts. <ul><li>To reduce your system and network costs. Because the system automatically
|
|
controls the capabilities of alerts, you can automate common responses to
|
|
system problems without operator intervention.</li>
|
|
<li>To monitor your network status. Alerts provide information about specific
|
|
network problems that can help you track and monitor your system.</li>
|
|
<li>To monitor unattended remote systems. Alerts can notify a central site
|
|
about a problem on an unattended system.</li>
|
|
<li>To have all your technical people at one location. When you use alerts,
|
|
you can staff all of your technical support at one central site.</li>
|
|
<li>To make your own applications have the same error-reporting capabilities
|
|
as the system functions. Alerts give you the capability to define your own
|
|
alertable messages.</li>
|
|
<li>To provide the ability to choose where your technical support is located.
|
|
When you use alerts, you can select which of your systems receive central
|
|
technical support.</li>
|
|
<li>When you manage a network with either homogeneous or heterogeneous systems.
|
|
Because alerts are designed to be independent of the system architecture,
|
|
alerts from one system are readable on other systems.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahbmsy.htm" title="There are a variety of system and server messages available to assist you, ranging from error messages, to printer messages, to alerts.">Types of messages</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzahbala.htm" title="You can log and display alerts that were either locally created on your system or that were received from other systems in the network. Your system does not need to be actively processing alerts to work with alerts. You can see all the alerts that are logged in the alert database.">Display alerts</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |