ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaha_5.4.0.1/sqljcr.htm

97 lines
8.0 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="task" />
<meta name="DC.Title" content="Compile and run SQLJ programs" />
<meta name="abstract" content="If you Java program has embedded SQLJ statements, you need to follow a special procedure to compile and run it." />
<meta name="description" content="If you Java program has embedded SQLJ statements, you need to follow a special procedure to compile and run it." />
<meta name="DC.Relation" scheme="URI" content="sqljembd.htm#sqljembd" />
<meta name="DC.Relation" scheme="URI" content="sqljintr.htm" />
<meta name="DC.Relation" scheme="URI" content="sqljprof.htm" />
<meta name="DC.Relation" scheme="URI" content="sqlj.htm" />
<meta name="DC.Relation" scheme="URI" content="sqljdbpc.htm" />
<meta name="DC.Relation" scheme="URI" content="sqljdbpp.htm" />
<meta name="DC.Relation" scheme="URI" content="sqljpdb.htm" />
<meta name="DC.Relation" scheme="URI" content="sqljpc.htm" />
<meta name="DC.Relation" scheme="URI" content="sqljembd.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="sqljcr" />
<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>Compile and run SQLJ programs</title>
</head>
<body id="sqljcr"><a name="sqljcr"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Compile and run SQLJ programs</h1>
<div><p>If you Java™ program has embedded SQLJ statements, you need
to follow a special procedure to compile and run it.</p>
<div class="section"><p>If your Java program has <a href="sqljembd.htm">embedded
SQLJ</a> statements, you need to follow a special procedure to compile
and run it. </p>
</div>
<ol><li class="stepexpand"><span><a href="sqljsetup.htm">Set up your server to use SQLJ.</a></span></li>
<li class="stepexpand"><span>Use the <a href="sqlj.htm">SQLJ translator, <samp class="codeph">sqlj</samp></a>,
on your Java source code with embedded SQL to generate Java source
code and associated <a href="sqljprof.htm">profiles</a>. There is one
profile generated for each connection.</span> <p>For example, type in
the following command:</p>
<pre> sqlj <em>MyClass.sqlj</em></pre>
where <em>MyClass.sqlj</em> is the name of your SQLJ file. <p>In this
example, the SQLJ translator generates a MyClass.java source code file and
any associated profiles. The associated profiles are named MyClass_SJProfile0.ser,
MyClass_SJProfile1.ser, MyClass_SJProfile2.ser, and so on.</p>
<div class="note"><span class="notetitle">Note:</span> The SQLJ
translator automatically compiles the translated Java source code into a class file unless
you explicitly turn off the compile option with the <samp class="codeph">-compile=false</samp> clause.</div>
</li>
<li class="stepexpand"><span>Use <a href="sqljdbpc.htm">the SQLJ Profile Customizer tool, <samp class="codeph">db2profc</samp></a>,
to install DB2<sup>®</sup> SQLJ
Customizers on generated profiles and create the DB2 packages on the local system.</span> <p>For example, type in the command:</p>
<pre> db2profc <em>MyClass_SJProfile0.ser</em></pre>
where <em>MyClass_SJProfile0.ser</em> is the name of the profile on which
the DB2 SQLJ
Customizer is run. <div class="note"><span class="notetitle">Note:</span> This step is optional but is recommended to
increase runtime performance.</div>
</li>
<li class="stepexpand"><span>Run the Java class file just like any other Java class
file.</span> <p>For example, type in the command:</p>
<pre> java <em>MyClass</em></pre>
where <em>MyClass</em> is the name of your Java class file. </li>
</ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="sqljintr.htm" title="DB2 Structured Query Language for Java (SQLJ) support is based on the SQLJ ANSI standard. The DB2 SQLJ support is contained in the IBM Developer Kit for Java. DB2 SQLJ support allows you to create, build, and run embedded SQL for Java applications.">Access databases using IBM Developer Kit for Java DB2 SQLJ support</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="sqljprof.htm" title="Profiles are generated by the SQLJ Translator, sqlj, when you translate the SQLJ source file. Profiles are serialized binary files. That is why these files have a .ser extension. These files contain the SQL statements from the associated SQLJ source file.">Structured Query Language for Java profiles</a></div>
<div><a href="sqlj.htm" title="The SQLJ translator, sqlj, generates a serialized profile containing information about the SQL operations found in the SQLJ program. The SQLJ translator uses the /QIBM/ProdData/Java400/ext/translator.zip file.">The structured query language for Java (SQLJ) translator (sqlj)</a></div>
<div><a href="sqljdbpc.htm" title="You can use the DB2 SQLJ Profile Customizer, db2profc, to make your Java application work more efficiently with your database.">Precompile SQL statements in a profile using the DB2 SQLJ profile customizer, db2profc</a></div>
<div><a href="sqljdbpp.htm" title="The DB2 SQLJ Profile Printer, db2profp, prints the contents of a DB2 customized profile in plain text. The Profile Printer, profp, prints the contents of profiles generated by the SQLJ translator in plain text.">Print the contents of DB2 SQLJ profiles (db2profp and profp)</a></div>
<div><a href="sqljpdb.htm" title="The SQLJ profile auditor installer (profdb) installs and uninstalls debugging class-auditors. The debugging class-auditors are installed into an existing set of binary profiles. Once the debugging class-auditors are installed, all RTStatement and RTResultSet calls made during application run time are logged. They can be logged to a file or standard output. The logs can then be inspected to verify the behavior and trace errors of the application. Note that only the calls made to the underlying RTStatement and RTResultSetcall interface at run time are audited.">SQLJ profile auditor installer (profdb)</a></div>
<div><a href="sqljembd.htm" title="Static SQL statements in SQLJ are in SQLJ clauses. SQLJ clauses begin with #sql and end with a semicolon (;) character.">Embed SQL statements in your Java application</a></div>
<div><a href="sqljembd.htm#sqljembd" title="Static SQL statements in SQLJ are in SQLJ clauses. SQLJ clauses begin with #sql and end with a semicolon (;) character.">Embed SQL statements in your Java application</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="sqljpc.htm" title="The SQLJ profile conversion tool (profconv) converts a serialized profile instance to Java class format. The profconv tool is needed because some browsers do not support loading a serialized object from a resource file that is associated with an applet. Run the profconv utility to perform the conversion.">Convert a serialized profile instance to Java class format using the SQLJ profile conversion tool (profconv)</a></div>
</div>
</div>
</body>
</html>