It doesn't matter where you put the JAR file, as long as it's in your
CLASSPATH.
Indeed, I consider /QIBM/UserData/Java400/ext to be a bad choice, and
would never recommend it. Except maybe as a test to eliminate other
possible problems...
Smith, Mike wrote:
I am using Scott's program to write records to a SQL Server database. I
have gotten this to work, but I guess I have a classpath issue.
Due to another issue I was having with JT400 I worked with a someone
from IBM to get it resolved. In my conversations with him, it was
indicated that
Official locations for the Toolbox jar files:
/QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar
/QIBM/ProdData/OS400/jt400/lib/jt400Native.jar
Rogue locations where Toolbox jars and classes have been found:
/QIBM/ProdData/Java400/
/QIBM/UserData/Java400/ext/
/QIBM/ProdData/Java400/jdk14/lib/
/QIBM/ProdData/Java400/jdk14/lib/ext/
/QIBM/ProdData/OS400/Java400/ext/
/QIBM/ProdData/OS400/Java400/jdk/lib/ext/
/QOPT/WEBSPHERE/was/setup.jar
So I started removing extraneous copies of
jt400.jar
Now Scott's program doesn't work. If I put
jt400.jar back in /QIBM/UserData/Java/ext then Scott's program works
again.
So if this is a roque location for jt400 and
shouldn't be there, then what do I need to do to make Scotts program
recognize jt400 in its proper location.
Mike
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
