52 lines
3.7 KiB
HTML
52 lines
3.7 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="Stored procedures, user-defined functions, and commitment control" />
|
||
|
|
<meta name="abstract" content="When an application such as Interactive SQL is running without commitment control active (COMMIT(*NONE)) over a DRDA connection, it is possible for an invoked stored procedure or user-defined function (UDF) to start commitment control on an iSeries server." />
|
||
|
|
<meta name="description" content="When an application such as Interactive SQL is running without commitment control active (COMMIT(*NONE)) over a DRDA connection, it is possible for an invoked stored procedure or user-defined function (UDF) to start commitment control on an iSeries server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1progdrd.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="rbal1spucc" />
|
||
|
|
<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>Stored procedures, user-defined functions, and commitment control</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1spucc"><a name="rbal1spucc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Stored procedures, user-defined functions, and commitment control</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"><p>This results in a mismatch in commitment control between the client
|
||
|
|
and the server, causing the possibility of uncommitted updates when the application
|
||
|
|
terminates.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>You should avoid this situation. If, however, you choose to implement
|
||
|
|
it, one solution is for the stored procedure or UDF running under commitment
|
||
|
|
control to explicitly commit all of its database updates. If that is not done,
|
||
|
|
the server will detect the pending updates during the disconnection process
|
||
|
|
and automatically commit the pending work.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1progdrd.htm" title="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.">Programming considerations for a distributed relational database application</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|