73 lines
5.4 KiB
HTML
73 lines
5.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="concept" />
|
|
<meta name="DC.Title" content="Factors that affect blocking for DRDA" />
|
|
<meta name="abstract" content="A very important performance factor is whether blocking occurs when data is transferred between the application requester (AR) and the application server (AS). A group of rows transmitted as a block of data requires much less communications overhead than the same data sent one row at a time." />
|
|
<meta name="description" content="A very important performance factor is whether blocking occurs when data is transferred between the application requester (AR) and the application server (AS). A group of rows transmitted as a block of data requires much less communications overhead than the same data sent one row at a time." />
|
|
<meta name="DC.subject" content="factors that affect blocking, blocking, factors that affect, performance, factors affecting" />
|
|
<meta name="keywords" content="factors that affect blocking, blocking, factors that affect, performance, factors affecting" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1improveviadata.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1block1.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1block2.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1block3.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1blocksummary.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1appnotcomp.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="rbal1facblk" />
|
|
<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>Factors that affect blocking for DRDA</title>
|
|
</head>
|
|
<body id="rbal1facblk"><a name="rbal1facblk"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Factors that affect blocking for DRDA<sup>®</sup></h1>
|
|
<div><p>A very important performance factor is whether blocking occurs
|
|
when data is transferred between the application requester (AR) and the application
|
|
server (AS). A group of rows transmitted as a block of data requires much
|
|
less communications overhead than the same data sent one row at a time.</p>
|
|
<p>One way to control blocking when connected to another <span class="keyword">iSeries™ server</span> is
|
|
to use the SQL multiple-row INSERT and multiple-row FETCH statements. The
|
|
multiple-row FETCH forces the blocking of the number of rows specified in
|
|
the FOR n ROWS clause, unless a hard error or end of data is encountered.
|
|
The following discussion gives rules for determining if blocking will occur
|
|
for single-row FETCHs.</p>
|
|
<p>Conditions that inhibit the blocking of query data between the AR and the
|
|
AS are also listed in the following discussion. These conditions do not apply
|
|
to the use of the multiple-row FETCH statement. Any condition listed under
|
|
each of the following cases is sufficient to prevent blocking.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbal1block1.htm">DB2 Universal Database for iSeries to DB2 Universal Database for iSeries blocking</a></strong><br />
|
|
</li>
|
|
<li class="ulchildlink"><strong><a href="rbal1block2.htm">DB2 Universal Database for iSeries to non-DB2 Universal Database for iSeries blocking</a></strong><br />
|
|
</li>
|
|
<li class="ulchildlink"><strong><a href="rbal1block3.htm">Non-DB2 Universal Database for iSeries to DB2 Universal Database for iSeries blocking</a></strong><br />
|
|
</li>
|
|
<li class="ulchildlink"><strong><a href="rbal1blocksummary.htm">Summarization of DRDA blocking rules</a></strong><br />
|
|
</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1improveviadata.htm" title="Distributed relational database performance is affected by the overall design of the database. The location of distributed data, the level of commitment control you use, and the design of your SQL indexes all affect performance.">Improve distributed relational database performance through the database</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rbal1appnotcomp.htm" title="If the request takes longer than expected to complete, the first place to check is at the application requester (AR).">Application does not complete in the expected time</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |