And if the DB/2 connect software is on the client, why not connect
directly to z/OS DB/2? Going through Linux would seem to be an
unnecessary step.
Harold Grovesteen
David Boyes wrote:
Trying my best to answer your question - but this is uncharted waters
for me.
What you want to do is forward the DB/2 Connect ports to the z/OS DB/2
instance, right?
No I don't think so, because isn't that what DB/2 Connect
provides. Some how I have got to get the DB/2 Connect instance
configured to receive client request and then to forward that
onto the
actual database on z/OS.
Is there DB/2 Connect software on the client making the request? If so,
then you want to forward the ports.
If there is only DB/2 Connect on the Linux guest, then you need to write
an application to accept the query from the client, use the DB/2 Connect
client on the Linux guest to retrieve the data from the DB/2 on z/OS and
present the data back to your client. DB/2 Connect won't do that on it's
own -- it's just a way to get to the data in DB/2 and pass it to an
application. If you need to forward that data on to another client, then
you need an application that understands the needs of the client to get
the right data retrieved.
One way to do that would be to use something like Jasper Reports (an
open source WWW-based reporting widget) to drive the DB/2 Connect
software on the Linux guest, and let your clients request the data via
that interface. Jasper Reports understand JDBC, and DB/2 Connect has a
JDBC provider interface.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
