69 lines
5.2 KiB
HTML
69 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="Use effective systems management practices" />
|
|
<meta name="abstract" content="One of the simplest ways to prevent unplanned outages is to ensure that you are doing everything you can to keep your system running smoothly. This includes performing basic preventive maintenance and systems management tasks that help your system perform at its peak." />
|
|
<meta name="description" content="One of the simplest ways to prevent unplanned outages is to ensure that you are doing everything you can to keep your system running smoothly. This includes performing basic preventive maintenance and systems management tasks that help your system perform at its peak." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwprevent_unplanned.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="rzalwsysman" />
|
|
<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>Use effective systems management practices</title>
|
|
</head>
|
|
<body id="rzalwsysman"><a name="rzalwsysman"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Use effective systems management practices</h1>
|
|
<div><p>One of the simplest ways to prevent unplanned outages is to ensure
|
|
that you are doing everything you can to keep your system running smoothly.
|
|
This includes performing basic preventive maintenance and systems management
|
|
tasks that help your system perform at its peak.</p>
|
|
<p> Many of these systems management tasks can be automated, which helps you
|
|
prevent failures that may occur because of human error or an oversight.</p>
|
|
<p>One way you can help ensure the availability of your system is to monitor
|
|
its performance and react promptly to any problems that you encounter. You
|
|
can use the Collection Services and monitors functions in Management Central
|
|
to actively monitor and track the performance of your server. You can be notified
|
|
of any problems that jeopardize the availability of your system in time to
|
|
react and prevent an unplanned outage. For more information on how to plan
|
|
for and manage the performance of your server, see <a href="../rzahx/rzahx1.htm">Performance</a>.</p>
|
|
<p>Fixes are also an important systems management component that can help
|
|
you keep your system available. When problems are discovered in iSeries™ programs, IBM<sup>®</sup> issues
|
|
a <span class="uicontrol">fix</span> (also known as a PTF, or program temporary fix)
|
|
to correct the problem. You need to be aware of fixes and install them on
|
|
your system to ensure that your system is operating at its optimal level.
|
|
You should create a fix management strategy and make checking for and applying
|
|
fixes part of the routine maintenance for your server. For more information
|
|
on how to obtain and apply fixes, refer to <a href="../rzam8/rzam8fix1.htm">Use
|
|
software fixes</a>. For help in determining a strategy for preventive maintenance
|
|
based on your iSeries environment and applications, try the <a href="http://www-912.ibm.com/supporthome.nsf/document/22721158" target="_blank">Fix
|
|
Maintenance Advisor</a> <img src="www.gif" alt="Link outside Information Center" />. </p>
|
|
<p><img src="./delta.gif" alt="Start of change" />In addition, you should also develop a strategy of when and
|
|
how new applications will be added to your systems. Before adding a new application
|
|
or updating an existing application, ensure that any software, hardware, or
|
|
other dependencies are understood and in place. It is also important to plan
|
|
and test these new or changed applications before introducing them into a
|
|
production environment to help avoid potential outages or other unexpected
|
|
impacts.<img src="./deltaend.gif" alt="End of change" /></p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwprevent_unplanned.htm" title="One way to approach availability is to try to prevent unplanned outages. You can use these different methods to ensure that your system experiences as little unplanned downtime as possible.">Prevent unplanned outages</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |