you can interacte with the DB2 as any otehr data soruce behind your interfaces. the only differences are in teh connection strings and basic SQL syntax cahnges.
It's really that simple? What happens on the mainframe side.
Here is the scenario as I see it right now.
1. set up DB2 ODBC driver
2. set up connection string in ASP
3. What happens then?
By the way I have seen this link before, it was helpful. The information on this one page is price-less.
one thing that you can do to make this process simplilar to look at is to simply think of your data storage or backend support as the same basic structure. I personally have not interfaces with DB2 on a mainframe enviroment but have on teh AS/400's DB2. I don't believe the differences are great concerning the relationship in ASP.
the data per say on a 400 box is stored in physical files which in translations are basically tables to new database design standards of terminology. You can populate a recordset in ASP just a simply with a physical file (table) as from SQL Server's tables.
the structure is the same
column to rows etc..
so what comes next is exactely the same as what would come next in a SQL Server situation. Use the properly structured (syntax oriented) SQL statement to query and extract the data you need to present it.
no, the server does the work in that respect. security on the mainframe as with the 400 is more strict so that will be something to address, but as far as object creation and such in regards to communications, IIS (or whatever server) and ASP will do the work.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.