71 lines
4.5 KiB
HTML
71 lines
4.5 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="Advanced trace function: Watch support" />
|
||
|
|
<meta name="abstract" content="You can find out how to maximize the benefits of the trace functions." />
|
||
|
|
<meta name="description" content="You can find out how to maximize the benefits of the trace functions." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakutoolstrc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuwatchscenarios.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuwatchparam.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuwatchexitpgmandexample.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuwatchtraces.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1997, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1997, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="advtrc" />
|
||
|
|
<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>Advanced trace function: Watch support</title>
|
||
|
|
</head>
|
||
|
|
<body id="advtrc"><a name="advtrc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Advanced trace function: Watch support</h1>
|
||
|
|
<div><p>You can find out how to maximize the benefits of the trace functions.</p>
|
||
|
|
<p>Watch support enhances the trace functions in <span> i5/OS™</span> by
|
||
|
|
automatically monitoring and ending traces when certain predetermined criteria
|
||
|
|
are met. This prevents the loss of valuable trace data and reduces the amount
|
||
|
|
of time you need to spend monitoring traces.</p>
|
||
|
|
<p>For example, when you start a trace on a busy server, it is possible for
|
||
|
|
large amounts of trace data to be collected very quickly so that the trace
|
||
|
|
buffer wraps, overlaying previous trace data. By the time you can manually
|
||
|
|
determine the problem has occurred and stop the trace, the previous trace
|
||
|
|
data needed to solve the problem has been overlaid. The result is lost trace
|
||
|
|
data. The watch function solves this problem by allowing you to set certain
|
||
|
|
watch criteria using the watch parameters. When a failure occurs, there is
|
||
|
|
often a message or a Licensed Internal Code log that is generated at the time
|
||
|
|
of the failure. You can specify which messages or Licensed Internal Code logs
|
||
|
|
should be monitored during the trace collection, and when they occur the server
|
||
|
|
automatically ends the trace.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakuwatchscenarios.htm">Scenarios: Use watch support with traces</a></strong><br />
|
||
|
|
You can learn how to use the watch function when you perform a trace from these scenarios.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakuwatchparam.htm">Watch parameters</a></strong><br />
|
||
|
|
Here are the parameters that you can use to specify watch criteria for watch support.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakuwatchexitpgmandexample.htm">Example: Watch exit program</a></strong><br />
|
||
|
|
<span>You can specify exit programs in the trace
|
||
|
|
program parameter to extend the capability of the watch function. </span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakuwatchtraces.htm">Traces that use watch support</a></strong><br />
|
||
|
|
<span>You can use watch support with these trace
|
||
|
|
functions.</span></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakutoolstrc.htm" title="You can use various trace tools to solve problems with your TCP/IP connectivity.">Tools for tracing data and jobs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|