The DB2 Stored Procedure Builder supports building Java stored procedures using Java 1.2 functionality. In addition, the Stored Procedure Builder supports bi-directional languages, such as Arabic and Hebrew, using the bi-di support in Java 1.2.
This support is provided for Windows NT platforms only.
In order for the Stored Procedure Builder to recognize and use Java 1.2 functionality, Java 1.2 must be installed.
To install Java 1.2:
After Java 1.2 is installed successfully, start the Stored Procedure Builder in the normal manner.
To execute Java stored procedures using JDK 1.2 support, set the database server environment variable DB2_USE_JDK12 to TRUE using the following command:
DB2SET DB2_USE_JDK12=TRUE
Also, set your JDK11_PATH to point to the directory where your Java 1.2 support is installed. You set this path by using the following command:
DB2 UPDATE DBM CFG USING JDK11_PATH
To stop the use of Java 1.2, you can either uninstall the JDK/JRE from <DB2PATH>\java\Java12, or simply rename the <DB2PATH>\java\Java12 subdirectory.
Important: Do not confuse <DB2PATH>\java\Java12 with <DB2PATH>\Java12. <DB2PATH>\Java12 is part of the DB2 installation and includes JDBC support for Java 1.2.
To use the remote debugging capability for stored procedures on the Intel and UNIX platforms, you need to install the IBM Distributed Debugger. The IBM Distributed Debugger is included on the Visual Age for Java Professional Edition CD. The debugger client runs only on the Windows platform. Supported server platforms include: Windows, AIX and Solaris. At this time, only Java and C stored procedures can be debugged remotely. Support for SQL procedures will be available at a later date.
To debug SQL procedures on the OS/390 platform, you must also have the IBM C/C++ Productivity Tools for OS/390 R1 product. For more information on the IBM C/C++ Productivity Tools for OS/390 R1, go to the following Web site: http://www.ibm.com/software/ad/c390/pt/
Before you can use the Stored Procedure Builder to successfully build SQL Procedures on your Intel or UNIX database, you must configure your server for SQL Procedures. For information on how to configure your server for SQL Procedures, see the IBM DB2 Universal Database Application Building Guide.
The database manager configuration parameter KEEPDARI must be set to NO. This can be done using the command db2 update dbm cfg using KEEPDARI NO, or using the Control Center. If KEEPDARI is set to YES, you may get message SQL0454N when attempting to build an SQL stored procedure that was previously built and run.
To use the Stored Procedure Builder on the Solaris platform:
To set the DB2 JDK11_PATH, use the command:
DB2 UPDATE DBM CFG USING JDK11_PATH.
- SF59674 - SF59878
There is a problem when using Java Development Kit or Java Runtime 1.1.8 with the Traditional Chinese locale. Graphical aspects of the Stored Procedure Builder program (including menus, editor text, messages, and so on) will not display properly. The solution is to make a change to the file font.properties.zh_TW, which appears in one or both of the following directories:
sqllib/java/jdk/lib sqllib/java/jre/lib
Change:
monospaced.0=\u7d30\u660e\u9ad4,CHINESEBIG5_CHARSET,NEED_CONVERTED
to:
monospaced.0=Courier New,ANSI_CHARSET
For Sun Solaris installations, and if you are using a Java Development Kit or Runtime other than the one installed on AIX with UDB, you must set the environment variable JAVA_HOME to the path where Java is installed (that is, to the directory containing the /bin and /lib directories). Stored Procedure Builder is not supported on Linux, but can be used on supported platforms to build and run stored procedures on DB2 UDB for Linux systems.