88 lines
5.1 KiB
HTML
88 lines
5.1 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="ODBC FAQs" />
|
||
|
|
<meta name="abstract" content="Find frequently asked questions about ODBC for iSeries Access for Linux." />
|
||
|
|
<meta name="description" content="Find frequently asked questions about ODBC for iSeries Access for Linux." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzatvodbc.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="faqodbc" />
|
||
|
|
<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>ODBC FAQs</title>
|
||
|
|
</head>
|
||
|
|
<body id="faqodbc"><a name="faqodbc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">ODBC FAQs</h1>
|
||
|
|
<div><p>Find frequently asked questions about ODBC for iSeries™ Access
|
||
|
|
for Linux<sup>®</sup>.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">What are the differences between the ODBC driver in iSeries Access
|
||
|
|
for Linux and
|
||
|
|
the ODBC driver in iSeries Access for Windows<sup>®</sup>?</h4><p>The following table
|
||
|
|
describes some of the differences between the ODBC driver in iSeries Access
|
||
|
|
for Linux and
|
||
|
|
the ODBC driver in iSeries Access for Windows: </p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Differences
|
||
|
|
between iSeries Access
|
||
|
|
for Linux ODBC
|
||
|
|
driver and iSeries Access
|
||
|
|
for Windows ODBC
|
||
|
|
driver.</caption><thead align="left"><tr><th valign="top" width="18.456375838926174%" id="d0e68">Function</th>
|
||
|
|
<th valign="top" width="40.604026845637584%" id="d0e70">Linux ODBC</th>
|
||
|
|
<th valign="top" width="40.939597315436245%" id="d0e74">Windows ODBC</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="18.456375838926174%" headers="d0e68 ">The driver</td>
|
||
|
|
<td valign="top" width="40.604026845637584%" headers="d0e70 ">The driver is an ODBC 3.5 ANSI driver with the ability
|
||
|
|
to store and process Unicode data. An ANSI driver does not support Unicode
|
||
|
|
strings passed as arguments to the APIs. Applications passing Unicode strings
|
||
|
|
on APIs will work because the unixODBC driver manager maps calls these calls
|
||
|
|
to the ANSI driver's narrow interfaces. </td>
|
||
|
|
<td valign="top" width="40.939597315436245%" headers="d0e74 ">The driver is an ODBC 3.5 Unicode driver. A Unicode
|
||
|
|
driver accepts Unicode strings as arguments to the APIs. </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="18.456375838926174%" headers="d0e68 ">Signon</td>
|
||
|
|
<td valign="top" width="40.604026845637584%" headers="d0e70 ">To sign on you must specify a user ID and password when
|
||
|
|
calling the connection API or have the user ID and password entered into the
|
||
|
|
DSN. The ODBC driver will not prompt for iSeries user IDs or passwords. User ID
|
||
|
|
and password updates must be done through a telnet session with the iSeries.</td>
|
||
|
|
<td valign="top" width="40.939597315436245%" headers="d0e74 ">The user has sign on options that control which user
|
||
|
|
ID and password to use when connecting. When connecting, cached passwords
|
||
|
|
might be used. If a user's password has expired a dialog is displayed to
|
||
|
|
allow a user to change it.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="18.456375838926174%" headers="d0e68 ">Binding a parameter or column</td>
|
||
|
|
<td valign="top" width="40.604026845637584%" headers="d0e70 ">When binding a parameter or a column with SQL_C_WCHAR
|
||
|
|
as the C type, wchar_t buffers should not be passed in. The driver manager
|
||
|
|
and driver both handle the SQL_C_WCHAR data type as a 2 byte UCS-2 string.</td>
|
||
|
|
<td valign="top" width="40.939597315436245%" headers="d0e74 ">When binding a parameter or a column with SQL_C_WCHAR
|
||
|
|
as the C type, wchar_t buffers should be passed in. The driver manager and
|
||
|
|
driver both handle the SQL_C_WCHAR data type as a 2 byte UCS-2 string.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzatvodbc.htm" title="For information on using Open Database Connectivity (ODBC) with iSeries Access for Linux, see the following topics.">Open Database Connectivity</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|