161 lines
9.2 KiB
HTML
161 lines
9.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="reference" />
|
|
<meta name="DC.Title" content="Trace TCP applications" />
|
|
<meta name="abstract" content="You can use the quality of service (QoS) trace to work with trace functions and to view the current trace buffer." />
|
|
<meta name="description" content="You can use the quality of service (QoS) trace to work with trace functions and to view the current trace buffer." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8troubleshooting.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8trace.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/trctcpapp.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="rzak8trace_tcp" />
|
|
<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>Trace TCP applications</title>
|
|
</head>
|
|
<body id="rzak8trace_tcp"><a name="rzak8trace_tcp"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Trace TCP applications</h1>
|
|
<div><p>You can use the quality of service (QoS) trace to
|
|
work with trace functions and to view the current trace buffer.</p>
|
|
<div class="section"><p>To run the trace on the server, type <samp class="codeph">TRCTCPAPP</samp> (Trace
|
|
TCP/IP Application command) from a command-line interface. </p>
|
|
<p>Here is
|
|
a sample of the trace selections to complete:</p>
|
|
<pre>TCP/IP application...........> *QOS
|
|
Trace option setting.........> *ON
|
|
Maximum storage for trace....> *APP
|
|
Trace full action............> *WRAP
|
|
Argument lists...............> 'lvl=4'
|
|
QoS trace type...............> *ALL</pre>
|
|
<p>The following table introduces
|
|
the possible parameters to use in a trace. If a setting does not appear on
|
|
the character-based interface, you must enter it in a command. For example, <samp class="codeph">TRCTCPAPP
|
|
APP(*QOS) MAXSTG(1000) TRCFULL(*STOPTRC) ARGLIST('l=4 c=i')</samp>.</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" class="firstcol" id="d0e36">Settings</th>
|
|
<th valign="top" id="d0e38">Options</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><th valign="top" class="firstcol" id="d0e42" headers="d0e36 ">TCP/IP application</th>
|
|
<td valign="top" headers="d0e42 d0e38 ">QOS</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e47" headers="d0e36 ">Trace option setting</th>
|
|
<td valign="top" headers="d0e47 d0e38 ">*ON, *OFF, *END, *CHK</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e52" headers="d0e36 ">Maximum storage for trace (MAXSTG)</th>
|
|
<td valign="top" headers="d0e52 d0e38 ">1-16000, *APP</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e57" headers="d0e36 ">Trace full action (TRCFULL)</th>
|
|
<td valign="top" headers="d0e57 d0e38 ">*WRAP, *STOPTRC</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e62" headers="d0e36 ">Argument lists (ARGLIST)</th>
|
|
<td valign="top" headers="d0e62 d0e38 ">Levels: 'lvl=1', 'lvl=2', 'lvl=3', 'lvl=4' Content: 'c=a', 'c=i', 'c=d'
|
|
, 'c=m'</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e67" headers="d0e36 ">QoS trace type</th>
|
|
<td valign="top" headers="d0e67 d0e38 ">*ALL</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
<div class="section" id="rzak8trace_tcp__max"><a name="rzak8trace_tcp__max"><!-- --></a><h4 class="sectiontitle">Maximum storage for trace</h4><dl><dt class="dlterm">1-16000</dt>
|
|
<dd>This is the maximum storage size for the trace data. The trace either
|
|
stops or wraps when this size is reached. The default size is 4MB. To specify
|
|
the default size, select *APP.</dd>
|
|
<dt class="dlterm">*APP</dt>
|
|
<dd>This is the default option. It tells the application to use its default
|
|
trace size. The default trace size for the QoS server is 4MB.</dd>
|
|
</dl>
|
|
</div>
|
|
<div class="section" id="rzak8trace_tcp__action"><a name="rzak8trace_tcp__action"><!-- --></a><h4 class="sectiontitle">Trace full action</h4><dl><dt class="dlterm">*WRAP</dt>
|
|
<dd>Wraps the trace information when the trace reaches the maximum disk space
|
|
(trace buffer size). Wrapping will allow the system to overwrite the oldest
|
|
information in the file, so you continue recording the trace information.
|
|
If you do not select wrap, then the trace operation stops when the disk is
|
|
full.</dd>
|
|
<dt class="dlterm">*STOPTRC</dt>
|
|
<dd>Stops collecting information when the system reaches maximum disk space.</dd>
|
|
</dl>
|
|
</div>
|
|
<div class="section" id="rzak8trace_tcp__list"><a name="rzak8trace_tcp__list"><!-- --></a><h4 class="sectiontitle">Argument lists</h4><p>Specifies which error levels
|
|
and content will be logged. There are two arguments allowed in the TRCTCPAPP
|
|
command: trace level and trace content. When you specify the trace level and
|
|
trace content, make sure all attributes are contained in a single set of quotations.
|
|
For example, <samp class="codeph">TRCTCPAPP 'l=4 c=a'</samp></p>
|
|
<div class="note"><span class="notetitle">Note:</span> Log levels are
|
|
inclusive. This means that when you select a log level, all previous log levels
|
|
are also selected. For example, if you select level 3, then levels 1 and 2
|
|
are automatically included. In a typical trace, it is recommended you specify
|
|
'l=4'.</div>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Trace levels</h4><dl><dt class="dlterm">Level 1: System errors (SYSERR)</dt>
|
|
<dd>Logs errors that occur in systems operations. If this error occurs, the
|
|
QoS server cannot continue. For example, a system error might occur if you
|
|
are running out of system memory or if your system cannot communicate with
|
|
TCP/IP. This is the default level.</dd>
|
|
<dt class="dlterm">Level 2: Errors between objects (OBJERR)</dt>
|
|
<dd>Logs errors that occur within the QoS server code. For example, an object
|
|
error might occur because a server operation encounters some unexpected result.
|
|
This is generally a serious condition that must be reported to service.</dd>
|
|
<dt class="dlterm">Level 3: Specific Events (EVENT)</dt>
|
|
<dd>Logs any QoS operation that has occurred. For example, an event log records
|
|
commands and requests. The results are similar to the QoS journaling function.</dd>
|
|
<dt class="dlterm">Level 4: Trace messages (TRACE)</dt>
|
|
<dd>Traces all data being transferred to and from the QoS server. For example,
|
|
you might use this high-level trace for logging anything that you think might
|
|
be helpful for debugging problems. This information is helpful to determine
|
|
where a problem occurred and how to reproduce the problem.</dd>
|
|
</dl>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Trace content</h4><p>Only specify one content type. If
|
|
you do not specify what content to trace, then (by default) all content will
|
|
be traced.</p>
|
|
<dl><dt class="dlterm">Content = All ('c=a')</dt>
|
|
<dd>Traces all functions of the QoS server. This is the default value.</dd>
|
|
<dt class="dlterm">Content = Intserv ('c=i')</dt>
|
|
<dd>Traces the IntServ operations only. Use this if you determine the problem
|
|
to be IntServ related.</dd>
|
|
<dt class="dlterm">Content = Diffserv ('c=d')</dt>
|
|
<dd>Traces the DiffServ operations only. Use this if you determine the problem
|
|
to be DiffServ related.</dd>
|
|
<dt class="dlterm">Content = Monitor ('c=m')</dt>
|
|
<dd>Traces the monitor operations only.</dd>
|
|
</dl>
|
|
<p>If you need help interpreting the trace output, read the
|
|
trace output example on the trace output page, which contains sample output
|
|
with comments to help you interpret its meaning. The TRCTCPAPP function is
|
|
typically used by the service, so if you have problems reading the output,
|
|
you might contact your service representative.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzak8trace.htm">Examples: Read the trace output</a></strong><br />
|
|
This is not an all-inclusive discussion of how to read your trace output. However, it does highlight the key events to look for in the trace information.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak8troubleshooting.htm" title="Quality of service (QoS) provides several methods to troubleshoot QoS problems.">Troubleshoot QoS</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="../cl/trctcpapp.htm">TRCTCPAPP (Trace TCP/IP Application) Command Description</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |