ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahh_5.4.0.1/jarfilelist.htm

263 lines
17 KiB
HTML
Raw Permalink 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="Jar files" />
<meta name="abstract" content="The IBM Toolbox for Java is shipped as a set of jar files. Each jar file contains Java packages that provide specific functions. You can reduce the amount of required storage space by using only the jar files required to enable the specific functions that you want." />
<meta name="description" content="The IBM Toolbox for Java is shipped as a set of jar files. Each jar file contains Java packages that provide specific functions. You can reduce the amount of required storage space by using only the jar files required to enable the specific functions that you want." />
<meta name="DC.Relation" scheme="URI" content="rzahnm09.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="jarfilelist" />
<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>Jar files</title>
</head>
<body id="jarfilelist"><a name="jarfilelist"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Jar files</h1>
<div><p>The IBM<sup>®</sup> Toolbox
for Java™ is
shipped as a set of jar files. Each jar file contains Java packages
that provide specific functions. You can reduce the amount of required storage
space by using only the jar files required to enable the specific functions
that you want.</p>
<div class="section"><p></p>
<p>To use a jar file, make sure that you include an entry
for it in your CLASSPATH.</p>
<p>The following chart indicates which jar files
you must add to your CLASSPATH to use the associated function or package.</p>
<div class="p">
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><thead align="left"><tr class="tablemainheaderbar"><th valign="top" width="50%" id="d0e34">IBM Toolbox
for Java package
or function</th>
<th valign="top" width="50%" id="d0e41">Jar files required to be in your CLASSPATH</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="50%" headers="d0e34 "><a href="classes.htm#classes">Access classes</a> </td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a>, or jt400Proxy.jar in a proxy environment</td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="rzahhcmdhelpretriever.htm">CommandHelpRetriever class</a></td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note 1</sup></a> and an XML parser
and XSLT processor <a href="#jarfilelist__xpcml"><sup>Note 2</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="cmdprmptr.htm#cmdprmptr">CommandPrompter</a> <sup> <a href="#jarfilelist__cmdprmptrnote">Note 3</a></sup></td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar, jui400.jar, util400.jar <sup> <a href="#jarfilelist__util400">Note
4</a></sup>, and an XML parser <a href="#jarfilelist__xpcml"><sup>Note
2</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">Commtrace classes</td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note 1</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="html.htm#html">HTML classes</a> </td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar <a href="#jarfilelist__jt400classic"><sup>Note 1</sup></a> plus
jt400Servlet.jar (client), or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="htmldocument.htm">HTMLDocument
class</a></td>
<td valign="top" width="50%" headers="d0e41 ">The same jars required for HTML classes, plus an XML
parser and XSLT processor <a href="#jarfilelist__xpcml"><sup>Note 2</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">JCA classes</td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note 1</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">JDBC Data Source GUI</td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a> and jui400.jar<a href="#jarfilelist__jui400"><sup>Note 5</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">NLS system and error messages</td>
<td valign="top" width="50%" headers="d0e41 ">jt400Mri_lang_cntry.jar <a href="#jarfilelist__jt400mrinn"><sup>Note
6</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">PCML (development and run-time, parsed) <sup> <a href="#jarfilelist__pcmlnote">Note
7</a></sup></td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a>, <sup> <a href="#jarfilelist__jt400pcml">Note 8</a></sup>,
and an XML parser <a href="#jarfilelist__xpcml"><sup>Note 2</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">PCML (run-time, serialized)</td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a>, <sup> <a href="#jarfilelist__jt400pcml">Note 8</a></sup></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">PDML (development) <sup> <a href="#jarfilelist__cmdprmptrnote">Note
3</a></sup></td>
<td valign="top" width="50%" headers="d0e41 ">uitools.jar, jui400.jar, util400.jar <sup> <a href="#jarfilelist__util400">Note
4</a></sup>, and an XML parser <a href="#jarfilelist__xpcml"><sup>Note
2</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">PDML (run-time, parsed) <sup> <a href="#jarfilelist__cmdprmptrnote">Note
3</a></sup></td>
<td valign="top" width="50%" headers="d0e41 ">jui400.jar, util400.jar <sup> <a href="#jarfilelist__util400">Note
4</a></sup>, and an XML parser <a href="#jarfilelist__xpcml"><sup>Note
2</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 ">PDML (run-time, serialized) <sup> <a href="#jarfilelist__cmdprmptrnote">Note
3</a></sup></td>
<td valign="top" width="50%" headers="d0e41 ">jui400.jar, and util400.jar <sup> <a href="#jarfilelist__util400">Note
4</a></sup></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="reportwriter.htm#reportwriter">ReportWriter classes</a></td>
<td align="left" valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a>, reportwriter jars <sup><a href="#jarfilelist__reportwriternote">Note
9</a></sup>, and an XML parser and XSLT processor <a href="#jarfilelist__xpcml"><sup>Note
2</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="resources.htm#resources">Resource classes</a></td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="rfmlmain.htm#rfmlmain">RFML</a></td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a>, and an XML parser <a href="#jarfilelist__xpcml"><sup>Note
2</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="security.htm#security">Security classes</a></td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a>, or jt400Proxy.jar in a proxy environment</td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="servlets.htm#servlets">Servlet classes</a> </td>
<td valign="top" width="50%" headers="d0e41 "> jt400.jar <a href="#jarfilelist__jt400classic"><sup>Note 1</sup></a> plus
jt400Servlet.jar (client), or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="../rzamq/rzamqmain.htm">iSeries™ System
Debugger</a> <sup> <a href="#jarfilelist__cmdprmptrnote">Note 3</a></sup></td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a> and tes.jar</td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="micromain.htm#micromain">ToolboxME for iSeries</a></td>
<td valign="top" width="50%" headers="d0e41 ">jt400Micro.jar (client) <a href="#jarfilelist__jt400micro"><sup>Note
10</sup></a> and jt400.jar (server) or jt400Native.jar (server)<a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="vaccess.htm#vaccess">Vaccess classes</a> </td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) <a href="#jarfilelist__jt400classic"><sup>Note
1</sup></a></td>
</tr>
<tr><td valign="top" width="50%" headers="d0e34 "><a href="rzahhxpcmlmain.htm#rzahhxpcmlmain">XPCML</a></td>
<td valign="top" width="50%" headers="d0e41 ">jt400.jar (client) or jt400Native.jar (server) <a href="#jarfilelist__jt400classic"><sup>Note 1</sup></a>, and an XML parser
and XSLT processor <a href="#jarfilelist__xpcml"><sup>Note 2</sup></a></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="section" id="jarfilelist__jt400classic"><a name="jarfilelist__jt400classic"><!-- --></a><p><strong>Note 1:</strong> Some of the IBM Toolbox for Java classes
are in more than one jar file:</p>
<ul><li><strong>jt400.jar</strong> - Access, commtrace, JCA, JDBC support, MEServer,
PCML, resource, RFML, security, utilities, vaccess, and XPCML.</li>
<li><strong>jt400.zip</strong> - Use jt400.jar instead of jt400.zip. jt400.zip is shipped
to retain compatibility with previous releases of IBM Toolbox for Java.</li>
<li><strong>jt400Access.zip</strong> - The same classes that are in jt400.jar minus
the vaccess classes. jtAccess400.zip is shipped to retain compatibility with
previous releases of IBM Toolbox for Java. Use jt400.jar or jt400Native.jar instead
of jt400Access.zip.</li>
<li><strong>jt400Native.jar</strong> - Access, HTML, MEServer, PCML, resource,
RFML, security, XPCML, and <a href="rzahnm0503.htm#rzahnm0503">native
optimizations</a>. Native optimizations is a set of classes (fewer than
20) that take advantage of iSeries function when running on the iSeries JVM.
Because jt400Native.jar contains the native optimizations, when running on
the the iSeries JVM,
use jt400Native.jar instead of jt400.jar. jt400Native.jar ships with i5/OS™ and resides
in directory /QIBM/ProdData/OS400/jt400/lib.</li>
<li><img src="./delta.gif" alt="Start of change" /><strong>jt400Native11x.jar</strong> - Use jt400Native.jar instead of
jt400Native11x.jar. jt400Native11x.jar is shipped to retain compatibility
with previous releases of IBM Toolbox for Java.<img src="./deltaend.gif" alt="End of change" /></li>
</ul>
</div>
<div class="section" id="jarfilelist__xpcml"><a name="jarfilelist__xpcml"><!-- --></a><p><strong>Note 2:</strong> When you must use an XML
parser or XSLT processor, make sure that they are JAXP-compliant. For more
information, see the following page:</p>
<blockquote><a href="rzahhxmlparserxslprocessor.htm">XML parser and XSLT processor</a></blockquote>
</div>
<div class="section" id="jarfilelist__cmdprmptrnote"><a name="jarfilelist__cmdprmptrnote"><!-- --></a><p><strong>Note 3:</strong> Using CommandPrompter, PDML,
or the iSeries System
Debugger also requires one additional jar file that is not part of IBM Toolbox for Java:
jhall.jar. For more information about downloading jhall.jar, see the <a href="http://java.sun.com/products/javahelp/index.html" target="_blank">Sun
JavaHelp<sup>(TM)</sup></a> Web site <img src="www.gif" alt="Link outside Information Center" />.</p>
</div>
<div class="section" id="jarfilelist__util400"><a name="jarfilelist__util400"><!-- --></a><p><strong>Note 4:</strong> util400.jar contains iSeries-specific
classes for formatting input and for using the command line prompter. Using
the CommandPrompter class requires util400.jar. Using PDML does not require
util400.jar, but it is useful.</p>
</div>
<div class="section" id="jarfilelist__jui400"><a name="jarfilelist__jui400"><!-- --></a><p><strong>Note 5:</strong> jui400.jar contains the classes necessary
to use the JDBC DataSource GUI interface. jt400.jar ( <a href="#jarfilelist__jt400classic">
Note 1</a>) contains the classes necessary for all other JDBC functions.</p>
</div>
<div class="section" id="jarfilelist__jt400mrinn"><a name="jarfilelist__jt400mrinn"><!-- --></a><p><strong>Note 6:</strong> jt400Mri_xx_yy.jar contains translated
messages, including strings contained in exception messages, dialogs, and
output from other normal processing. In jt400Mri_lang_cntry.jar, lang = the
ISO Language Code and cntry = the ISO Country or Region Code used to translate
the contained text. In some cases, the ISO Country or Region Code is not used.
Installing a particular national language version of the IBM Toolbox for Java licensed
program on the iSeries installs
the appropriate jt400Mri_lang_cntry.jar file. If the language is not supported,
the install defaults to the English version, which is included in the IBM Toolbox
for Java jar
files.</p>
<ul><li>For example, installing the German language version of licensed program
5722-JC1 installs the German language jar file, jt400Mri_de.jar.</li>
</ul>
<p>You can add support for other languages by adding more than one of
these jar files to the classpath. Java loads the correct string based on the
current locale.</p>
</div>
<div class="section" id="jarfilelist__pcmlnote"><a name="jarfilelist__pcmlnote"><!-- --></a><p><strong>Note 7:</strong> Serializing your PCML file during
development has two benefits:</p>
<ol><li>You need to parse the PCML file only during development and not during
run-time</li>
<li>Users need fewer jar files in their CLASSPATH to run the application</li>
</ol>
<p>To parse the PCML file during development, you need both the PCML
run-time in data.jar or jt400.jar and the PCML parser in x4j400.jar. To run
the serialized application , users need only jt400.jar. For more information
see <a href="pcmlproc.htm#pcmlproc">Building iSeries program calls with PCML</a>.</p>
</div>
<div class="section"><p id="jarfilelist__jt400pcml"><a name="jarfilelist__jt400pcml"><!-- --></a><strong>Note 8:</strong> Use jt400.jar and jt400Native.jar
instead of data400.jar. data400.jar contains the PCML runtime classes, which
are now also in jt400.jar and jt400Native.jar (<a href="#jarfilelist__jt400classic">Note
1</a>). data400.jar is shipped to retain compatibility with previous releases
of IBM Toolbox
for Java.</p>
</div>
<div class="section" id="jarfilelist__reportwriternote"><a name="jarfilelist__reportwriternote"><!-- --></a><p><strong>Note 9:</strong> Copies of the
ReportWriter classes are in more than one jar file:</p>
<ul><li>composer.jar</li>
<li>outputwriter.jar</li>
<li>reportwriters.jar</li>
</ul>
<p>If your application streams PCL data to an iSeries spooled file, you must make the
access classes available by using the appropriate jar file ( <a href="#jarfilelist__jt400classic"> Note
1</a>). Creating a spooled file to hold PCL data requires the AS400, OutputQueue,
PrintParameterList, and SpooledFileOutputStream classes. For more information,
see the <a href="reportwriter.htm#reportwriter">ReportWriter classes</a>.</p>
</div>
<div class="section" id="jarfilelist__jt400micro"><a name="jarfilelist__jt400micro"><!-- --></a><p><strong>Note 10:</strong> jt400Micro.jar does not contain
the classes needed to run MEServer, which reside in both jt400.jar and jt400Native.jar
(<a href="#jarfilelist__jt400classic">Note 1</a>). jt400Micro.jar is
available only from the <a href="http://www.ibm.com/servers/eserver/iseries/toolbox/" target="_blank">IBM Toolbox for Java and JTOpen</a> Web site <img src="www.gif" alt="Link outside Information Center" />.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahnm09.htm" title="Before you install IBM Toolbox for Java, make sure to address the workstation requirements that pertain to your environment.">Installing IBM Toolbox for Java on your workstation</a></div>
</div>
</div>
</body>
</html>