ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzajq_5.4.0.1/retcurs.htm

75 lines
5.6 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Retaining cursor positions for non-ILE program calls" />
<meta name="abstract" content="For non-ILE program calls, the close SQL cursor (CLOSQLCSR) parameter allows you to specify the scope of the following:" />
<meta name="description" content="For non-ILE program calls, the close SQL cursor (CLOSQLCSR) parameter allows you to specify the scope of the following:" />
<meta name="DC.subject" content="improving performance, using, close SQL cursor (CLOSQLCSR), improving performance, retaining cursor positions across program call, retaining cursor positions, across program call, performance improvement, retaining cursor positions across program call, cursor, positions, retaining across program call, rules for retaining, using to improve performance, parameters, command, CLOSQLCSR (close SQL cursor), precompiler command, default" />
<meta name="keywords" content="improving performance, using, close SQL cursor (CLOSQLCSR), improving performance, retaining cursor positions across program call, retaining cursor positions, across program call, performance improvement, retaining cursor positions across program call, cursor, positions, retaining across program call, rules for retaining, using to improve performance, parameters, command, CLOSQLCSR (close SQL cursor), precompiler command, default" />
<meta name="DC.Relation" scheme="URI" content="retaincursors.htm" />
<meta name="DC.Relation" scheme="URI" content="precompileopts.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="retcurs" />
<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>Retaining cursor positions for non-ILE program calls</title>
</head>
<body id="retcurs"><a name="retcurs"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Retaining cursor positions for non-ILE program calls</h1>
<div><p>For non-ILE program calls, the close SQL cursor (CLOSQLCSR) parameter
allows you to specify the scope of the following: </p>
<div class="section"><ul><li>The cursors</li>
<li>The prepared statements</li>
<li>The locks</li>
</ul>
</div>
<div class="section"><p>When used properly, the CLOSQLCSR parameter can reduce the number
of SQL OPEN, PREPARE, and LOCK statements needed. It can also simplify applications
by allowing you to retain cursor positions across program calls. </p>
<dl><dt class="dlterm"><u><strong>*ENDPGM</strong></u></dt>
<dd>This is the default for all non-ILE precompilers. With this option, a
cursor remains open and accessible only while the program that opened it is
on the call stack. When the program ends, the SQL cursor can no longer be
used. Prepared statements are also lost when the program ends. Locks, however,
remain until the last SQL program on the call stack has completed.</dd>
<dt class="dlterm">*ENDSQL</dt>
<dd>With this option, SQL cursors and prepared statements that are created
by a program remain open until the last SQL program on the call stack has
completed. They cannot be used by other programs, only by a different call
to the same program. Locks remain until the last SQL program in the call stack
completes.</dd>
<dt class="dlterm">*ENDJOB</dt>
<dd>This option allows you to keep SQL cursors, prepared statements, and locks
active for the duration of the job. When the last SQL program on the stack
has completed, any SQL resources created by *ENDJOB programs are still active.
The locks remain in effect. The SQL cursors that were not explicitly closed
by the CLOSE, COMMIT, or ROLLBACK statements remain open. The prepared statements
are still usable on subsequent calls to the same program.</dd>
</dl>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="retaincursors.htm" title="You can improve performance by retaining cursor positions.">Retain cursor positions</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="precompileopts.htm" title="Several precompile options are available for creating SQL programs with improved performance. They are only options because using them may impact the function of the application. For this reason, the default value for these parameters is the value that will ensure successful migration of applications from prior releases. However, you can improve performance by specifying other options.">Effects of precompile options on database performance</a></div>
</div>
</div>
</body>
</html>