Jar files

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.

To use a jar file, make sure that you include an entry for it in your CLASSPATH.

The following chart indicates which jar files must be in your CLASSPATH to use classes from the listed package.

Some entries in the table have notes that offer more information. If your browser is Javascript-enabled, click the Click to display a detailed explanation image to display the information in a separate window. Otherwise, you can click the text link to link to the same information listed following the table.

Toolbox for Java package or function Jar files required to be in your CLASSPATH
Access classes jt400.jar (client) or jt400Native.jar (server) in the usual client/server environment Click to display a detailed explanation Note 1, or jt400Proxy.jar in a proxy environment
Begin changeCommandPrompterClick to display a detailed explanation Note 2 jt400.jar, jui400.jar, util400.jar Click to display a detailed explanation Note 3, and x4j400.jarEnd change
HTML classes jt400.jar Click to display a detailed explanation Note 1 plus jt400Servlet.jar (client), or jt400Native.jar (server) Click to display a detailed explanation Note 1
JDBC Data Source GUI Click to display a detailed explanation Note 4 jt400.jar (client) Click to display a detailed explanation Note 1 and jui400.jar
NLS system and error messages jt400Mri_lang_cntry.jar Click to display a detailed explanation Note 5
PCML (development) Click to display a detailed explanation  Note 6 jt400.jar (client) or jt400Native.jar (server) Click to display a detailed explanation Note 1Click to display a detailed explanation Note 7, and x4j400.jar
PCML (run-time, serialized) jt400.jar (client) or jt400Native.jar (server) Click to display a detailed explanation Note 1, Click to display a detailed explanation Note 7
PDML (development) Click to display a detailed explanation Note 2 uitools.jar, jui400.jar, util400.jar Click to display a detailed explanation Note 3, and x4j400.jar
PDML (run-time, parsed) Click to display a detailed explanation Note 2 jui400.jar, util400.jar Click to display a detailed explanation Note 3, and x4j400.jar
PDML (run-time, serialized) Click to display a detailed explanation Note 2 jui400.jar, and util400.jar Click to display a detailed explanation Note 3
ReportWriter classes jt400.jar (client) or jt400Native.jar (server) Click to display a detailed explanation Note 1 and reportwriter jars Click to display a detailed explanation Note 8
Resource classes jt400.jar (client) or jt400Native.jar (server) Click to display a detailed explanation Note 1
Begin changeRFML jt400.jar (client) or jt400Native.jar (server) Click to display a detailed explanation Note 1, and x4j400.jarEnd change
Security classes jt400.jar (client) or jt400Native.jar (server) in the usual client/server environment Click to display a detailed explanation Note 1, or jt400Proxy.jar in a proxy environment
Servlet classes jt400.jar Click to display a detailed explanation Note 1 plus jt400Servlet.jar (client), or jt400Native.jar (server) Click to display a detailed explanation Note 1
Begin changeiSeries System Debugger Click to display a detailed explanation Note 2 jt400.jar (client) Click to display a detailed explanation Note 1 and tes.jarEnd change
Begin changeToolboxME for iSeries jt400Micro.jar (client) and jt400.jar (server) or jt400Native.jar (server) Click to display a detailed explanation Note 9End change
Vaccess classes jt400.jar (client) Click to display a detailed explanation Note 1

Note 1: Some of the IBM Toolbox for Java classes are in more than one jar file:

Begin changeNote 2: Using CommandPrompter, PDML, or the iSeries System Debugger also requires one additional jar file that is not part of Toolbox for Java: jhall.jar. For more information about downloading jhall.jar, see the Sun JavaHelp(TM) Web site Link outside Information Center.End change

Note 3: util400.jar contains iSeries-specific classes for formatting input and for using the command line (CL) prompter. Using the CommandPrompter class requires util400.jar. Using PDML does not require util400.jar, but it is useful.

Note 4: jui400.jar contains the classes necessary to use the JDBC DataSource GUI interface. jt400.jar ( Note 1) contains the classes necessary for all other JDBC functions.

Note 5: 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 Code used to translate the contained text. In some cases, the ISO Country 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.

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.

Note 6: Serializing your PCML file during development has two benefits:

  1. You need to parse the PCML file only during development and not during run-time
  2. Users need fewer jar files in their CLASSPATH to run the application

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 Building iSeries program calls with PCML.

Note 7: 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 (Note 1). data400.jar is shipped to retain compatibility with previous releases of IBM Toolbox for Java.

Note 8: Copies of the ReportWriter classes are in more than one jar file:

If your application streams PCL data to an iSeries spooled file, you must make the access classes available by using the appropriate jar file ( Note 1). Creating a spooled file to hold PCL data requires the AS400, OutputQueue, PrintParameterList, and SpooledFileOutputStream classes. For more information, see the ReportWriter classes.

Begin changeNote 9: jt400Micro.jar does not contain the classes needed to run MEServer, which reside in both jt400.jar and jt400Native.jar (Note 1). jt400Micro.jar is available only from the IBM Toolbox for Java and JTOpen Web site Link outside Information Center.End change