× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



No joy. I created a folder and copied the class file to it and ran it with a "classpath" parameter that pointed to where the jt400.jar was located and I still got the same error. Even dumped jt400.jar into the current folder and it didn't work.

Something is up.  I just need to figure out what.

Pete


Pete Helgren wrote:
So if a create a "Petesjava" folder and move the JDBCPopulate.class file to that folder, it will then run? Hmmm. Not sure if I understand why that would work but I'll give it a whirl.

Pete

Clapham, Paul wrote:
This sounds familiar. Is /QIBM/ProdData/OS400/Java400/ in the Java extensions 
directory? I can't remember. If so, then classes loaded from there can't see 
classes in the classpath (because they are loaded by a class loader that's only 
looking at the extensions directory). So your JDBCPopulate class is in the 
extensions directory and the jt400.jar isn't, so JDBCPopulate can't load 
classes from jt400.jar.

It took me about 3 days to figure out what was going on when that happened to 
me. Pretty much cured me of the lazy habit of throwing jars into the extensions 
directory to avoid explicitly naming them in the classpath. (Although that 
isn't exactly what happened here.) Moral of the story in this case would be to 
put your source code and compiled classes in your own directories and not in 
IBM's.

PC2


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.