ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddp_5.4.0.1/rbal1standardtrace.htm

118 lines
7.5 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="Standard communications trace" />
<meta name="abstract" content="The communications trace function lets you start or stop a trace of data on communications configuration objects. After you have run a trace of data, you can format the data for printing or viewing. You can view the printer file only in the output queue." />
<meta name="description" content="The communications trace function lets you start or stop a trace of data on communications configuration objects. After you have run a trace of data, you can format the data for printing or viewing. You can view the printer file only in the output queue." />
<meta name="DC.subject" content="communications trace, system service tools (SST), SST (system service tools)" />
<meta name="keywords" content="communications trace, system service tools (SST), SST (system service tools)" />
<meta name="DC.Relation" scheme="URI" content="rbal1commt.htm" />
<meta name="DC.Relation" scheme="URI" content="rbal1fndlcdd.htm" />
<meta name="DC.Relation" scheme="URI" content="../books/sc415406.pdf" />
<meta name="DC.Relation" scheme="URI" content="../cl/dltcmntrc.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/endcmntrc.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/prtcmntrc.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/strcmntrc.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="rbal1standardtrace" />
<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>Standard communications trace</title>
</head>
<body id="rbal1standardtrace"><a name="rbal1standardtrace"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Standard communications trace</h1>
<div><p>The communications trace function lets you start or stop a trace
of data on communications configuration objects. After you have run a trace
of data, you can format the data for printing or viewing. You can view the
printer file only in the output queue.</p>
<div class="section"><p>Communication trace options run under system service tools (SST).
SST lets you use the configuration objects while communications trace is active.
You can trace and format data for any of the communications types that you
can use in a distributed database network.</p>
</div>
<div class="section"><p>You can run the <span class="keyword">iSeries™</span> communications
trace from any display that is connected to the server. Anyone with a special
authority (SPCAUT) of *SERVICE can run the trace on <span class="keyword">iSeries server</span>.
Communications trace supports all line speeds. </p>
</div>
<div class="section"><p>You should use communications trace in the following situations:
</p>
<ul><li>The problem analysis procedures do not supply sufficient information about
the problem.</li>
<li>You suspect that a protocol violation is the problem.</li>
<li>You suspect a line noise to be the problem.</li>
<li>The error messages indicate that there is a Systems Network Architecture
(SNA) bind problem.</li>
</ul>
<p>You must have detailed knowledge of the line protocols that you use
to correctly interpret the data that is generated by a communications trace.
For information about interpreting DRDA<sup>®</sup> data streams, see <a href="rbal1anrwtr.htm#rbal1anrwtr">Example: Analyze the RW trace data</a>.</p>
</div>
<div class="section"><p>Whenever possible, start the communications trace before varying
on the lines. This gives you the most accurate sample of your line as it varies
on.</p>
</div>
<div class="section"><p>To run an APPC trace and to work with its output, you have to
know on what line, controller, and device you are running.</p>
</div>
<div class="section"><p>To format and avoid unwanted data in the output of a TCP/IP trace,
you can specify the IP addresses of the source and application servers (ASs).
Sometimes it is sufficient to just specify the port number instead, which
is easier. </p>
</div>
<div class="section"><p>The following commands start, stop, print, and delete communications
traces: </p>
<dl><dt class="dlterm"><a name="rbal1standardtrace__max"><!-- --></a><span class="cmdname">Start Communications Trace (STRCMNTRC)</span> command</dt>
<dd>Starts a communications trace for a specified line or network interface
description. Specify *MAX for value of Beginning bytes in Number of bytes
to trace parameter. A communications trace continues until you run the <span class="cmdname">End
Communications Trace (ENDCMNTRC)</span> command.</dd>
<dt class="dlterm"><span class="cmdname">End Communications Trace (ENDCMNTRC)</span> command</dt>
<dd>Ends the communications trace running on the specified line or network
interface description.</dd>
<dt class="dlterm"><span class="cmdname">Print Communications Trace (PRTCMNTRC)</span> command</dt>
<dd>Moves the communications trace data for the specified line or network
interface description to a spooled file or an output file. Specify *YES for
the format SNA data only parameter.</dd>
<dt class="dlterm"><span class="cmdname">Delete Communications Trace (DLTCMNTRC)</span> command</dt>
<dd>Deletes the communications trace for a specified line or network interface
description.</dd>
</dl>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbal1fndlcdd.htm">Find your line, controller, and device descriptions</a></strong><br />
Use the <span class="cmdname">Work with Configuration Status (WRKCFGSTS)</span> command
to find the controller and device under which your application server job
starts.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1commt.htm" title="If you get a message in the CPF3Exx range or the CPF91xx range when using Distributed Relational Database Architecture (DRDA) to access a distributed relational database, you should run a communications trace.">Communications trace</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../books/sc415406.pdf " target="_blank">Communications Management PDF</a></div>
<div><a href="../cl/dltcmntrc.htm">Delete Communications Trace (DLTCMNTRC) command</a></div>
<div><a href="../cl/endcmntrc.htm">End Communications Trace (ENDCMNTRC) command</a></div>
<div><a href="../cl/prtcmntrc.htm">Print Communications Trace (PRTCMNTRC) command</a></div>
<div><a href="../cl/strcmntrc.htm">Start Communications Trace (STRCMNTRC) command</a></div>
</div>
</div>
</body>
</html>