NonStop Server for Java 6.0 Programmer's Reference

_RLD_LIB_PATH
The _RLD_LIB_PATH environment variable specifies the library path for DLLs. You need to use
this environment variable only if you use user DLLs. You can specify one or more directories as
necessary. Separate each directory in the list by using a colon (:). Set this environment variable
as follows:
_RLD_LIB_PATH=dll_path[:dll_pathn]...
where dll-path and dll-pathn are the directories where the user DLLs reside.
For example:
export _RLD_LIB_PATH=/home/me/mydll
Symbolic Link
The link /usr/tandem/java is created when NonStop Server for Java 6.0 is installed. It is a
symbolic link to the actual JDK directory, which has the form:
/usr/tandem/nssjava/jdk60x_hyy
where x refers to the version number of the Sun Microsystems update upon which NonStop Server
for Java 6.0 is based and yy refers to the particular product version update (PVU) of NonStop
Server for Java 6.0. For example, for NonStop Server for Java 6.0, based on Java SE 6.0, the
symbolic link is /usr/tandem/nssjava/jdk160_h60.
The /usr/tandem/java is a shorthand way to refer to the latest version of the JDK installed on
the system. When you unpax a NonStop Server for Java 6.0 pax file, the symbolic link is created
or reset to refer to the JDK directory that is being unpaxed, which means that the symbolic link
refers to the version of NonStop Server for Java 6 that was last installed. You are not required to
use the symbolic link. To make sure you are always using the 6.0 version of the JDK, even if a
later version has been installed, you can put the bin directory in your PATH, for example:
export PATH=/usr/tandem/nssjava/jdk160_h60/bin:$PATH
You can also reset the symbolic link yourself by using the ln command with the -s option. For
example, if you install a PVU based on version 1.4.2 of the JDK, but still want version 6.0 to be
the one referred to by /usr/tandem/java, you can reset the symbolic link instead of unpaxing
version 6.0 again:
$ cd /usr/tandem
$ rm java
$ ln -s /usr/tandem/nssjava/jdk160_h60 java
The symbolic link is always put in the directory where NonStop Server for Java 6.0 is installed, so
if you use the -s option to specify an alternative installation directory during the unpaxing step,
the symbolic link is install_dir/java instead of /usr/tandem/java. For example, if
nssjava/jdk160_h60 is installed in /h/myjava, the symbolic link is /h/myjava/java, and
this symbolic link points to the directory /h/myjava/nssjava/jdk160_h60.
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 6.0 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 /usr/tandem/java/install/README_javachk.
40 Installation and Configuration