• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JNDI and as400

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am trying to use jndi for an application that currently gets server info from a properties file. The application accesses both SQL Server and db2 on as400 (iSeries). The jndi works for SQL Server but not for the as400.

When I use:

<connection-url>jdbc:com.ibm.as400://ppcdev;date format=iso</connection-url>
<driver-class>com.ibm.as400.access.AS400JDBCDriver</driver-class>

I get as error message: apparently wrong driver class specified for URL.

These two parameters are exactly the same as what is in the properties file, which has been working for a long time.

Any ideas why this is happening? TIA.
 
Marshal
Posts: 28226
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My idea, which may or may not be relevant: when I create a JDBC URL to go with the Toolbox driver, it starts with "jdbc:as400:" only. At least as far as I recall; right now I have it in Websphere, which doesn't expose the URL.
 
Steve Jagels
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've tried both jdbc:com.ibm.as400 and jdbc:as400, and both give that same error message.
 
reply
    Bookmark Topic Watch Topic
  • New Topic