57 lines
3.9 KiB
HTML
57 lines
3.9 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="Change cluster resource services settings" />
|
|
<meta name="abstract" content="The default values affecting message timeout and retry are set to account for most typical installations. However, it is possible to change these values to more closely match your communications environment." />
|
|
<meta name="description" content="The default values affecting message timeout and retry are set to account for most typical installations. However, it is possible to change these values to more closely match your communications environment." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsevents.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsheartbeatmonitor.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="rzaigmanagechangecrsssettings" />
|
|
<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>Change cluster resource services settings</title>
|
|
</head>
|
|
<body id="rzaigmanagechangecrsssettings"><a name="rzaigmanagechangecrsssettings"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Change cluster resource services settings</h1>
|
|
<div><p>The default values affecting message timeout and retry are set
|
|
to account for most typical installations. However, it is possible to change
|
|
these values to more closely match your communications environment.</p>
|
|
<p>The values can be adjusted in one of these ways:</p>
|
|
<ul><li>Set a general performance level that matches your environment</li>
|
|
<li>Set values for specific message tuning parameters for more specific adjustment.</li>
|
|
</ul>
|
|
<p>In the first method above, the message traffic is adjusted to one of three
|
|
communications levels. The normal level is the default and is described in
|
|
detail in Heartbeat monitoring.</p>
|
|
<p>The second method should normally be done only under the advisement of
|
|
an expert.</p>
|
|
<p>The <a href="../apis/clcntchgcrs.htm"><span class="apiname">Change
|
|
Cluster Resource Services (QcstChgClusterResourceServices)</span> API</a> describes
|
|
details on both methods.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <img src="./delta.gif" alt="Start of change" /><a href="rzaigconceptsevents.htm" title="Within a cluster several types events, actions, and services can occur.">Cluster events</a><img src="./deltaend.gif" alt="End of change" /></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaigconceptsheartbeatmonitor.htm" title="Heartbeat monitoring is a cluster resource services function that ensures that each node is active by sending a signal from every node in the cluster to every other node in the cluster to convey that they are still active.">Heartbeat monitoring</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |