|
Sad Vern, you can't even spell the name of your product. :-)
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Vern Hamberg <vhamberg@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/25/2010 12:35 AM
Subject: Re: Navigator question
Sent by: midrange-l-bounces@xxxxxxxxxxxx
<verndor response>
Thanks, Luis!
Connecting to any database with RUNSQLSTM or with embedded SQL requires
an RDBDIRE be defined - and have a DRDA provider for that database.
These are like ODBC in the world outside DB2 for i. No non-DB2 RDBMS has
one other than Oracle. Just like ODBC, these providers work only for the
flavor of database that they're made for.
So we have a product called RPB2SQL Integrator that lets you connect to
non-DB2 (well, it could go there, too) SQL-ish database systems. It's a
software development kit - a SRVPGM with procedures for doing all the
work. IBM has something like this, too, and much more expensive. And
there are Java solutions you can code yourself, which'd be free but
require learning a different code skill.
All our examples are in RPGLE ( a few in ILE COBOL). I've never tried
doing anything directly in ILE CL - easier to manage everything in RPG,
in my opinion. But a CALLPRC and CALLP aren't all that different, mayhaps.
If interested, give a call at 888.RJS.SOFT or email me directly about a
quick demo.
</verndor response>
Luis Rodriguez wrote:
Well, Most of the times you can connect to a DB2 table withoutproblems....
(Sorry, could not resist :-) )<LGillespie@xxxxxxxx>wrote:
Seriously, I think that there are some products than can allow you to do
that (Time for a vendor response).
Regards,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
On Mon, May 24, 2010 at 4:51 PM, Lance Gillespie
list
Is it possible to connect to a non-db4 table in the
'run SQL scripts' interface?
It would be nice to be able to use this to update
other tables from db4 data (and maybe vice versa).
Thanks,
Lance
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
--To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.