88 lines
6.2 KiB
HTML
88 lines
6.2 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="SQLJ procedures that manipulate JAR files" />
|
||
|
|
<meta name="abstract" content="Both Java stored procedures and Java UDFs can use Java classes that are stored in Java JAR files." />
|
||
|
|
<meta name="description" content="Both Java stored procedures and Java UDFs can use Java classes that are stored in Java JAR files." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="jsqlrout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="jsqlover.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="javaproc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="writeudf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="udfparam.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="sqljinst.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="sqljremv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="sqljrplc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="sqljupdt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="sqljrcvr.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="sqljrfc.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="sqljjar" />
|
||
|
|
<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>SQLJ procedures that manipulate JAR files</title>
|
||
|
|
</head>
|
||
|
|
<body id="sqljjar"><a name="sqljjar"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">SQLJ procedures that manipulate JAR files</h1>
|
||
|
|
<div><p>Both Java™ stored procedures and Java UDFs can use Java classes
|
||
|
|
that are stored in Java JAR files. </p>
|
||
|
|
<p>To use a JAR file, a <em>jar-id</em> must be associated with the JAR file.
|
||
|
|
The system provides stored procedures in the SQLJ schema that allow <em>jar-ids</em> and
|
||
|
|
JAR files to be manipulated. These procedures allow JAR files to be installed,
|
||
|
|
replaced, and removed. They also provide the ability to use and update the
|
||
|
|
SQL catalogs associated with JAR files.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="sqljinst.htm">SQLJ.INSTALL_JAR</a></strong><br />
|
||
|
|
The SQLJ.INSTALL_JAR stored procedure installs a JAR file into the database system. This JAR file can be used in subsequent CREATE FUNCTION and CREATE PROCEDURE statements.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="sqljremv.htm">SQLJ.REMOVE_JAR</a></strong><br />
|
||
|
|
The SQLJ.REMOVE_JAR stored procedure removes a JAR file from the database system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="sqljrplc.htm">SQLJ.REPLACE_JAR</a></strong><br />
|
||
|
|
</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="sqljupdt.htm">SQLJ.UPDATEJARINFO</a></strong><br />
|
||
|
|
The SQLJ.UPDATEJARINFO updates the CLASS_SOURCE column of the SYSJARCONTENTS
|
||
|
|
catalog table. This procedure is not part of the SQLJ standard but is used
|
||
|
|
by the DB2<sup>®</sup> UDB
|
||
|
|
for iSeries™ stored
|
||
|
|
procedure builder.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="sqljrcvr.htm">SQLJ.RECOVERJAR</a></strong><br />
|
||
|
|
The SQLJ.RECOVERJAR procedure takes the JAR file that is stored
|
||
|
|
in the SYSJAROBJECTS catalog and restores it to the /QIBM/UserData/OS400/SQLLib/Function/jar/<em>jarschema</em>/<em>jar_id</em>.jar
|
||
|
|
file.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="sqljrfc.htm">SQLJ.REFRESH_CLASSES</a></strong><br />
|
||
|
|
The SQLJ.REFRESH_CLASSES stored procedure causes the reloading
|
||
|
|
of user defined classes used by Java stored procedures or Java UDFs
|
||
|
|
in the current database connection. This stored procedure must be called
|
||
|
|
by existing database connections to obtain changes made by a call to the SQLJ.REPLACE_JAR
|
||
|
|
stored procedure.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="jsqlrout.htm" title="Your iSeries server provides the ability to access Java programs from SQL statements and programs. This can be done using Java stored procedures and Java user-defined functions (UDFs). The iSeries server supports both the DB2 and SQLJ conventions for calling Java stored procedures and Java UDFs. Both Java stored procedures and Java UDFs can use Java classes that are stored in JAR files. The iSeries server uses stored procedures defined by the SQLJ Part 1 standard to register JAR files with the database.">Java SQL routines</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="javaproc.htm" title="When using Java to write stored procedures, you can use two possible parameter passing styles.">Java stored procedures</a></div>
|
||
|
|
<div><a href="writeudf.htm" title="A Java scalar function returns one value from a Java program to the database. For example, a scalar function could be created that returns the sum of two numbers.">Java user-defined scalar functions</a></div>
|
||
|
|
<div><a href="udfparam.htm" title="The following table lists how SQL data types are represented in Java stored procedures and UDFs.">Parameter passing conventions for Java stored procedures and UDFs</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="jsqlover.htm" title="You can access Java programs from SQL statements and programs. This can be done using Java stored procedures and Java user-defined functions (UDFs).">Use Java SQL routines</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|