HP-UX 11i March 2002 Release Notes

HP-UX 11i Operating Environment Applications
HP-UX 11i Technical Computing Operating Environment
Chapter 4
94
— VECLIB manpages (revised)
HP 3D Technology for the Java Platform
The HP 3D Technology for the Java 2 Platform contains the classes for creating 3D
applications. The HP 3D Technology for the Java Platform may be distributed with your
Java applications as long as you adhere to the terms of the LICENSE file. Vendors also
need to include an installer.
Documentation
For prerequisites, installation requirements, and information read the release notes
included in the HP 3D software. Or for the most up-to-date information, go to the Web at
http://www.hp.com/go/java.
HP Message-Passing Interface (MPI)
HP Message-Passing Interface (MPI) is a high-performance implementation of the
Message-Passing Interface Standard. HP MPI complies fully with the 1.2 standard and
partially with the 2.0 standard. HP MPI provides an application programming interface
and software libraries to support parallel, message-passing applications that are
efficient, portable, and flexible.
updated for
March 2002
New feature of HP MPI version 1.7.2:
• With the use of libmpirm.sl, the PA-RISC version of Load Sharing Facility (LSF)
can be run on the Itanium Processor Family (IPF) version of HP MPI.
updated for
September 2001
New features of HP MPI version 1.7 include the following:
• New start up. The new HP MPI start-up requires that MPI be installed in the same
directory on every execution host. The default is the location from which mpirun is
executed. This can be overridden with the MPI_ROOT environment variable. We
recommend setting the MPI_ROOT environment variable prior to starting mpirun.
Previous versions of HP MPI allowed mpirun to exit prior to application termination
by specifying the -W option. The option -W used with mpirun is no longer supported.
To achieve similar functionality, place mpirun in the background.
• Support for shared libraries. When a library is shared, programs using it contain only
references to library routines, as opposed to archive libraries, which must be linked
into every program using them. The same copy of the shared library is referenced by
each executable using it.
An advantage of shared libraries is that when the library is updated (e.g. to fix a bug),
all programs, which use the library immediately, enjoy the fix.
• Library names. Some of the libraries have been merged. Compilation wrappers have
been provided for convenience. Wrappers can also be used as templates.
• Multi-thread mode. By default, the non thread-compliant library (libmpi) is used
when running MPI jobs. Linking to the thread-compliant library (libmtmpi) is now
required only for applications that have multiple threads making MPI calls
simultaneously. In previous releases, linking to the thread-compliant library was
required for multi-threaded applications even if only one thread was making a MPI
call at a time.