90 lines
6.3 KiB
HTML
90 lines
6.3 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Communications trace" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="error reporting, communications trace, messages, trace, communications, problem handling, TRCTCPAPP, function" />
|
||
|
|
<meta name="keywords" content="error reporting, communications trace, messages, trace, communications, problem handling, TRCTCPAPP, function" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1gdrf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1standardtrace.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1connsec.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1jobt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1papptrace.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="rbal1commt" />
|
||
|
|
<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="rbal1commt"><a name="rbal1commt"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Communications trace</h1>
|
||
|
|
<div><p>If you get a message in the CPF3Exx range or the CPF91xx range
|
||
|
|
when using Distributed
|
||
|
|
Relational Database Architecture™ (DRDA<sup>®</sup>) to access a distributed relational
|
||
|
|
database, you should run a communications trace.</p>
|
||
|
|
<p>The following list shows common messages you might see in these ranges.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="void" border="1" rules="rows"><caption>Table 1. Communications trace messages</caption><thead align="left"><tr><th valign="top" width="24.242424242424242%" id="d0e58">MSG ID</th>
|
||
|
|
<th valign="top" width="75.75757575757575%" id="d0e60">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="24.242424242424242%" headers="d0e58 ">CPF3E80</td>
|
||
|
|
<td valign="top" width="75.75757575757575%" headers="d0e60 ">DDM data stream syntax error.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="24.242424242424242%" headers="d0e58 ">CPF91xx</td>
|
||
|
|
<td valign="top" width="75.75757575757575%" headers="d0e60 ">DDM protocol error.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="24.242424242424242%" headers="d0e58 ">CPF3E83</td>
|
||
|
|
<td valign="top" width="75.75757575757575%" headers="d0e60 ">Invalid FD0:CA descriptor.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="24.242424242424242%" headers="d0e58 ">CPF3E84</td>
|
||
|
|
<td valign="top" width="75.75757575757575%" headers="d0e60 ">Data mismatch error.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<p>You can perform two types of communications traces. The first
|
||
|
|
is the standard communications trace. The second is the TRCTCPAPP function.
|
||
|
|
The TRCTCPAPP function provides for intelligible traces where IPSec or the
|
||
|
|
secure sockets protocol has encrypted the data streams. It captures the data
|
||
|
|
before encryption and after decryption. However, it also works well for getting
|
||
|
|
traces of unencrypted data streams. It is required for getting traces of intra-system DRDA flows
|
||
|
|
where LOOPBACK is used. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1standardtrace.htm">Standard communications trace</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1gdrf.htm" title="This topic collection describes the kinds of data that you can print to help you diagnose a problem in a distributed relational database on iSeries servers.">Get data to report a failure</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbal1jobt.htm" title="Sometimes a problem cannot be tracked to a specific program. In these cases, Start Trace (STRTRC) and Trace Job (TRCJOB) commands can be used for tracing module flow, i5/OS data acquisition and CL commands executed.">Job tracing</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rbal1papptrace.htm" title="One of the uses of the trace tool is to show the clear text of a transmission in an environment where the data is encrypted.">TCP/IP communications trace</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="rbal1connsec.htm" title="Several connection security protocols are supported by the current DB2 UDB for iSeries implementation of distributed data management (DDM) or Distributed Relational Database Architecture (DRDA) over TCP/IP.">Connection security protocols for DDM and DRDA</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|