By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,756 Members | 1,721 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,756 IT Pros & Developers. It's quick & easy.

.NET integration and development - best version of DB2 to use, tools, etc?

P: n/a
My new client is running DB2 6.1 on IBM mainframe (z/OS).

They are running DB2 Connect ver. 7.2 to connect to database. (If you
cannot already tell, I'm new to DB2.) I'm not sure what DB2 Connect
does for them, as I have not yet interviewed mainframe development
staff at client company. I assume that it eases coding to access
back-end DB2 database from front-end mainframe source code - is this
true?

I am going to help build .NET pieces of legacy application, based on
mainframe
coding technologies, and platform. As well, I will be converting
current pieces of application from green-screens to .NET/Windows UI.

What is my best solution, including: upgrading either DB2 itelf, DB2
Connect (if necessary), or other IBM or 3rd party tools as add-ins.
I'd like to develop code for .NET Framework 1.1 on Visual Studio.NET,
so VS.NET compatibility would be best for this solution.

Fred Z.
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
First DB2 V7.2 is going out of service very soon if not now, actually.
DB2 Connect is needed only if you are attempting to connect DB2 UDB
clients TO your V6.1 z/OS subsystem.
IF the flow is the other direction, you don't need anything but DB2 UDB
on UNIXX, LINUX,WINDOWS on one side and DB2 z/OS on the other.

I believe that DB2 UDB for LUW V8.2 is required if you plan to run .NET
apps. on the db. but I may be wrong here. I know that V8.2 introduced
a lot of enhancements just for that. Go on the DB2 web site to
investigate or to www.db2mag.com for a discussion on developping with
..NET. Article: Totallt RAD: Developping with .NET

Given .NET and DB2 UDB requirements, I'd convince the client to go to
most recent versions. I don't have my docs. handy to see what version
of z/OS is/is not supported by which version of DB2 UDB Connect.
HTH, Pierre.

Fred Zimmerman wrote:
My new client is running DB2 6.1 on IBM mainframe (z/OS).

They are running DB2 Connect ver. 7.2 to connect to database. (If you
cannot already tell, I'm new to DB2.) I'm not sure what DB2 Connect
does for them, as I have not yet interviewed mainframe development
staff at client company. I assume that it eases coding to access
back-end DB2 database from front-end mainframe source code - is this
true?

I am going to help build .NET pieces of legacy application, based on
mainframe
coding technologies, and platform. As well, I will be converting
current pieces of application from green-screens to .NET/Windows UI.

What is my best solution, including: upgrading either DB2 itelf, DB2
Connect (if necessary), or other IBM or 3rd party tools as add-ins.
I'd like to develop code for .NET Framework 1.1 on Visual Studio.NET,
so VS.NET compatibility would be best for this solution.

Fred Z.


--
Pierre Saint-Jacques - Reply to: sescons at attglobal dot net
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.
Nov 12 '05 #2

P: n/a
A data provider for .NET v1.0 was available in V81 FP2. A v1.1 provider
was added in V81 FP3. Performance improvements for both went into FP4.

Support for .NET routines (ie, UDFs and procedures) were added in V82
(aka FP7) as LANGUAGE CLR. This requires a minimum of .NET v1.1
installed on the server.

Pierre Saint-Jacques wrote:
First DB2 V7.2 is going out of service very soon if not now, actually.
DB2 Connect is needed only if you are attempting to connect DB2 UDB
clients TO your V6.1 z/OS subsystem.
IF the flow is the other direction, you don't need anything but DB2 UDB
on UNIXX, LINUX,WINDOWS on one side and DB2 z/OS on the other.

I believe that DB2 UDB for LUW V8.2 is required if you plan to run .NET
apps. on the db. but I may be wrong here. I know that V8.2 introduced
a lot of enhancements just for that. Go on the DB2 web site to
investigate or to www.db2mag.com for a discussion on developping with
.NET. Article: Totallt RAD: Developping with .NET

Given .NET and DB2 UDB requirements, I'd convince the client to go to
most recent versions. I don't have my docs. handy to see what version
of z/OS is/is not supported by which version of DB2 UDB Connect.
HTH, Pierre.

Fred Zimmerman wrote:
My new client is running DB2 6.1 on IBM mainframe (z/OS).

They are running DB2 Connect ver. 7.2 to connect to database. (If you
cannot already tell, I'm new to DB2.) I'm not sure what DB2 Connect
does for them, as I have not yet interviewed mainframe development
staff at client company. I assume that it eases coding to access
back-end DB2 database from front-end mainframe source code - is this
true?

I am going to help build .NET pieces of legacy application, based on
mainframe
coding technologies, and platform. As well, I will be converting
current pieces of application from green-screens to .NET/Windows UI.

What is my best solution, including: upgrading either DB2 itelf, DB2
Connect (if necessary), or other IBM or 3rd party tools as add-ins.
I'd like to develop code for .NET Framework 1.1 on Visual Studio.NET,
so VS.NET compatibility would be best for this solution.

Fred Z.


Nov 12 '05 #3

P: n/a
Thanks for the update. I've kept a copy of this.
Merci, Pierre.

amurchis wrote:
A data provider for .NET v1.0 was available in V81 FP2. A v1.1 provider
was added in V81 FP3. Performance improvements for both went into FP4.

Support for .NET routines (ie, UDFs and procedures) were added in V82
(aka FP7) as LANGUAGE CLR. This requires a minimum of .NET v1.1
installed on the server.

Pierre Saint-Jacques wrote:
First DB2 V7.2 is going out of service very soon if not now, actually.
DB2 Connect is needed only if you are attempting to connect DB2 UDB
clients TO your V6.1 z/OS subsystem.
IF the flow is the other direction, you don't need anything but DB2
UDB on UNIXX, LINUX,WINDOWS on one side and DB2 z/OS on the other.

I believe that DB2 UDB for LUW V8.2 is required if you plan to run
.NET apps. on the db. but I may be wrong here. I know that V8.2
introduced a lot of enhancements just for that. Go on the DB2 web
site to investigate or to www.db2mag.com for a discussion on
developping with .NET. Article: Totallt RAD: Developping with .NET

Given .NET and DB2 UDB requirements, I'd convince the client to go to
most recent versions. I don't have my docs. handy to see what version
of z/OS is/is not supported by which version of DB2 UDB Connect.
HTH, Pierre.

Fred Zimmerman wrote:
My new client is running DB2 6.1 on IBM mainframe (z/OS).

They are running DB2 Connect ver. 7.2 to connect to database. (If you
cannot already tell, I'm new to DB2.) I'm not sure what DB2 Connect
does for them, as I have not yet interviewed mainframe development
staff at client company. I assume that it eases coding to access
back-end DB2 database from front-end mainframe source code - is this
true?

I am going to help build .NET pieces of legacy application, based on
mainframe
coding technologies, and platform. As well, I will be converting
current pieces of application from green-screens to .NET/Windows UI.

What is my best solution, including: upgrading either DB2 itelf, DB2
Connect (if necessary), or other IBM or 3rd party tools as add-ins.
I'd like to develop code for .NET Framework 1.1 on Visual Studio.NET,
so VS.NET compatibility would be best for this solution.

Fred Z.



--
Pierre Saint-Jacques - Reply to: sescons at attglobal dot net
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.