SQLJ Driver Built-In Procedures
Use the SQLJ Driver built-in procedures for
one of the following tasks:
- To install, replace, or remove a set of Java™ classes
- To specify a path for Java™ class resolution for Java™ classes that are included in a JAR file
- To map or remove the mapping between a user-defined type and the Java™ type to which it corresponds
(explicit id sqlj001)
sqlj001
(explicit id sqlj002)
sqlj002
(explicit id sqlj003)
sqlj003
(explicit id sqlj004)
sqlj004
(explicit id sqlj005)
sqlj005
(explicit id sqlj006)
sqlj006
SQLJ Driver Built-In Procedures
{ <sqlj.install_JAR>[] | <sqlj.replace_JAR> [] | <sqlj.remove_JAR> [] | <sqlj.alter_java_path> [] | <sqlj.SetUDTextName> [] | <sqlj.unsetUDTextName> [] }
A client application must specify the 'sqli' owner name to invoke these functions from an ANSI-compliant database.
The SQLJ built-in procedures are stored in the sysprocedures system
catalog table. They are grouped under the sqlj schema.
Tip: For any Java™ static
method, the first built-in procedure that you execute must be the sqlj.install_jar(
) procedure. You must install the JAR file before you can create
a UDR or map a user-defined data type to a Java™ type. Similarly, you cannot use any of
the other SQLJ built-in procedures until you have used sqlj.install_jar(
).
1 See sqlj.install_jar
2 See sqlj.replace_jar
3 See sqlj.remove_jar
5 See sqlj.setUDTextName