That does help. In that case, set up both DRDA over TCP and the ODBC drivers. That will allow the 390 applications to access and update the data directly, and allow the desktop apps to access the same data. You can then present a quick ROI by moving the existing logic in the Access databases immediately to the new server, and decide what package to use for the WWW front end based on your applications.
----- Original Message ----- From: "Diana Reynolds" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 26, 2003 4:02 PM Subject: Re: DB2 UDB and Websphere > Okay, here is the situation, we are exploring alternatives. We have DB2 UDB running on a linux server. We have legacy systems running under cobol/cics/vsam on a 390. we have access applications with access databases on servers. We want to get to a common ground. we have loaded one of our access databases into DB2 UDB, we have also downloaded some of our legacy vsam files into DB2 UDB. Now the question is, what do we use as a common front end. We want to get to some type of web base portal type situation. I am not sure that I am explaining this very well.
