89 lines
6.4 KiB
HTML
89 lines
6.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 management and activation groups" />
|
|
<meta name="abstract" content="SQL connections are managed at the activation group level. Each activation group within a job manages its own connections and these connections are not shared across activation groups." />
|
|
<meta name="description" content="SQL connections are managed at the activation group level. Each activation group within a job manages its own connections and these connections are not shared across activation groups." />
|
|
<meta name="DC.subject" content="activation groups, connection management, example, examples, distributed relational database, commitment control, activation group" />
|
|
<meta name="keywords" content="activation groups, connection management, example, examples, distributed relational database, commitment control, activation group" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydrda.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydrdasourcecode.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydrdapgm2.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydrdapgm3.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydrdamulti.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyc1.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyc2.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="rbafyconnectmgmt" />
|
|
<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 management and activation groups</title>
|
|
</head>
|
|
<body id="rbafyconnectmgmt"><a name="rbafyconnectmgmt"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Connection management and activation groups</h1>
|
|
<div><p>SQL connections are managed at the activation group level. Each
|
|
activation group within a job manages its own connections and these connections
|
|
are not shared across activation groups.</p>
|
|
<div class="section"><p>Before the use of TCP/IP by DRDA<sup>®</sup>, the term <dfn class="term">connection</dfn> was
|
|
not ambiguous. It referred to a connection from the SQL point of view. That
|
|
is, a connection started at the time one did a CONNECT TO some RDB, and ended
|
|
when a DISCONNECT was done or a RELEASE ALL followed by a successful COMMIT
|
|
occurred. The APPC conversation may or may not have been kept up, depending
|
|
on the job's DDMCNV attribute value, and whether the conversation was with
|
|
an <span class="keyword">iSeries™</span> or other type of
|
|
system.</p>
|
|
<p>TCP/IP terminology does not include the term <dfn class="term">conversation</dfn>.
|
|
A similar concept exists, however. With the advent of TCP/IP support by DRDA,
|
|
use of the term <dfn class="term">conversation</dfn> is replaced, in this topic, by the
|
|
more general term <dfn class="term">connection</dfn>, unless the discussion is specifically
|
|
about an APPC conversation. Therefore, there are now two different types of
|
|
connections about which the reader must be aware: SQL connections of the type
|
|
described above, and network connections which replace the term <dfn class="term">conversation</dfn>. </p>
|
|
<p>Where
|
|
there might be the possibility of confusion between the two types of connections,
|
|
the word will be qualified by SQL or network to help the reader to understand
|
|
the intended meaning.</p>
|
|
</div>
|
|
<div class="section"><p>The following is an example of an application that runs in multiple
|
|
activation groups. This example is used to illustrate the interaction between
|
|
activation groups, connection management, and commitment control. It is <strong>not</strong> a
|
|
recommended coding style.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbafydrdasourcecode.htm">Source code for PGM1</a></strong><br />
|
|
Here is the source code for PGM1.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafydrdapgm2.htm">Source code for PGM2</a></strong><br />
|
|
Here is the source code for PGM2.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafydrdapgm3.htm">Source code for PGM3</a></strong><br />
|
|
Here is the source code for PGM3.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafydrdamulti.htm">Multiple connections to the same relational database</a></strong><br />
|
|
If different activation groups connect to the same relational database, each SQL connection has its own network connection and its own application server job.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafyc1.htm">Implicit connection management for the default activation group</a></strong><br />
|
|
The application requester can implicitly connect to an application server.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafyc2.htm">Implicit connection management for nondefault activation groups</a></strong><br />
|
|
The application requester can implicitly connect to an application server. Implicit SQL connection occurs when the application requester detects that the first SQL statement issued for the activation group is not a CONNECT statement with parameters.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafydrda.htm" title="A distributed relational database consists of a set of SQL objects that are spread across interconnected computer systems.">Distributed relational database function and SQL</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |