×
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.
Classpath seems like a reasonable place to start. It's also possible your old machine had the jTDS JAR in a system directory (HIGHLY discouraged behavior), so you didn't have to set the classpath.
Do you still have access to the old machine?
-----Original Message-----
From: Larenzo Alexander [mailto:Larenzo.Alexander@xxxxxxx]
Sent: Monday, June 18, 2018 8:01 AM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>; Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: JDBCR4 on New IBM i v7r3
I hope this is the right forum to find some java help. I'm not too familiar with Java but I'm using the Scott Kement's JDBCR4 to connect to SQL Server 2012 databases. It was working well on our old IBM I v7r1 but this weekend we got a new IBM I machine and upgraded to v7r3 and the applications that are using JDBCR4 seem to not be working. I may just need to set the class path since it's a new machine or I may need a later version of the jTDS driver that I'm using or there may be a later version of JDBCR4.
I'm clueless about what to check as far as Java and JVM so if anyone can point me in the right direction I would greatly appreciate. I've been looking through the IFS to see where I have the jTDS driver but I can't remember where I stored it. Or how to check if my class path is located but I'm about to do some googling and reading but thought I would post this in the meantime..
As an Amazon Associate we earn from qualifying purchases.
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.