SQLJ procedures that manipulate JAR files

Both Java™ stored procedures and Java UDFs can use Java classes that are stored in Java JAR files.

To use a JAR file, a jar-id must be associated with the JAR file. The system provides stored procedures in the SQLJ schema that allow jar-ids and JAR files to be manipulated. These procedures allow JAR files to be installed, replaced, and removed. They also provide the ability to use and update the SQL catalogs associated with JAR files.

• SQLJ.INSTALL_JAR
  The SQLJ.INSTALL_JAR stored procedure installs a JAR file into the database system. This JAR file can be used in subsequent CREATE FUNCTION and CREATE PROCEDURE statements.
• SQLJ.REMOVE_JAR
  The SQLJ.REMOVE_JAR stored procedure removes a JAR file from the database system.
• SQLJ.REPLACE_JAR
  
• SQLJ.UPDATEJARINFO
  The SQLJ.UPDATEJARINFO updates the CLASS_SOURCE column of the SYSJARCONTENTS catalog table. This procedure is not part of the SQLJ standard but is used by the DB2^® UDB for iSeries™ stored procedure builder.
• SQLJ.RECOVERJAR
  The SQLJ.RECOVERJAR procedure takes the JAR file that is stored in the SYSJAROBJECTS catalog and restores it to the /QIBM/UserData/OS400/SQLLib/Function/jar/jarschema/jar_id.jar file.
• SQLJ.REFRESH_CLASSES
  The SQLJ.REFRESH_CLASSES stored procedure causes the reloading of user defined classes used by Java stored procedures or Java UDFs in the current database connection. This stored procedure must be called by existing database connections to obtain changes made by a call to the SQLJ.REPLACE_JAR stored procedure.