ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaik_5.4.0.1/rzaikversionreleasechanges.htm

123 lines
7.3 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Version and release changes in the ODBC driver behavior" />
<meta name="abstract" content="This topic describes version and release changes in the ODBC driver behavior." />
<meta name="description" content="This topic describes version and release changes in the ODBC driver behavior." />
<meta name="DC.Relation" scheme="URI" content="rzaikodbcapifunctions.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="versionreleasechanges" />
<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>Version and release changes in the ODBC driver behavior</title>
</head>
<body id="versionreleasechanges"><a name="versionreleasechanges"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Version and release changes in the ODBC driver behavior</h1>
<div><p>This topic describes version and release changes in the ODBC driver
behavior.</p>
<div class="section"><img src="./delta.gif" alt="Start of change" /><h4 class="sectiontitle">The following list describes some of the important
changes for V5R4:</h4><div class="p">There are several new features available when
using the ODBC driver to access data on a V5R4 iSeries™ server. These features include:<ul><li>Support for 128-byte column names</li>
<li>Support for longer SQL statements (commands can be up to 2,097,152 bytes
or 1,048,576 characters long)</li>
<li>Support for passing an IBM<sup>®</sup> Enterprise Workload Manager (eWLM) correlator to
the iSeries host</li>
<li>Improved support for table and column names that are not all uppercase</li>
<li>Enhanced distributed transaction support for loosely coupled transactions</li>
<li>A Linux<sup>®</sup> 64-bit
ODBC driver </li>
</ul>
</div>
<img src="./deltaend.gif" alt="End of change" /></div>
<div class="section"><h4 class="sectiontitle">The following list describes some of the important changes
for V5R3:</h4><p>There are several new features available when using the
ODBC driver to access data on a V5R3 iSeries server. These features include:</p>
<ul><li>DB2<sup>®</sup> UDB
database types of BINARY and VARBINARY</li>
<li>UTF-8 and UTF-16 data </li>
<li>Increased precision of decimal numbers</li>
<li>Support for accessing stored procedure result sets with scrollable cursors</li>
<li>Enhanced commitment control model so that autocommit can run with any
isolation level</li>
<li>Enhanced Microsoft<sup>®</sup> Transaction Server (MTS) / XA support
which allows the coordination of transactions across multiple iSeries connections</li>
</ul>
</div>
<div class="section"><h4 class="sectiontitle">The following list describes some of the important changes
for V5R2:</h4><p>There are several new features available when using the
ODBC driver to access data on a V5R2 iSeries server. These features include:</p>
<ul><li>Ability to send Structured Query Language (SQL) statements that are 64K
bytes long to the DB2 UDB database (the previous limit was 32K bytes)</li>
<li>Ability to make use of the DB2 UDB database type of ROWID</li>
<li>Ability to get back additional descriptor information, such as the base
table name for a result set column </li>
<li>Ability to access multiple databases on the same iSeries server</li>
<li>Ability to retrieve meaningful information from the SQLTablePrivileges
and SQLColumnPrivileges APIs</li>
<li>Ability to use Kerberos support for authenticating a user to an iSeries server</li>
<li>Ability to retrieve, regardless of the iSeries server version, more information
in the result sets for the catalog APIs. The driver now queries the iSeries catalog
tables directly to provide the result set for the catalog APIs.</li>
</ul>
</div>
<div class="section"><h4 class="sectiontitle">The following list describes some of the important changes
for V5R1:</h4><ul><li>Character data for parameter markers is converted from the iSeries Access(PC)
codepage directly to the column CCSID. If a new iSeries Access codepage setting was specified
on the Advanced Translation Options dialog of the DSN setup GUI, it will be
the iSeries Access(PC)
codepage. The V4R5 driver first converted character data from the iSeries Access(PC)
codepage to the job CCSID before it was converted to the column CCSID. </li>
<li>Character column data is converted directly from the column CCSID to the iSeries Access(PC)
codepage. If the C type specified is SQL_C_WCHAR, then the data is converted
to Unicode.</li>
<li>If the value type specified in SQLBindParameter is SQL_C_WCHAR, then the
driver converts the parameter marker data from Unicode to the column CCSID.</li>
<li>When calling SQLBindParameter for a SQL_C_CHAR to INTEGER conversion,
if BufferLength is 0 and the buffer contains an empty string then an error
is returned. The V4R5 driver would accept the empty string and insert the
value of 0 into the table.</li>
<li>The lazy close option default is 0 (OFF), and in V4R5 its default was
1 (ON).</li>
<li>The prefetch option default is 0 (OFF), and in V4R5 its default was 1
(ON).</li>
<li>Unicode SQL statements can be sent to V5R1 or later iSeries servers.
The package names are generated differently than in V4R5 when sending Unicode
SQL statements.</li>
<li>Managed DSNs (created through V4R5 or earlier iSeries Navigator) are not supported.
They are instead treated like a User DSN, meaning that the DSN information
is not updated from the server copy.</li>
<li>BIGINT data type is supported to V4R5 (or later) hosts.</li>
<li>Static cursor supported to V5R1 or later hosts. In earlier hosts, and
in previous iSeries Access
for Windows<sup>®</sup> ODBC
drivers, static cursor type is mapped to dynamic.</li>
<li>The V5R1 driver supports the ODBC 3.51 specification. In V4R5, the ODBC
2.5 specification was supported.</li>
<li>In V5R1, no conversion is performed when fetching data from a char field
and retrieving it as SQL_C_BINARY. In V4R5, the driver translated data from
EBCDIC codepages to ASCII codepages.</li>
</ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikodbcapifunctions.htm" title="Learn about implementations issues when using ODBC APIs.">Implementation issues of ODBC APIs</a></div>
</div>
</div>
</body>
</html>