× 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.



You mean like the SQL Client Integration exit point documented at
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/xsqlci.htm in
conjunction with a socket interface (or even roll your own comm protocol)?

Bruce

On Wed, Oct 21, 2009 at 3:07 PM, Don <dr2@xxxxxxxx> wrote:

Hey Scott...

Well, while we're looking at hypotheticals...why couldn't some API open a
commlink to a target box with a non-DB2, but supported, DBMS on it. Query
the structure and engines, open the table desired, as desired, then use SQL
constructs to do I/O remotely and pass the items across in the same concept
that we use remote databases on the AS/400 now??

DR2

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Wednesday, October 21, 2009 2:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: IBM i "Open I/O" Architecture

Hi Don,

dr2@xxxxxxxx wrote:
How about Oracle, etc??


Hmmm.. I'm just brainstorming here, I don't know all of the details of
the Open I/O support. But here is what I suspect:

a) You'd create a PF on i with the same fields & keys as the oracle
file. (Potentially, you could get the DDL used to create the table on
oracle, and use it to create the same table on i)

This would give you the external definition of the file.

b) You'd write handlers that received the key and record information,
and used it to build the appropriate SQL statements to get the record
from Oracle,and then return it back.


Is this easier than just running the SQL statement to begin with? IMHO,
probably not.
--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.