82 lines
4.6 KiB
HTML
82 lines
4.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Client-side ODBC diagnostic and performance tools" />
|
||
|
|
<meta name="abstract" content="Use client-side tools to help diagnose ODBC problems." />
|
||
|
|
<meta name="description" content="Use client-side tools to help diagnose ODBC problems." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiiodbc62.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="rzaiiodbc62clientside" />
|
||
|
|
<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>Client-side ODBC diagnostic and performance tools</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiiodbc62clientside"><a name="rzaiiodbc62clientside"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Client-side ODBC diagnostic and performance tools</h1>
|
||
|
|
<div><p>Use client-side tools to help diagnose ODBC problems.</p>
|
||
|
|
<p>The following table contains ODBC client-side diagnostic and performance
|
||
|
|
tools:</p>
|
||
|
|
<div class="section">
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><tbody><tr><td valign="top" width="25%">ODBC Trace (SQL.LOG)</td>
|
||
|
|
<td valign="top" width="75%">Microsoft's ODBC Administrator provides its own trace utility to trace
|
||
|
|
ODBC API calls from applications.<p>See Collecting an ODBC Trace (SQL.LOG)
|
||
|
|
for more information.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%">ODBC trace utilities</td>
|
||
|
|
<td valign="top" width="75%">There are other ODBC trace utilities available that can be more robust
|
||
|
|
than the ODBC Trace (SQL.LOG). These retail utilities can provide detailed
|
||
|
|
entry and exit point tracing of ODBC API calls. Two tracing utilities are
|
||
|
|
Trace Tools (Dr. DeeBee) and SST Trace Plus (Systems Software Technology). </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%">CWBPING</td>
|
||
|
|
<td valign="top" width="75%">To use CWBPING, type <samp class="codeph">cwbping (your system name or IP address)</samp> at
|
||
|
|
a command prompt. For example: <samp class="codeph">cwbping testsys1</samp> or <samp class="codeph">cwbping
|
||
|
|
127.127.127.1</samp><p>CWBPING responds with a list of servers, and their
|
||
|
|
status. Run CWBPING without any parameters for help with using CWBPING. For
|
||
|
|
more information about CWBPING, see Checking the server status.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%">CWBCOTRC</td>
|
||
|
|
<td valign="top" width="75%">To use CWBCOTRC, type <span class="uicontrol">CWBCOTRC ON</span> at a command
|
||
|
|
prompt while located in the \Program Files\IBM\Client Access directory. After
|
||
|
|
turning on the trace, you can start your application. Typing <span class="uicontrol">CWBCOTRC
|
||
|
|
OFF</span> stops tracing. CWBCOTRC gathers information about data that
|
||
|
|
is being transmitted to and from the server. Run CWBCOTRC without any parameters
|
||
|
|
for help with using CWBCOTRC.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%">Detail trace</td>
|
||
|
|
<td valign="top" width="75%">Detail trace gathers information traced out by the iSeries™ Access
|
||
|
|
for Windows<sup>®</sup> components
|
||
|
|
that are in use. ODBC information that can be found in this trace includes
|
||
|
|
entry points into the driver, information about the prestart job, the package
|
||
|
|
name in use, and special error conditions. For more information, see Gather
|
||
|
|
a detail trace.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiiodbc62.htm" title="Use tools to help diagnose ODBC problems.">ODBC diagnostic and performance tools</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|