97 lines
7.0 KiB
HTML
97 lines
7.0 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="Files required to build an ODBC application" />
|
||
|
|
<meta name="abstract" content="Identify the files required to build an ODBC application." />
|
||
|
|
<meta name="description" content="Identify the files required to build an ODBC application." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikappodbc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcinterfaces.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcapicplusplus.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcenvconnstate.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikparmmarkers.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiksqlfetchgetdata.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikdirectcodeodbcapis.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikretrieveresults.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikbasicappsteps.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikestodbcconn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikexecuteodbcfunct.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikexecuteprepstmt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcfunctionrc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikendodbcfunct.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="odbcapiinfo" />
|
||
|
|
<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>Files required to build an ODBC application</title>
|
||
|
|
</head>
|
||
|
|
<body id="odbcapiinfo"><a name="odbcapiinfo"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Files required to build an ODBC application</h1>
|
||
|
|
<div><p>Identify the files required to build an ODBC application.</p>
|
||
|
|
<div class="section"><p>Choose from the following topics for information on files and
|
||
|
|
other concepts used in building an ODBC application.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The Programmer's
|
||
|
|
Toolkit provides ODBC documentation, and links to sample programs and related
|
||
|
|
information. To access this information, open the Programmer's Toolkit and
|
||
|
|
select <span class="menucascade"><span class="uicontrol">Database</span> > <span class="uicontrol">ODBC</span></span>.</div>
|
||
|
|
<p></p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikodbcinterfaces.htm">Choose an interface to access the ODBC driver</a></strong><br />
|
||
|
|
There are different programming interfaces that can be used with
|
||
|
|
the iSeries™ Access
|
||
|
|
for Windows<sup>®</sup> ODBC
|
||
|
|
Driver. Each interface has its strengths and weaknesses.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikodbcapicplusplus.htm">ODBC C/C++ application header files</a></strong><br />
|
||
|
|
Identify C/C++ header files for an ODBC C/C++ application.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikodbcenvconnstate.htm">ODBC APIs: General concepts</a></strong><br />
|
||
|
|
The following general concepts apply to ODBC APIs:</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikparmmarkers.htm">Parameter markers</a></strong><br />
|
||
|
|
Parameter markers act as place holders for values that are supplied by the program when you instruct the data source to run the SQL statement.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaiksqlfetchgetdata.htm">SQLFetch and SQLGetData</a></strong><br />
|
||
|
|
<strong>SQLGetData</strong> provides an alternative to <strong>SQLBindCol</strong> to
|
||
|
|
retrieve data from the columns of a retrieved row. It can only be called after
|
||
|
|
calling fetch APIs and when the array size is 1.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikdirectcodeodbcapis.htm">Code directly to ODBC APIs</a></strong><br />
|
||
|
|
Many PC applications make ODBC calls that allow the user to seamlessly access data on different platforms. Before you begin developing your own application with ODBC APIs, you should understand how an ODBC application connects to and exchanges information with a database server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikretrieveresults.htm">Retrieve results</a></strong><br />
|
||
|
|
In order to work with all of the rows in a result set, call the <strong>SQLFetch</strong> API
|
||
|
|
until no more rows are returned.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikbasicappsteps.htm">Access a database server with an ODBC application</a></strong><br />
|
||
|
|
An ODBC application needs to follow a basic set of steps in order to access a database server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikestodbcconn.htm">Establish ODBC connections</a></strong><br />
|
||
|
|
Use these handle types to establish an ODBC connection.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikexecuteodbcfunct.htm">Execute ODBC functions</a></strong><br />
|
||
|
|
Use these handle types to execute ODBC functions.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikexecuteprepstmt.htm">Execute prepared statements</a></strong><br />
|
||
|
|
If an <span class="keyword">SQL</span> statement
|
||
|
|
is used more than once, it is best to have the statement prepared and then
|
||
|
|
executed.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikodbcfunctionrc.htm">ODBC API return codes</a></strong><br />
|
||
|
|
Every ODBC API function returns a value of type SQLRETURN (a short integer). There are seven possible return codes, and associated with each is a manifest constant.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikendodbcfunct.htm">End ODBC functions</a></strong><br />
|
||
|
|
The last procedure that must be completed before ending an ODBC application is to free the resources and memory allocated by the application. This must be done so that they are available when the application is run the next time.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikappodbc.htm" title="A common database interface that uses SQL as its database access language. iSeries Access for Windows provides an ODBC driver to support this interface.">iSeries Access for Windows ODBC</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|