Re: IBM i connection to SQL server databases via SQL or RPG

[Alan Campin <alan0307d@xxxxxxxxx>]

If you can talk to Oracle with Java without anything else, the answer would
be yes. You have to have a pure Java JDBC type 4 driver. The driver cannot
depend on any operating system calls.

On Tue, Jun 30, 2009 at 4:51 PM, Mike Cunningham <mike.cunningham@xxxxxxx>wrote:

> DB2/400 can talk to Oracle without any extra middleware?  I thought this
> was only possible if you ran the Oracle Gateway for DB2
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
> midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
> Sent: Tuesday, June 30, 2009 2:50 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: IBM i connection to SQL server databases via SQL or RPG
>
> Eric
>
> There is neither native nor embedded SQL connectivity to SQL Server -
> only to DB2 on Windows/Linux/Unix and Oracle. So you have to use JDBC or
> some other means of doing this.
>
> <verndor response>
> We have a product called RPG2SQL Integrator that gives this capability.
> It is a couple service programs, which contain functions for connecting
> to and moving about remote SQL-based databases. Any valid SQL statement
> can be run using this product, including various creates, updates,
> inserts, whatever is valid for the remote database. It does use a
> middleware PC, just as IBM's solution, WebSphere Data Integrator, does -
> I think that's the name - they change it all the time!
>
> If this is interesting to you, contact me at vern@xxxxxxxxxxxxxxx or
> Richard at richard@xxxxxxxxxxxxxxx - or call toll-free at 888.RJS.SOFT -
> an evaluation can be installed and running in 15 minutes. And I'm only
> too happy to do a demo.
> </verndor response>
>
> Regards
> Vern
>
> elehti@xxxxxxxxxxxxxxxxxx wrote:
> > What integration is available these days at V5R4M5 to enable the IBM I
> > to connect to databases on other hardware platforms via SQL or languages
> > like RPG?
> >
> >
> > Our company runs JD Edwards World ERP that resides on the IBM I database
> > (DB2).
> > Our maintenance department elected to purchase the SQL server-based
> > maintenance package ePac ( http://www.epacst.com/products.html  )
> > because ePac has a few more features than the JD Edwards World
> > Equipment/Plant Maintenance suite.  (The users said, "We don't need to
> > integrate our Maintenance Purchase Orders, Work Orders, etc., into the
> > JDE ERP system".
> >
> > Well, users are now getting tired of performing dual data entry into two
> > separate, unrelated systems that are not integrated with each other,
> > saying,
> > "We want the ePac Vendor master file to synchronize with the JDE vendor
> > master file and JDE Address book."
> > "We want the ePac purchase orders and P.O. Receivers to synchronize
> > with/ (feed into) JD Edwards purchasing."
> > "We want to maintain inventory in ePac and have JDE to expense all the
> > ePac purchases".
> >
> >
> > Recommendations from YOU?
> > We will probably export purchase order header and Detail data out of
> > ePac into a flat file and import the data into JDE P.O. header and
> > detail files via some custom batch process, and then scrub and validate
> > the data according to JDE business rules.
> >
> > Because we run SQL Server 2003, not 2005, The ePac consultant's
> > recommendation of SQL Server Integration Services (SSIS) as
> > http://searchsqlserver.techtarget.com/generic/0,295582,sid87_gci1282913,
> > 00.html# is not an option.  We don't even use the 2003 SQL Server Data
> > Transformation Services (DTS).
> >
> > What about connectivity hosted on the i?
> > For an SQL interface I would prefer STRSQL CONNECT TO functionality, but
> > the only database this screen shows is our production IBM I and our
> > high-availability IBM I machine.   How do I configure things so that
> > STRSQL CONNECT TO will show sql server databases also?
> >
> > And what commercial products allow RPG programs on IBM I to read and
> > write databases hosted in SQL Server?
> --
> 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.