My guess is that they'll plug it in as a DRDA client (not server). DRDA
is the published interface for "plugging in" to DB2 of all flavors.
SQLServer, for instance, has a DRDA client that allows you to connect
SQLServer to DB2 (including DB2400). You won't set it up in ADDRDBDIRE.
MySQL will have a setup for the engine that sets up DRDA to your DB2400
that will be like ADDRDBDIRE. ADDRDBDIRE sets up your System i as a
client to another DRDA server.
There'll be the normal MySQL api available to PHP or any other software
that uses MySQL.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of bryan dietz
Sent: Monday, October 06, 2008 12:56 PM
To: Midrange Systems Technical Discussion
Subject: Re: MySQL on i
Scott, I understand the concept behind the storage engine concept, the
problem I have is "seeing" how it will be setup/configured.
For instance when using PHP and MySQL you have something like:
mysql_connect()
mysql_db_query()
How/where will the system understand those commands, are they
"comprehended" in the QZDASOINIT jobs?
That is the part I am trying to grasp.
Maybe there will be a new type of DB for the ADDRDBDIRE command, and
when you "connect to" it will put the system in MySQL mode.
I hope this sheds some more light on what I am trying to understand.
Bryan
--
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.
midrange.com
