These restrictions apply to Java™ stored procedures.
- A Java stored
procedure should not create additional threads. An additional thread may be
created in a job only if the job is multithread capable. Because there is
no guarantee that a job that calls an SQL stored procedure is multithread
capable, a Java stored procedure should not create additional threads.
- You cannot use adopted authority to access Java class files.
- A Java stored
procedure always uses the latest version of the Java Development Kit that is installed on
the system.
- Since Blob and Clob classes reside in both the java.sql and com.ibm.db2.app
packages, the programmer must use the entire name of these classes if both
classes are used in the same program. The program must ensure that the Blob
and Clob classes from the com.ibm.db2.app are used as the parameters passed
to the stored procedure.
- When a Java stored procedure is created, the system generates
a program in the library. This program is used to store the procedure definition.
The program has a name that is generated by the system. This name can be obtained
by examining the job log of the job that created the stored procedure. If
the program object is saved and then restored, then the procedure definition
is restored. If a Java stored procedure is to be moved from one system
to another, you are responsible for moving the program that contains the procedure
definition as well as the integrated file system file, which contains the Java class.
- A Java stored
procedure cannot set the properties (for example, system naming) of the JDBC
connection that is used to connect to the database. The default JDBC connection
properties are always used, except when prefetching is disabled.