Suggestions related to migration from VB to .NET

Question

1.00/5 (1 vote)

See more:

Hi Friends,

There is a windows application developed in VB.
It is using the data base DB2.
Application is communicating with DB2 by means "MainFrame Programs".
Here an interface is used to convert the VB calls to "MainFrame Calls".

Frontend:
Windows developed in VB 5.0

BackEnd:
DB2

MainFrame:
Lot of Business logic is added in MainFrame programs. This will communicate with DB2. Lots of batches are also present.

First time, I am seeing this architecture in my life.
Whether you pupils heard of this architecture....
If yes, How can we migrate this project to some other ?

I am reading the we can directly connect with DB2 from .NET application.
Can we write procedure in DB2 and call the same from our .NET code ?

Please suggest guys...

Posted 15-Jun-15 5:10am

Nibin22

Add a Solution

2 solutions

Solution 1

I googled "connect to db2 from .net" for you and this was the first result

Connect to DB2 from Microsoft .NET[^]

Posted 15-Jun-15 5:32am

F-ES Sitecore

Comments

Nibin22 16-Jun-15 1:21am

F-ES Sitecore..
thanks for your answer. I googled and read the article already. And hence i got to know that we can connect from DB2 from .NET.
But thinking about migration of a big project with number of Business logic written in MF, I posted this question to get the answers from the ones who already experience this issue or worked in this king of project...

F-ES Sitecore 16-Jun-15 4:06am

Personally I'd look to take the logic out of the mainframe and into my code, and just leave the db2 stuff as it is (may looking to migrate to the likes of SQL in the future). You're going to have to just re-write the vb apps though, taking the opportunity to improve them as they're probably not very well architected and won't be OO in nature.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CHill60 · Accepted Answer · 2015-06-15T06:14:00

This is quite a common architecture, often used to give a more "modern" frontend to legacy mainframe "green-screen" applications, with improved validation, appearance etc.

If the VB5 programs are just running DB2 queries then see solution 1.

However, you have mentioned

Quote:
Lot of Business logic is added in MainFrame programs. This will communicate with DB2. Lots of batches are also present.

In which case you may need to instigate the running of those programs (from VB) rather than just connecting to DB2 (or you may need both).

This now depends on how you are (currently) connecting to the mainframe, which emulator or other communication protocol you are currently using or intend to use. That will also depend on what kind of mainframe it is, whether you are using IMS, CICS, etc etc etc. Here is a starter[^] search

In the past I've used direct communication, emulators and screen-scraping.

If you are intending to replace the mainframe business logic (in which instance I would ask "why?") then be sure to put in place a test region ... first. And make sure that you have production-strength data in it.