106 lines
6.6 KiB
HTML
106 lines
6.6 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="Communications trace" />
|
||
|
|
<meta name="abstract" content="You can use communications trace to determine whether your data is being transmitted correctly across the network." />
|
||
|
|
<meta name="description" content="You can use communications trace to determine whether your data is being transmitted correctly across the network." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakutoolstrc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuplant.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuperformt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakucommanalyzer.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakuaddlt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415302.pdf" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakutraceconn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakujobtrace.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakujobtrace.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="communictrace" />
|
||
|
|
<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>Communications trace</title>
|
||
|
|
</head>
|
||
|
|
<body id="communictrace"><a name="communictrace"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1"><span>Communications trace</span></h1>
|
||
|
|
<div><p>You can use communications trace to determine whether your data
|
||
|
|
is being transmitted correctly across the network.</p>
|
||
|
|
<div class="section"> <p>Use the communications trace function to troubleshoot TCP/IP.
|
||
|
|
Communications trace is a service function that allows the data that flows
|
||
|
|
over a communications line, such as a local area network (LAN) or wide area
|
||
|
|
network (WAN), to be captured for analysis. The communications trace traces
|
||
|
|
only the packets received by or sent from <span>i5/OS™</span>. It
|
||
|
|
does not trace other packets flowing on the network. After the data has been
|
||
|
|
traced, the raw data can be dumped into a stream file, or it can be formatted
|
||
|
|
and placed in a spooled file to be displayed or printed.</p>
|
||
|
|
<p>If your system
|
||
|
|
is multihomed, data might be sent on one interface and received on a different
|
||
|
|
interface. In this situation, you should trace two communications lines to
|
||
|
|
see packets that are sent and received.</p>
|
||
|
|
<p>Communications trace can be
|
||
|
|
used for troubleshooting both IPv4 and IPv6 communications.</p>
|
||
|
|
<p>Use communications
|
||
|
|
trace in these situations:</p>
|
||
|
|
<ul><li>Your problem analysis procedures do not give enough information about
|
||
|
|
the problem.</li>
|
||
|
|
<li>You suspect that a protocol violation is the problem.</li>
|
||
|
|
<li>You suspect that line noise is the problem.</li>
|
||
|
|
<li>You want to know if your application is transmitting information correctly
|
||
|
|
across the network.</li>
|
||
|
|
<li>You want to know if you have performance problems with network congestion
|
||
|
|
or data throughput.</li>
|
||
|
|
</ul>
|
||
|
|
<p>To use the CL commands to perform a communications trace, you must
|
||
|
|
have *SERVICE special authority, or you must be authorized to the service
|
||
|
|
trace function of i5/OS through iSeries™ Navigator. See the chapter on
|
||
|
|
user profiles in iSeries Security
|
||
|
|
Reference for more information about this type of authority.</p>
|
||
|
|
<p>The trace
|
||
|
|
connection function is an alternative method of getting a trace that is similar
|
||
|
|
to a communications trace. See Trace connection for more information.</p>
|
||
|
|
<p>To
|
||
|
|
use the communications trace function, perform these tasks:</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ol>
|
||
|
|
<li class="olchildlink"><a href="rzakuplant.htm">Plan a communications trace</a><br />
|
||
|
|
You can learn how to prepare for the communications trace before using it to determine whether your data is being transmitted correctly across the network.</li>
|
||
|
|
<li class="olchildlink"><a href="rzakuperformt.htm">Perform a communications trace</a><br />
|
||
|
|
You can learn how to perform the communications trace to help you determine whether your data is being transmitted correctly across the network.</li>
|
||
|
|
<li class="olchildlink"><a href="rzakucommanalyzer.htm">Tools for analyzing a communication trace</a><br />
|
||
|
|
The Communications Trace Analyzer is designed to analyze an iSeries communications
|
||
|
|
trace using either the STRCMNTRC command or the TRCCNN command for various
|
||
|
|
performance, connection or security problems you might be experiencing. </li>
|
||
|
|
<li class="olchildlink"><a href="rzakuaddlt.htm">Additional communications trace functions</a><br />
|
||
|
|
You can learn how to check the status of existing communications traces and how to programmatically check the storage space currently allocated for traces.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<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 class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakutraceconn.htm" title="You can trace encrypted data to locate the source of the problem by using trace connection. Trace connection is especially useful for connections, such as virtual Ethernet and OptiConnect, that do not support the general communications trace function.">Trace connection</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakujobtrace.htm" title="Use the job trace tool to trace data in any job to help identify your problem.">Job trace</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../books/sc415302.pdf" target="_blank">iSeries Security Reference PDF</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|