A Cloudscape test gets a different error depending on whether it was run with
the JIT on or JIT off. The problem is in JDK 1.2.2_06 on Sparc Solaris 5.8 and 5.6
systems. The problem does not exist in JDK 1.2.2_007. However, there is a
JDK 1.2.2_07 for Sparc/Solaris, but I can't figure out how to get a copy. That is
your job.

Jar files are attached. We might be able to get source.

algol% cat bug1.ksh
#!/bin/ksh
# This test fails on a Solaris 5.8 system using the jdk1.2.2_06 JVM
#JAVA_HOME=/usr/local/java/jdk1.4.0/solsparc
#JAVA_HOME=/usr/local/java/jdk1.2.2_007/binary/sparc
JAVA_HOME=/usr/java1.2
export CLASSPATH=cloudscape.jar:tools.jar
#rm -rf /tmp/foodb
${JAVA_HOME}/bin/java -Djava.compiler=NONE COM.cloudscape.tools.ij <<EOF_ARCHIVE_01
connect 'jdbc:cloudscape:/tmp/foodb;create=true';
drop table foo;
create table foo (a int, b int, c int);
exit;
EOF_ARCHIVE_01
STATUS=$?
echo 'Create: '${STATUS}
${JAVA_HOME}/bin/java -Djava.compiler=NONE COM.cloudscape.tools.ij <<EOF_ARCHIVE_02
connect 'jdbc:cloudscape:/tmp/foodb;create=true';
create table foo (a int, b int, c int);
exit;
EOF_ARCHIVE_02
STATUS=$?
echo 'Test JIT off '${STATUS}
${JAVA_HOME}/bin/java COM.cloudscape.tools.ij <<EOF_ARCHIVE_03
connect 'jdbc:cloudscape:/tmp/foodb;create=true';
create table foo (a int, b int, c int);
exit;
EOF_ARCHIVE_03
STATUS=$?
echo 'Test JIT on '${STATUS}
algol% bug1.ksh
ij version 3.5 (c) 1997-2000 Informix Software, Inc.
ij> WARNING 01J01: Database '/tmp/foodb' not created, connection made to existing database instead.
ij> 0 rows inserted/updated/deleted
ij> 0 rows inserted/updated/deleted
ij> Create: 0
ij version 3.5 (c) 1997-2000 Informix Software, Inc.
ij> WARNING 01J01: Database '/tmp/foodb' not created, connection made to existing database instead.
ij> ERROR X0X08: Table or view 'FOO' already exists in schema 'APP'.
ij> Test JIT off 0
ij version 3.5 (c) 1997-2000 Informix Software, Inc.
ij> WARNING 01J01: Database '/tmp/foodb' not created, connection made to existing database instead.
ij> ERROR XJ001: Java exception: ': java.lang.NullPointerException'.
ij> Test JIT on 0

allan.jacobs@Eng 2000-12-07

JDK 1.2.2_07 broke the same way. My report did not make this explicit, but the
behavior is fine in JDK 1.3.0 and in JDK 1.4.0.

allan.jacobs@Eng 2000-12-13