Dieter wrote:
Hi,
this corresponds to Driver class not found. possible reason:
- wrong configuration in global.properties (Driver name, or subprotocol
in URL)
- wrong classpath
I attempted to take suggestions from your first response and changed CL
program
STRJVAGATE.
After ending and re-starting, the SQLGATE job log now shows:
Display All Messages
System: TEST
Job . . : SQLGATE User . . : GTHOMPSON Number . . . :
095645
Job 095645/GTHOMPSON/SQLGATE started on 09/15/11 at 14:30:22 in
subsystem
QBATCH in QSYS. Job entered system on 09/15/11 at 14:30:22.
Job 095645/GTHOMPSON/SQLGATE submitted.
>> QSH CMD('java -classpath /java/jdbc -jar
/JVAGATE/AppServer4RPG.jar')
I retained a modified classpath part because the Microsoft Sql Server
sqljdbc4.jar file is there.
Here are global.properties lines which are not commented:
as400.system=172.17.16.69
as400.user=GTHOMPSON
as400.password=
as400.dataqPath=/QSYS.LIB/JVAGATE.LIB/JAVAQ.DTAQ
as400.responseqLib=/QSYS.LIB/JVAGATE.LIB/
as400.ccsid=500
handler.ARDPGM=de.bender_dv.ardgate.application.ArdHandler
handler.KUNDE=de.bender_dv.test.Confirmer
ard.url.JDBCTEST=jdbc:sqlserver://172.17.16.63;databaseName=JdbcTest
ard.driver.JDBCTEST=com.microsoft.sqlserver.jdbc.SQLServerDriver <-
this looks correct to me !?
I entered ".JDBCTEST" after ard,url and ard.driver thinking that
associates
the url and driver to the JDBCTEST RDB Directory Entry I made for this
test.
I then repeated the test connection from STRSQL, getting the same result:
Enter SQL Statements
Type SQL statement, press Enter.
> connect to JDBCTEST user jdbctest using 'XXXX'
Connection exception - SQLSTATE 08003, SQLCODE -30061.
I researched "Home directory" (no java savy) and finally located the log.
Here are the most recent ArdGateLog.log entries:
2011-09-15 14:31:00,864 INFO [Thread-4]
< as above > de.bender_dv.ardgate.pords2pojo.GenericArFormat: *****
JDBCTEST :2 *****
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: deviceName:
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: modeName:
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: remoteLoc:
*ARDPGM
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: localLoc:
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: remoteNetId:
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: tpnName:
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: productId:
QSQ07010
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: userId:
JDBCTEST
< as above > de.bender_dv.ardgate.pords2pojo.ARCN0100Format: password:
SPRITE
< as above > de.bender_dv.ardgate.database.ArdConnection: url:
jdbc:sqlserver://172.17.16.63;databaseName=JdbcTest
< as above > de.bender_dv.ardgate.database.ArdConnection: driver:
com.microsoft.sqlserver.jdbc.SQLServerDriver
< as above > de.bender_dv.ardgate.pords2pojo.SqlcaBean: SQLCode: -30061
< as above > de.bender_dv.ardgate.pords2pojo.SqlcaBean: SQLState: 08003
< as above > de.bender_dv.ardgate.database.ArdConnection: Driver class not
found: com.microsoft.sqlserver.jdbc.SQLServerDriver
< as above > de.bender_dv.ardgate.application.ARCN0100Handler:
de.bender_dv.ardgate.database.ConnectException: Driver Class not found
After my changes, the result appears identical: the driver class is still
not found.
One thing that confuses me is that when I make a connection using Scott
Klement's
service program JDBCR4, I specify
'com.microsoft.sqlserver.jdbc.SQLServerDriver'
as a connection property.
Dieter, thank you, again, for all your support.
As an Amazon Associate we earn from qualifying purchases.