RE: Accesssing External Databases -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Accesssing External Databases
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Wed, 13 Sep 2017 19:16:15 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Or it wasn't in your classpath when you started your JVM. Once your JVM is started, the classpath is permanently fixed. If you're doing this via 5250, try starting a new session.

-----Original Message-----
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Wednesday, September 13, 2017 10:21 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Accesssing External Databases

Appears that you didn't add the JDBC driver to your classpath...

You might want to investigate Deiter's ArdGate...
https://sourceforge.net/projects/appserver4rpg/

Allows for simple embedded SQL usage..

Charles

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Accesssing External Databases , Alan Shore

This mailing list archive is Copyright 1997-2026 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.