105 lines
7.2 KiB
HTML
105 lines
7.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="Interpret data entries for the RW component of trace job" />
|
||
|
|
<meta name="abstract" content="The RW component of the i5/OS licensed program includes most of the Distributed Relational Database Architecture (DRDA) support." />
|
||
|
|
<meta name="description" content="The RW component of the i5/OS licensed program includes most of the Distributed Relational Database Architecture (DRDA) support." />
|
||
|
|
<meta name="DC.subject" content="interpreting, data entries, for the RW component of trace job, data entries" />
|
||
|
|
<meta name="keywords" content="interpreting, data entries, for the RW component of trace job, data entries" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1ffdcap.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1anrwtr.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1trcpts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/trcjob.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="rbal1interpretdata" />
|
||
|
|
<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>Interpret data entries for the RW component of trace job</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1interpretdata"><a name="rbal1interpretdata"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Interpret data entries for the RW component of trace job</h1>
|
||
|
|
<div><p>The RW component of the <span class="keyword">i5/OS™</span> licensed
|
||
|
|
program includes most of the Distributed Relational
|
||
|
|
Database Architecture™ (DRDA<sup>®</sup>) support.</p>
|
||
|
|
<div class="section"><p>RW component produces certain types of diagnostic information
|
||
|
|
when the <span class="cmdname">Trace Job (TRCJOB)</span> command is issued with TRCTYPE(*ALL)
|
||
|
|
or TRCTYPE(*DATA). RW trace points can be located easily by doing a find operation
|
||
|
|
using the string >> as the search argument. </p>
|
||
|
|
<p>The end of the data dumped at each trace point can be determined by looking
|
||
|
|
for the <<<... delimiter characters. There are one or more of the <
|
||
|
|
delimiter characters at the end of the data, enough to fill out the last line.</p>
|
||
|
|
</div>
|
||
|
|
<div class="example"> <div class="fignone" id="rbal1interpretdata__rbal1rwinf"><a name="rbal1interpretdata__rbal1rwinf"><!-- --></a><span class="figcap">Figure 1. An example of job trace RW component
|
||
|
|
information</span><pre>DATA FF 6E6ED9E6D8E840D9C37A0016D052000100102205000611490000 *>>RWOQ RC: } *
|
||
|
|
DATA FF 0006210224170025D0530001001F241A0C76D00500023100030A * } } *
|
||
|
|
DATA FF 00080971E0540001D000010671F0E00000002CD0530001002624 * \ } 0\ } *
|
||
|
|
DATA FF 1BFF0000000100F1F1F14110000000000000FF0000000200F2F2 * 111 22 *
|
||
|
|
DATA FF F241200000000000000026D05200010020220B00061149000400 *2 } *
|
||
|
|
DATA FF 162110C4C2F2C5E2E8E240404040404040404040400056D00300 * DB2ESYS } *
|
||
|
|
DATA FF 01005024080000000064F0F2F0F0F0C4E2D5E7D9C6D54000C4C2 * & 02000DSNXRFN DB *
|
||
|
|
DATA FF F2C5E2E8E24040404040404040404040FFFFFF92000000000000 *2ESYS k *
|
||
|
|
DATA FF 0000FFFFFFFF0000000000000000404040404040404040404000 * *
|
||
|
|
DATA FF 0000004C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C * <<<<<<<<<<<<<<<<<<<<<< *
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="p"> <div class="note"><span class="notetitle">Note:</span> There is an exception to the use of the < delimiters
|
||
|
|
to determine the end of data. In certain rare circumstances where a received
|
||
|
|
data stream is being dumped, the module that writes the trace data is unable
|
||
|
|
to determine where the end of the data stream is. In that case, the program
|
||
|
|
dumps the entire receive buffer, and as a warning that the length of the data
|
||
|
|
dumped is greater than that of the data stream, it replaces the <<<...
|
||
|
|
delimiter with a string of ( characters.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Following the >> prefix is a seven-character string that
|
||
|
|
identifies the trace point. The first two characters, RW, identify the component.
|
||
|
|
The second two characters identify the RW function being performed. The QY
|
||
|
|
indicates the query function which corresponds to the DDM commands OPNQRY,
|
||
|
|
CNTQRY, and CLSQRY. The EX indicates the EXECUTE function which corresponds
|
||
|
|
to the DDM commands EXCSQLSTT, EXCSQLIMM, and PRPSQLSTT.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Which program module corresponds to each of these functions depends
|
||
|
|
on whether the job trace was taken at the application requester (AR) end of
|
||
|
|
the distributed SQL access operation, or at the application server (AS) end.
|
||
|
|
The modules performing the process and query functions at the AR are QRWSEXEC
|
||
|
|
and QRWSQRY. The modules at the AS are QRWTEXEC and QRWTQRY.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The last two characters of the seven-byte trace point identifier
|
||
|
|
indicate the nature of the dumped data or the point at which the dump is taken.
|
||
|
|
For example, SN corresponds to the data stream sent from an AR or an AS, and
|
||
|
|
RC corresponds to the data stream received by an AR.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1anrwtr.htm">Example: Analyze the RW trace data</a></strong><br />
|
||
|
|
This discussion examines the elements that make up the data stream in the example.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1trcpts.htm">Description of RW trace points</a></strong><br />
|
||
|
|
This topic collection discusses the RW trace points.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1ffdcap.htm" title="This topic collection provides additional problem-analysis information. It is useful to specialists responsible for problem determination. It is also for suppliers of software products designed to conform to the Distributed Relational Database Architecture who want to test connectivity to an iSeries server.">Interpret trace job and FFDC data</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/trcjob.htm">Trace Job (TRCJOB) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|