× 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.



Hi Mike,

Thought I would put my 2 cents worth in.  Below I have included an
example of the Java command running on our iSeries, V5R3, Java 1.4.  It
may give some clues as to where you are going wrong.... (RUNJVA is set
up similarly):


JAVA CLASS('com.xxxx.pdfgen.SplfMonitor')
CLASSPATH('/com/xxxx/as400splf2pdf/as4
00splf2pdf.jar:COM/xxxx/as400splf2pdf/XXXX_COMMON.JAR:/COM/xxxx/as400spl
f2pdf/LO
G4J-1.2.8.JAR:/COM/xxxx/as400splf2pdf/MSBBarCode.jar:/QIBM/ProdData/OS40
0/jt400/
lib/jt400native.jar:/com/StyleReportPro/xtools.jar:/com/StyleReportPro/x
report_p
ro.jar:/com/StyleReportPro/design_pro.jar') OPTIMIZE(40)
PROP((java.version 1.4)
 (java.awt.headless true)) OPTION(*VERBOSE) JOB(*GEN)

Points to note:
(1) In this case I am using the Native jt400native.jar.  I am not
suggesting going this way, but it is an alternative.
(2) I checked my IFS and our jt400.jar resides in this location:
/com/ProdData/HTTP/Public/jt400/lib/jt400.jar.  This version does have
AS400JDBCDriver.class included.  You may want to verify that in your
version.
(3) Note that the Class of your program called needs to have the fully
qualified name of the package to the Class being called.
(4) Note that any supporting jars need to be included in the classpath,
not just the folder that the jar resides.  
(5) I recommend option(*verbose) while working out this issue.  It will
show you in the associated QPRINT every class that is being loaded, and
from where.
(6) You may want to verify with your admin that Java 1.4 is loaded on
the AS400.  I think it normally is with V5R3, but it may be an option
that needs to be added.  This can be checked with GO LICPGM, option 10.
You should see: 5722JV1   *COMPATIBLE  Java Developer Kit 1.4 
(7) Verify that the jt400.jar that you are picking up is the only one in
your classpath, and that the version being used has the AS400JDBCDriver
included. 
(8) Note: Running HelloWorld does not test jt400.jar capability as it
has no database connectivity. 
(9) Finally, you may want to verify with your admin that no particular
access restrictions have been placed on the jt400.jar file i.e. you
should have read access.  If you have sufficient privilage, you can
check this with the WRKLNK command (just navigate to the jt400.jar and
use option 9 to work with authority).  You should have *PUBLIC *RX for
each level to the jt400.jar and on the jar.

Failing all that, then we will need to see how your program loads
AS400JDBCDriver.  Perhaps it is using an explicit path or something like
that.

Regards
John                         


date: Wed, 14 Feb 2007 10:49:25 -0500
from: "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx>
subject: RE: RUNJVA problems

Don't take this the wrong way, but I feel better that you and Pete are
stumped on this.  

Any way I have tried your last 2 suggestions with the same results.  

I appreciate all the help, because  I just don't have a clue whats going
on.

Michael Smith
iSeries.mySeries.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.