Access databases using IBM Developer Kit for Java DB2 SQLJ support

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.

The SQLJ support provided by the IBM Developer Kit for Java includes the SQLJ run-time classes, and is available in /QIBM/ProdData/Java400/ext/runtime.zip.

SQLJ setup

Before you can use SQLJ in Java applications on your server, you need to prepare your server to use SQLJ. For more information, see Setting up your server to use SQLJ.

SQLJ tools

The following tools are also included in the SQLJ support provided by the IBM Developer Kit for Java:

The SQLJ translator, sqlj, replaces embedded SQL statements in the SQLJ program with Java source statements and generates a serialized profile that contains information about the SQLJ operations that are found in the SQLJ program.
The DB2 SQLJ Profile Customizer, db2profc, precompiles the SQL statements stored in the generated profile and generates a package in the DB2 database.
The DB2 SQLJ Profile Printer, db2profp, prints the contents of a DB2 customized profile in plain text.
The SQLJ profile auditor installer, profdb, installs and uninstalls debugging class-auditors into an existing set of binary profiles.
The SQLJ profile conversion tool, profconv, converts a serialized profile instance to Java class format.

Note: These tools must be run in the Qshell Interpreter.

DB2 SQLJ restrictions

When you create DB2 applications with SQLJ, you should be aware of the following restrictions:

DB2 SQLJ support adheres to standard DB2 Universal Database™ restrictions on issuing SQL statements.
The DB2 SQLJ profile customizer should only be run on profiles associated with connections to the local database.
The SQLJ Reference Implementation requires JDK 1.1, or higher. See Support for multiple Java Development Kits (JDKs) for more information on running multiple versions of the Java Development Kit.

For information on using SQL in your Java applications, see Embed SQL Statements in your Java application and Compile and run SQLJ programs.

Structured Query Language for Java profiles
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.
The structured query language for Java (SQLJ) translator (sqlj)
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.
Precompile SQL statements in a profile using the DB2 SQLJ profile customizer, db2profc
You can use the DB2 SQLJ Profile Customizer, db2profc, to make your Java application work more efficiently with your database.
Print the contents of DB2 SQLJ profiles (db2profp and profp)
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.
SQLJ profile auditor installer (profdb)
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.
Convert a serialized profile instance to Java class format using the SQLJ profile conversion tool (profconv)
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.
Embed SQL statements in your Java application
Static SQL statements in SQLJ are in SQLJ clauses. SQLJ clauses begin with #sql and end with a semicolon (;) character.
Compile and run SQLJ programs
If you Java program has embedded SQLJ statements, you need to follow a special procedure to compile and run it.

Parent topic: Database access with the IBM Developer Kit for Java