109 lines
6.3 KiB
HTML
109 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="Server-side ODBC diagnostic and performance tools" />
|
||
|
|
<meta name="abstract" content="Use server-side tools to help diagnose ODBC problems." />
|
||
|
|
<meta name="description" content="Use server-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="rzaiiodbc62serverside" />
|
||
|
|
<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>Server-side ODBC diagnostic and performance tools</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiiodbc62serverside"><a name="rzaiiodbc62serverside"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Server-side ODBC diagnostic and performance tools</h1>
|
||
|
|
<div><p>Use server-side tools to help diagnose ODBC problems.</p>
|
||
|
|
<p>The following tables contain ODBC diagnostic and performance tools the
|
||
|
|
server side:</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Server-side tools</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><tbody><tr><td valign="top" width="25%">Communications trace</td>
|
||
|
|
<td valign="top" width="75%">The communications trace facility will trace and format any communications
|
||
|
|
type that has a line description (token ring and Ethernet).<p>This is a tool
|
||
|
|
for isolating many problems. It also is a useful aid for diagnosing where
|
||
|
|
a performance delay is occurring. Use the timestamp and eye-catcher fields
|
||
|
|
to measure how long it takes to process a request.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%">Job traces</td>
|
||
|
|
<td valign="top" width="75%">The job trace can help isolate most host problems and many performance
|
||
|
|
issues. A service job must first be started on the job to be traced. Locate
|
||
|
|
the fully qualified job name of the ODBC job. From any 5250 emulation session,
|
||
|
|
start a service job on this QZDASOINIT job by using the STRSRVJOB command.
|
||
|
|
Then choose one of two traces, depending on the information needed:<dl><dt class="dlterm">Trace job</dt>
|
||
|
|
<dd>Traces the internal calls made by the host server. Run the TRCJOB *ON
|
||
|
|
command.</dd>
|
||
|
|
<dt class="dlterm">Debug trace</dt>
|
||
|
|
<dd>Used to review the performance of your application and to determine the
|
||
|
|
cause of a particular problem.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>The STRDBG command runs against an active service job. This
|
||
|
|
command logs the decisions made by the query Optimizer to the job log of the
|
||
|
|
debug session. For example, it records estimated query times, access paths
|
||
|
|
used, and cursor errors.</p>
|
||
|
|
<p>An easy way to enable STRDBG is to configure
|
||
|
|
the ODBC DSN you are using through <span class="uicontrol">ODBC Adminstrator</span> by
|
||
|
|
selecting the <span class="uicontrol">Enable the Start Debug (STRDBG) command</span> option
|
||
|
|
on the <span class="uicontrol">Diagnostic</span> tab. Alternatively, you can run the
|
||
|
|
following command:</p>
|
||
|
|
<pre> STRDBG UPDPROD(*YES)</pre>
|
||
|
|
<p>The
|
||
|
|
ODBC job log can record all errors that occur on the iSeries™ server. When the job is in debug
|
||
|
|
mode, the job log also will contain performance-related information.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%">Performance tools</td>
|
||
|
|
<td valign="top" width="75%">Performance toolkit provides reports and utilities that can be used
|
||
|
|
to create an in-depth analysis of your application performance. The toolkit
|
||
|
|
provides information about CPU utilization, disk arm utilization, memory paging
|
||
|
|
and much more. Although the base operating system includes the ability to
|
||
|
|
collect performance data, you will need the separately licensed program <span class="uicontrol">Performance
|
||
|
|
Tools/400</span> to analyze the results.<p>You can also use the tools
|
||
|
|
Database Monitor and Visual Explain. Refer to the iSeries Navigator Online help for more
|
||
|
|
information.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%">QZDASOINIT job log</td>
|
||
|
|
<td valign="top" width="75%">To receive optimal support, generate, locate and retrieve the QZDASOINIT
|
||
|
|
job log. The job log may contain messages that can help you to determine and
|
||
|
|
resolve errors that are returned through ODBC.<p>An easy way to access the
|
||
|
|
job log is to configure the ODBC DSN you are using through <span class="uicontrol">ODBC
|
||
|
|
Adminstrator</span> by selecting the <span class="uicontrol">Print job log at disconnect</span> option
|
||
|
|
on the <span class="uicontrol">Diagnostic</span> tab. To find the job log, open a <span class="uicontrol">PC5250</span> emulation
|
||
|
|
session and run the WRKSPLF command. Specify the iSeries user profile that was used on
|
||
|
|
the ODBC connection as the user parameter for the WRKSPLF command.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%">QAQQINI (Query options file)</td>
|
||
|
|
<td valign="top" width="75%">You can set the library for Query options file, by configuring the
|
||
|
|
ODBC DSN you are using through <span class="uicontrol">ODBC Adminstrator</span> and
|
||
|
|
selecting the <span class="uicontrol">Diagnostic</span> tab. Enter the name of the
|
||
|
|
library you want to use in the Query options file library box.</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>
|