We have just tried your suggestions regarding the JRE 1.3 fixes on Solaris,
using version 7 of the OS, 1.3.0.1 of the JRE and version 6.0 of the
compiler. In addition we have used the compiler command line switches you
recommended.

Unfortunately when we try to run the code we see the following output.

StarII starting.
Starting TOSY Server
Started TOSY Server
Starting webserver
Started webserver
Starting rmid
Started rmid
Initialising Javaspace
using absolute policy path: /usr/local/aol/./java.policy
using absolute logdir path: /usr/local/aol/sp1log
/outrigger-dl.jar requested from localhost:47516
Fri Jan 05 09:23:28 GMT 2001:ExecGroup-0:out:BasicSpace: Front end activated
Fri Jan 05 09:23:29 GMT 2001:ExecGroup-0:out:opening DB:
/usr/local/aol/sp1log/J
avaSpace.odb
Javaspace Initialised
Starting lookup
Started lookup
/reggie-dl.jar requested from localhost:47527
Starting trans
Started trans
Starting rmiregistry
Started rmiregistry
/mahalo-dl.jar requested from localhost:47532
Starting QM
Started QM
Quarter Master, Version 2.2.2 Entegrity Solutions 2000, clear quest fixes
Date Created:- 20/12/2000
Last Modified by: Shaun Hyett
# # An unexpected exception has been detected in native code outside the
VM.# Pr
ogram counter=0xf423b544
#
# Problematic Thread: prio=5 tid=0x27fe0 nid=0x1 runnable
#
Fri Jan 05 09:24:05 GMT 2001:ExecGroup-2:out:TxnManagerImpl: recovering
state...
Fri Jan 05 09:24:05 GMT 2001:ExecGroup-2:out:TxnManagerImpl: ...state
recovered
1267 Abort - core dumped
Starting ts
Started ts
StarII Startup Completed
# *****************************************
* AOL STARII Transformation Server *
* (C) 2000 Entegrity Solutions *
* *
*****************************************
Transformation Server, Version 2.2.1(c) Entegrity Solutions 2000
Date Created: - 08/12/2000
Last Modified by: Steven Christopher Upton, Darren Harter
# # An unexpected exception has been detected in native code outside the
VM.# Pr
ogram counter=0xf3e3b544
#
# Problematic Thread: prio=5 tid=0x28010 nid=0x1 runnable
#
^C
#
# java -version
java version "1.3.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_01)
Java HotSpot(TM) Client VM (build 1.3.0_01, mixed mode)
# ldd -r libesc*
        libsdpts.so => ./libsdpts.so
        libldapssl30.so => ./libldapssl30.so
        libsocket.so.1 => /usr/lib/libsocket.so.1
        libnsl.so.1 => /usr/lib/libnsl.so.1
        libdl.so.1 => /usr/lib/libdl.so.1
        libpthread.so.1 => /usr/lib/libpthread.so.1
        libthread.so.1 => /usr/lib/libthread.so.1
        librt.so.1 => /usr/lib/librt.so.1
        libm.so.1 => /usr/lib/libm.so.1
        libCrun.so.1 => /usr/lib/libCrun.so.1
        libresolv.so.2 => /usr/lib/libresolv.so.2
        libc.so.1 => /usr/lib/libc.so.1
        libmp.so.2 => /usr/lib/libmp.so.2
        libaio.so.1 => /usr/lib/libaio.so.1
        libw.so.1 => /usr/lib/libw.so.1
        /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
#

Using -library=iostream,no%Cstd -liostream is impossible to compile the code
You gave me since it is based upon SDP and therefor needs the
compiler-provided Cstd header files.
Since no%Cstd tells the compiler not to use those it is simple not possible
to compile with that set at least.

What i have done instead is library=iostream,Cstd -liostream....

We can't use SDP unless we have Cstd available.
But with Cstd available the Hotspot VM dies and Sun says build without Cstd
to fix it.

If -library=no%Cstd is specified, then the compiler-provided Cstd header
files are not searched. Since SDP is based upon this it is simply impossible
to compile with no%Cstd set.

Since the SUN sample of some reason statically link with iostream i was
meaning to try and compile linking with it statically instead of dynamically
as the standard way is..