Re: SQLException 9999:9999 - SOLVED!

["Steve Swett" <swett@xxxxxxxxxxxxxx>]

The feedback from the newsgroups helped me realize the problem wasn't on the
AS/400 and it also wasn't with the JDK version/level.  My initial goal with
the very small AS/400 test project was to create a JDBC-enabled applet.  To
help with trouble-shooting, though, I temporarily converted it to an
application.  Class path issues were preventing me from running the
application outside the Borland IDE.  However, once that was cleared up I
was still getting the 9999:9999 error if I ran the application using its jar
file -- that is, with the following command:

java -jar test400db.jar

So I traced down the problem by using the "java -verbose" switch on the run
without the jar and on the run with the jar.

Turns out the Borland Archive Wizard wouldn't automatically add the
following classes to the jar file.  These were key to getting text string
error messages:

com.ibm.as400.access.JDMRI
com.ibm.as400.access.JDMRI_en
com.ibm.as400.access.JDMRI_en_US

Once those were in place, the 9999:9999 error was replaced by "The
application requester cannot establish the connection."

Upon further comparison of the "-verbose" listings, I found another class
that wasn't automatically getting added to the jar file:

com.ibm.as400.access.SocketContainerInet

Way early in the project it was obvious that yet 3 other class files weren't
getting add to the jar:

com.ibm.as400.access.MRI
com.ibm.as400.access.MRI_en
com.ibm.as400.access.MRI_en_US

So, by adding all 7 of these class files to the jar file manually,
everything started working just fine.

Thanks to those who "bumped" me in the right direction.  I appreciate your
help.



-----Original Message-----
From: Dave Wall <dawall@us.ibm.com>
To: JAVA400-L@midrange.com <JAVA400-L@midrange.com>
Date: Friday, March 09, 2001 4:49 PM
Subject: Re: SQLException 9999:9999 getConnection - stack trace & complete
program


>
>To summarize what you said, (1) the app works inside the Borland
>environment, and (2) the app works if you remove the JDBC stuff so all that
>is left is the swing GUI.  The problem is when you try to connect outside
>the Borland environment.  If  true then I agree that the AS/400 side is in
>good shape.  The IBM JDK may be enough to get you going.
>
>You can get IBM's 1.3 JVM at http://www.ibm.com/java.  Take the "developer
>kits" link at the top of the page, then pick the JVM you want.
>
>David Wall
>AS/400 Toolbox for Java


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---