Re: ODBC from IFS

> Don, you've got a database with no central control.  And while I
sympathize
> with your desire to access every database from the iSeries, I don't see
that
> happening anytime soon.  Why don't they standardize on SQL Server, instead
> of a disparate group of databases?
>
> Anyway, the issue is not whether the job can be done by the iSeries, but
> whether the database vendor supports non-Windows platforms.  It's up to
the
> database vendor to provide drivers.
>
> So now it's a business decision.  If a given database vendor does not
> support universal access, then anybody who uses that database is locking
> themselves into a proprietary (in this case, Windows) solution.

Amen, Joe, I agree, but your preaching to the Choir.   I have been trying to
get them (here) to standardize to the iSeries but am not in control here.
We actually do have 1 mission critical application (and this is another
subject..) that is windows based that utilizes Dbase IV as it's database.
We also have a project tracking system that is MS Access & 2 phone systems
that 1 is dbase III and the other is Microsoft Access.   Our User
departments are allowed (not supposed to but will anyway) to run amuck and
sometimes purchase systems without IT approval, but we're (IT) still
responsible to maintain and interface into our enterprise systems.  Our
enterprise systems are JD Edwards World & OneWorld plus another major
iSeries application written in COBOL.

I have a few web applications that I have written that utilizes our iSeries
databases, but I would like to be able to create web & non-web applications
that I could interface into all of these applications.  The windows database
access applications end up being written in ASP by our 1 Microsoft
Developer.  And I wind up writing the non-web java applications to
manipulate data and such.  If I could access all windows & non-windows
databases, I could make a case to move all or most of our web & non-web
applications to a more secure and reliable platform (iSeries).

> On the other hand, if you insist on storing mission critical data on
> databases that provide only Windows access, then you could conceivably
write
> your own universal driver that sits on one of your Microsoft PCs.  This
> driver would accept requests from the iSeries, process them, and send the
> results back to the iSeries.  This would probably be quite a nifty
product!

I believe that this is what DataDirect has done.  Their Windows drivers
reside on a PC Server that can be accessed via JDBC.  But they're too
pricey.

> Hmmm.  That's a real thought.  A Type 4 JDBC driver whose sole purpose is
to
> talk to a Windows ODBC client.  Verrrrrrrrrrrry interesting...

Joe, send me an order form, I want to get my order in for your new Type 4
JDBC driver that will access any Windows ODBC client.
This is currently beyond my technical ability at this time.  I'm an old 20+
year RPG'er that began learning all this fun new technology about 2+ years
ago. (and by the way, I agree with you on deployment complexity for
WebSphere :)

Thanks for your response.

Don McIntyre