Begin changeJar 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 it resides in a directory contained in your CLASSPATH.

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

To use this package or function... ...place the appropriate jar files in your CLASSPATH
Toolbox 1 jt400Servlet.jar data400.jar 2 uitools.jar jui400.jar util400.jar 3 x4j400.jar jt400Proxy.jar jt400Mri_lang_cntry.jar 4 reportwriter 5
Access classes X             X    
Vaccess classes X                  
Security classes X             X    
Resource classes X                  
HTML classes   X                
Servlet classes X X                
Reportwriter classes X                 X
PCML (development) 6 X   X       X      
PCML (run-time, serialized) X   X              
PDML (development)       X X X X      
PDML (run-time, parsed)         X X X      
PDML (run-time, serialized)         X X        
JDBC Data Source GUI 7 X       X          
NLS system and error messages                 X  
Proxy server X                  

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

Note 2: 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. Use jt400.jar and jt400Native.jar instead of data400.jar.

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

Note 4: 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 5: 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.

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: 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.End change