87 lines
6.7 KiB
HTML
87 lines
6.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="Considerations for creating an SQL package" />
|
||
|
|
<meta name="abstract" content="There are many considerations to think about when you are creating an SQL package." />
|
||
|
|
<meta name="description" content="There are many considerations to think about when you are creating an SQL package." />
|
||
|
|
<meta name="DC.subject" content="distributed relational database, consideration for creating packages, creating packages" />
|
||
|
|
<meta name="keywords" content="distributed relational database, consideration for creating packages, creating packages" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypacksupport.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider5.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider6.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider7.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider8.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider9.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider10.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider11.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider12.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafypackconsider13.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="rbafysqlpack2" />
|
||
|
|
<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>Considerations for creating an SQL package</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafysqlpack2"><a name="rbafysqlpack2"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Considerations for creating an SQL package</h1>
|
||
|
|
<div><p>There are many considerations to think about when you are creating
|
||
|
|
an SQL package.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider1.htm">CRTSQLPKG authorization</a></strong><br />
|
||
|
|
When you create an SQL package on an <span class="keyword">iSeries™</span> system,
|
||
|
|
the authorization ID used must have *USE authority to the CRTSQLPKG command.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider2.htm">Create a package on a non-DB2 UDB for iSeries</a></strong><br />
|
||
|
|
When you create a program and SQL package for a non-<span class="keyword">DB2<sup>®</sup> UDB for iSeries™</span>,
|
||
|
|
and try to use SQL statements that are unique to that relational database,
|
||
|
|
the CRTSQLxxx GENLVL parameter should be set to 30.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider3.htm">Target release (TGTRLS) parameter</a></strong><br />
|
||
|
|
While creating the package, the SQL statements are checked to determine which release can support the function.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider4.htm">SQL statement size</a></strong><br />
|
||
|
|
The create SQL package function may not be able to handle the same size SQL statement that the precompiler can process.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider5.htm">Statements that do not require a package</a></strong><br />
|
||
|
|
In some cases, you might try to create an SQL package but the SQL package is created and the program still runs. This situation occurs when the program contains only SQL statements that do not require an SQL package to run.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider6.htm">Package object type</a></strong><br />
|
||
|
|
SQL packages are always created as non-ILE objects and always run in the default activation group.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider7.htm">ILE programs and service programs</a></strong><br />
|
||
|
|
ILE programs and service programs that bind several modules containing SQL statements must have a separate SQL package for each module.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider8.htm">Package creation connection</a></strong><br />
|
||
|
|
The type of connection done for the package creation is based on the type of connect requested using the RDBCNNMTH parameter.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider9.htm">Unit of work</a></strong><br />
|
||
|
|
Because package creation implicitly performs a commit or rollback, the commit definition must be at a unit of work boundary before the package creation is attempted.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider10.htm">Create packages locally</a></strong><br />
|
||
|
|
The name specified on the RDB parameter can be the name of the local system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider11.htm">Labels</a></strong><br />
|
||
|
|
You can use the LABEL ON statement to create a description for the SQL package.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider12.htm">Consistency token</a></strong><br />
|
||
|
|
The program and its associated SQL package contain a consistency token that is checked when a call is made to the SQL package.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafypackconsider13.htm">SQL and recursion</a></strong><br />
|
||
|
|
If you start SQL from an attention key program while you are already precompiling, you will receive unpredictable results.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafypacksupport.htm" title="The operating system supports an object called an SQL package. The object type is *SQLPKG.">SQL package support</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|