119 lines
7.4 KiB
HTML
119 lines
7.4 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="Connection string keywords - Diagnostic properties" />
|
||
|
<meta name="abstract" content="Use these iSeries Access ODBC driver connection string keywords to change Diagnostic properties of the ODBC connection." />
|
||
|
<meta name="description" content="Use these iSeries Access ODBC driver connection string keywords to change Diagnostic properties of the ODBC connection." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="connectkeywords.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rzaikconnstrkeywordsdiagprop" />
|
||
|
<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>Connection string keywords - Diagnostic properties</title>
|
||
|
</head>
|
||
|
<body id="rzaikconnstrkeywordsdiagprop"><a name="rzaikconnstrkeywordsdiagprop"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Connection string keywords - Diagnostic properties</h1>
|
||
|
<div><p>Use these iSeries™ Access ODBC driver connection string keywords
|
||
|
to change Diagnostic properties of the ODBC connection.</p>
|
||
|
<div class="section"><p>The following table lists connection string keywords for Diagnostic
|
||
|
properties that are recognized by the iSeries Access ODBC driver:</p>
|
||
|
</div>
|
||
|
<div class="section">
|
||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. iSeries Access ODBC connection string keywords for
|
||
|
Diagnostic properties </caption><thead align="left"><tr><th align="center" valign="middle" width="21.73913043478261%" id="d0e35">Keyword</th>
|
||
|
<th align="center" valign="middle" width="35.177865612648226%" id="d0e37">Description</th>
|
||
|
<th align="center" valign="middle" width="33.59683794466403%" id="d0e39">Choices</th>
|
||
|
<th align="center" valign="middle" width="9.486166007905137%" id="d0e41">Default</th>
|
||
|
</tr>
|
||
|
</thead>
|
||
|
<tbody><tr><td valign="top" width="21.73913043478261%" headers="d0e35 ">MAXTRACESIZE</td>
|
||
|
<td valign="top" width="35.177865612648226%" headers="d0e37 ">Specifies the maximum trace size (in MB) of the internal
|
||
|
driver trace. Specifying a value of 0 means no limit. This property has
|
||
|
no effect unless the TRACE property has option 1 set.</td>
|
||
|
<td valign="top" width="33.59683794466403%" headers="d0e39 "> 0 (no limit) - 1000</td>
|
||
|
<td valign="top" width="9.486166007905137%" headers="d0e41 "> 0 </td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" width="21.73913043478261%" headers="d0e35 ">MULTTRACEFILES or MultipleTraceFiles</td>
|
||
|
<td valign="top" width="35.177865612648226%" headers="d0e37 ">Specifies whether or not trace data from the internal
|
||
|
driver trace will be put into multiple files. A new file will be created
|
||
|
for each thread that the application is using. This property has no effect
|
||
|
unless the TRACE property has option 1 set. </td>
|
||
|
<td valign="top" width="33.59683794466403%" headers="d0e39 "> 0 = Trace data into a single file <p>1 = Trace data
|
||
|
into multiple files</p>
|
||
|
</td>
|
||
|
<td valign="top" width="9.486166007905137%" headers="d0e41 ">1 </td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" width="21.73913043478261%" headers="d0e35 ">QAQQINILIB or QAQQINILibrary</td>
|
||
|
<td valign="top" width="35.177865612648226%" headers="d0e37 ">Specifies a query options file library. When a query
|
||
|
options file library is specified the driver will issue the command CHGQRYA
|
||
|
passing the library name for the QRYOPTLIB parameter. The command is issued
|
||
|
immediately after the connection is established. This option should only
|
||
|
be used when debugging problems or when recommended by support as enabling
|
||
|
it will adversely affect performance. </td>
|
||
|
<td valign="top" width="33.59683794466403%" headers="d0e39 ">Query options file library</td>
|
||
|
<td valign="top" width="9.486166007905137%" headers="d0e41 "> none </td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" width="21.73913043478261%" headers="d0e35 ">SQDIAGCODE</td>
|
||
|
<td valign="top" width="35.177865612648226%" headers="d0e37 ">Specifies DB2<sup>®</sup> UDB SQL diagnostic options to be set.
|
||
|
Use only as directed by your technical support provider.</td>
|
||
|
<td valign="top" width="33.59683794466403%" headers="d0e39 ">DB2 UDB SQL diagnostic options </td>
|
||
|
<td valign="top" width="9.486166007905137%" headers="d0e41 ">none </td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" width="21.73913043478261%" headers="d0e35 ">TRACE </td>
|
||
|
<td valign="top" width="35.177865612648226%" headers="d0e37 ">Specifies one or more trace options. To specify multiple
|
||
|
trace options add together the values for the options that you want. For
|
||
|
example, if you want the Database Monitor and Start Debug command to be activated
|
||
|
on the server then the value you would want to specify is 6. These options
|
||
|
should only be used when debugging problems or when recommended by support
|
||
|
as they will adversely affect performance.</td>
|
||
|
<td valign="top" width="33.59683794466403%" headers="d0e39 ">To determine the value for this keyword, add the
|
||
|
values below that are associated with each option that you want. <p>0 = No
|
||
|
tracing </p>
|
||
|
<p>1 = Enable internal driver tracing</p>
|
||
|
<p>2 = Enable Database
|
||
|
Monitor</p>
|
||
|
<p>4 = Enable the <span class="cmdname">Start Debug (STRDBG)</span> command</p>
|
||
|
<p>8
|
||
|
= Print job log at disconnect</p>
|
||
|
<p>16 = Enable job trace</p>
|
||
|
<p> 32 = Enable
|
||
|
database host server trace</p>
|
||
|
</td>
|
||
|
<td valign="top" width="9.486166007905137%" headers="d0e41 ">0 </td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" width="21.73913043478261%" headers="d0e35 ">TRACEFILENAME</td>
|
||
|
<td valign="top" width="35.177865612648226%" headers="d0e37 ">Specifies the full path name to either the file or the
|
||
|
directory in which to put the internal driver trace data into. A path name
|
||
|
to the file should be specified if MULTTRACEFILES is set to 0. A path name
|
||
|
to a directory should be specified if MULTTRACEFILES is set to 1. This property
|
||
|
has no effect unless the TRACE property has option 1 set.</td>
|
||
|
<td valign="top" width="33.59683794466403%" headers="d0e39 ">Full path name to file or directory </td>
|
||
|
<td valign="top" width="9.486166007905137%" headers="d0e41 ">none </td>
|
||
|
</tr>
|
||
|
</tbody>
|
||
|
</table>
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="connectkeywords.htm" title="The iSeries Access ODBC driver has many connection string keywords that can be used to change the behavior of the ODBC connection.">Connection string keywords</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|