74 lines
4.8 KiB
HTML
74 lines
4.8 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="task" />
|
||
|
|
<meta name="DC.Title" content="Read a communications trace" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuperformt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuviewt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakudeletet.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="readt" />
|
||
|
|
<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>Read a communications trace</title>
|
||
|
|
</head>
|
||
|
|
<body id="readt"><a name="readt"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Read a communications trace</h1>
|
||
|
|
<div><div class="section"> <p>The communications trace displays several types of information.
|
||
|
|
The first part of the communications trace summarizes the prompts that you
|
||
|
|
specified when you started the trace, such as the name of the <em>Configuration
|
||
|
|
object</em>. Page down to find a list of items, such as <em>Record Number</em> and <em>S/R</em>,
|
||
|
|
with associated definitions. These items represent titles that are later used
|
||
|
|
to identify sections of the communications trace data. It might be useful
|
||
|
|
to refer back to this list as you read the trace data. This figure shows the
|
||
|
|
preliminary information in a communications trace.</p>
|
||
|
|
<br /><img src="rzaku001.gif" alt="This figure shows the first part of a communications
trace. A description precedes the figure." /><br /><p>After reading the
|
||
|
|
preliminary information, page down to the actual TCP/IP data in the communications
|
||
|
|
trace. A row of titles, starting with <em>Record Number</em>, identifies each
|
||
|
|
section of the data records. Each record number represents a
|
||
|
|
frame, and it includes information that can help you debug the problem that
|
||
|
|
you are having with TCP/IP on this server or in the associated network.</p>
|
||
|
|
<p>If
|
||
|
|
you find an asterisk (*) after a record number, for example, <samp class="codeph">31*</samp>,
|
||
|
|
be aware that the asterisk represents missing trace data. This missing trace
|
||
|
|
data appears when communications trace records are dropped. Communications
|
||
|
|
trace data is collected by the input/output processor (IOP). If the communications
|
||
|
|
line is very busy, the IOP prioritizes all the network traffic and gives a
|
||
|
|
higher priority to the data path input/output than to the communications trace
|
||
|
|
information. Under these circumstances, the IOP might drop some of the communications
|
||
|
|
trace records. This can indicate that the IOP is not capable of handling the
|
||
|
|
excessive speeds or traffic on the network.</p>
|
||
|
|
<div class="p">If your communications trace
|
||
|
|
is missing data, consider these options: <ul><li>Acknowledge that your communications line is busy and that frames will
|
||
|
|
be missing from your communications trace.</li>
|
||
|
|
<li>Investigate the traffic on the communications line to determine if there
|
||
|
|
is traffic that can be moved to another line or TCP/IP interface.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>This figure shows the TCP/IP data portion of the communications
|
||
|
|
trace.</p>
|
||
|
|
<br /><img src="rzaku002.gif" alt="This figure shows
the TCP/IP data portion of a communications trace. A description precedes
the figure." /><br /></div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakuperformt.htm" title="You can learn how to perform the communications trace to help you determine whether your data is being transmitted correctly across the network.">Perform a communications trace</a></div>
|
||
|
|
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzakuviewt.htm">View the contents of a communications trace</a></div>
|
||
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzakudeletet.htm">Delete a communications trace</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|