89 lines
7.0 KiB
HTML
89 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Programming considerations for a distributed relational database application" />
|
||
|
|
<meta name="abstract" content="Programming considerations for a distributed relational database application on an iSeries server fall into two main categories: those that deal with a function that is supported on the local server and those that are a result of having to connect to other servers." />
|
||
|
|
<meta name="description" content="Programming considerations for a distributed relational database application on an iSeries server fall into two main categories: those that deal with a function that is supported on the local server and those that are a result of having to connect to other servers." />
|
||
|
|
<meta name="DC.subject" content="programming considerations, for a Distributed Relational Database application, considerations, application programming, Distributed Relational Database application, considerations for a Distributed Relational Database, programming considerations" />
|
||
|
|
<meta name="keywords" content="programming considerations, for a Distributed Relational Database application, considerations, application programming, Distributed Relational Database application, considerations for a Distributed Relational Database, programming considerations" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1program.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1naming.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1cnct.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1sdd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1enddrda.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1spucc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1ccsid.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1dtrans.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1ddmsql.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1appcons.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="rbal1progdrd" />
|
||
|
|
<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>Programming considerations for a distributed relational database application</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1progdrd"><a name="rbal1progdrd"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Programming considerations for a distributed relational database application</h1>
|
||
|
|
<div><p>Programming considerations for a distributed relational database
|
||
|
|
application on an <span class="keyword">iSeries™ server</span> fall
|
||
|
|
into two main categories: those that deal with a function that
|
||
|
|
is supported on the local server and those that are a result of having to
|
||
|
|
connect to other servers. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1naming.htm">Naming of distributed relational database objects</a></strong><br />
|
||
|
|
SQL objects are created and maintained as <span class="keyword">iSeries server</span> objects.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1cnct.htm">Connect to a distributed relational database</a></strong><br />
|
||
|
|
What makes a distributed relational database application <em>distributed</em> is
|
||
|
|
its ability to connect to a relational database on another server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1sdd.htm">SQL specific to distributed relational database and SQL CALL</a></strong><br />
|
||
|
|
During the precompile process of a distributed <span class="keyword">DB2 Universal Database™ for iSeries</span> application,
|
||
|
|
the <span class="keyword">i5/OS™</span> licensed program
|
||
|
|
might build SQL packages to be run on an application server (AS). </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1enddrda.htm">End DRDA units of work</a></strong><br />
|
||
|
|
You should be careful about ending SQL programs with uncommitted work. When a program ends with uncommitted work, the connection to the relational database remains active.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1spucc.htm">Stored procedures, user-defined functions, and commitment control</a></strong><br />
|
||
|
|
When an application such as Interactive SQL is running without
|
||
|
|
commitment control active (COMMIT(*NONE)) over a DRDA<sup>®</sup> connection, it is possible for an
|
||
|
|
invoked stored procedure or user-defined function (UDF) to start commitment
|
||
|
|
control on an iSeries server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1ccsid.htm">Coded character set identifier</a></strong><br />
|
||
|
|
Support for the national language of any country requires the proper handling of a minimum set of characters.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1dtrans.htm">Other DRDA data conversion</a></strong><br />
|
||
|
|
Sometimes, when you are doing processing on a remote system, your
|
||
|
|
program might need to convert the data from one system so that it can be used
|
||
|
|
on the other. Distributed
|
||
|
|
Relational Database Architecture™ (DRDA<sup>®</sup>) support on the <span class="keyword">iSeries server</span> converts
|
||
|
|
the data automatically between other systems that use DRDA<sup>®</sup> support. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1ddmsql.htm">DDM files and SQL</a></strong><br />
|
||
|
|
You can use <span class="keyword">iSeries</span> distributed
|
||
|
|
data management (DDM) support to help you do some distributed relational database
|
||
|
|
tasks within a program that also uses SQL distributed relational database
|
||
|
|
support.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1program.htm" title="Programmers can write high-level language programs that use SQL statements for iSeries distributed application programs.">Application development</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbal1appcons.htm" title="Distributed relational database applications have different requirements from applications developed solely for use on a local database.">Tips: Design distributed relational database applications</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|