HP-UX 11i September 2001 Release Notes

HP-UX 11i Operating Environment Applications

HP-UX 11i Technical Computing Operating Environment (new at 11i original release)

Chapter 4

Documentation

For more detailed documentation and additional product information, see:

• The HP MLIB User’s Guide (B6061-96015) and the HP MLIB Release Notice

(B6061-96016) available at the following URLs:

http://docs.hp.com/

http://www.hp.com/rsn/mlib/mlibhome.html/

• Manpages:

— BLAS Standard manpages (new for 11i)

— LAPACK 3.0 manpages (revised)

— VECLIB manpages (revised)

HP 3D Technology for the Java Platform

The HP 3D Technology for the Java 1.1.3a Platforms 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 ﬁle. 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) (updated for September

2001)

HP Message-Passing Interface (MPI) Version B.11.11 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.

New features include:

• 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 ﬁx a bug)

all programs, which use the library immediately, enjoy the ﬁx.