NonStop Server for Java Programmer's Reference (NSJ 4.2+)

$ cd /usr/tandem/nssjava/jdk142_v20/install
$ make TARGET_JAVA_DIR=/h/testdir CUSTLIB_DIRS=/h/testdir
Example 2 shows how to accomplish the operations performed in Example 1, but runs make while
in a user directory.
$ cd /h/testdir
$ make -f /usr/tandem/java/install/Makefile TARGET_JAVA_DIR=. \
CUSTLIB_DIRS=/h/testdir
In this example, CUSTLIB_DIRS must contain an absolute directory name even though the current
working directory is /h/testdir. The backslash (\) character is a continuation character and is
not required if you type the command on one line.
Example 3 sets CUSTLIB_DIRS to more than one directory and uses a wildcard in one directory.
$ make CUSTLIB_DIRS="/h/testdir /h/lib/*"
This command creates a java executable in the directory that TARGET_JAVA_DIR is set to in
the Makefile. It uses all library files found in /h/testdir and in any directories directly under
/h/lib.
Note: This command does not use library files in /h/lib itself. Also, this command
does not use libraries in directories that are subdirectories of the directories in
/h/lib. This command uses only the library files in the directories directly under
/h/lib.
How to Create Your Own Library of Native Code
The javahjni demonstration program that comes with NonStop Server for Java 4 shows an
example of a user Makefile that builds a library file from user source code and uses the Nonstop
Server for Java 4 Makefile to build a new java executable with the user's native code linked in.
The javahjni demonstration program can be found in the
install-dir/demo/javahjni directory.
Configuring TCP/IP and DNS for RMI
For Remote Method Invocation (RMI) API to work, TCP/IP and its component, DNS, must be
configured correctly. For the correct version of TCP/IP, see the NonStop Server for Java 4 Softdoc.
A network administrator usually configures TCP/IP and DNS, but you can determine if an incorrect
TCP/IP configuration is causing a JVM problem. To check the TCP/IP configuration, use the Java
Checker, javachk, which is available in the /usr/tandem/java/install directory.
Execute javachk in the same environment as the JVM has (that is, using the same defines that
were used to run the JVM). The Java Checker will identify failing socket routine calls. When you
know which calls are failing, you can fix or work around the problems.
For information about javachk, see the file