Filter
Top Products
You may want to pipe the output to a file for easier viewing. The JDK11_PATH
field appears near the beginning of the output. For more information on these
commands, refer to the Command Reference.
On Solaris, some Java Virtual Machine implementations do not work
well in programs that run in a ″setuid″ environment. The shared
library that contains the Java interpreter, libjava.so, may fail to
load. As a workaround, you can create symbolic links for all needed
JVM shared libraries in /usr/lib, with a command similar to the
following (depending on where Java is installed on your machine):
ln -s /opt/jdk1.1.3/lib/sparc/native_threads/*.so /usr/lib
For more information on this and other workarounds available,
please visit:
http://www.software.ibm.com/data/db2/java/v5/faq.html
To run Java programs, the following environment variables are automatically
updated during DB2 installation on OS/2 and the Windows Operating
System, and during instance creation on UNIX platforms.
On UNIX platforms:
v CLASSPATH includes ″.″ and the file sqllib/java/db2java.zip
v On AIX, Linux, Silicon Graphics IRIX, and Solaris: LD_LIBRARY_PATH
includes the directory sqllib/lib; on HP-UX: SHLIB_PATH includes the
directory sqllib/lib
v On Solaris only: THREADS_FLAG is set to ″native″
On Windows and OS/2 platforms:
v CLASSPATH includes ″.″ and the file %DB2PATH%\java\db2java.zip
In order to build and run SQLJ programs, CLASSPATH is also automatically
updated to include these files:
On UNIX platforms:
v sqllib/java/sqlj.zip (required to build SQLJ programs)
v sqllib/java/runtime.zip (required to run SQLJ programs)
On Windows and OS/2 platforms:
v %DB2PATH%\java\sqlj.zip (required to build SQLJ programs)
v %DB2PATH%\java\runtime.zip (required to run SQLJ programs)
Java Applications
Start your application from the desktop or command line by running the Java
interpreter on the executable program with this command:
Chapter 10. Running Your Own Applications 129