|
View previous topic :: View next topic
|
| Author |
Message |
AjmalMohammed
New User
Joined: 02 Jun 2010
Posts: 10
Location: My Cubicle, Hyderabad, India
|
|
|
|
Hello,
I'm currently in a project that involves migrating all the Cobol,Db2,Cics,IMS codes to the DotNet technology. Does anyone here have any experience regarding this? If yes, i'd be grateful if you can share your experiences.
Regards,
Ajmal. |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| DotNet technology, isn't that windoze ??? |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
Since the DotNet technology boys convinced your managers that the conversion would be - easy
- painless
- contributing to the ROI
I imagine the DotNet technology boys would have manuals, instructions, ideas on how it is done.
anyone who went thru this, is probably nolonger lingering around Mainframe websites,
they are all too busy trying to complete this easy/painless conversion, get it to work and keep their jobs.
If you expect IBM to help you convert off of their products to another,
you are as clueless as the managers who bought into the DotNet technology. |
|
| Back to top |
|
|
mtaylor
Active User
Joined: 20 Feb 2009
Posts: 108
Location: Kansas City
|
|
|
|
Notice how the op uses 'codes' to refer to programs. I've noticed that only people from a scientific computing/fortran backround do this. Interesting.
There used to a product that converted Cobol to 'maintainable' Java, the web site disappeared some time ago however ('jazillian'). |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| Does anyone here have any experience regarding this? If yes, i'd be grateful if you can share your experiences. |
Yes - the process is not painless. . .
IMHO - it is far easier to migrate mainframe applicatons to unix than some Win-based environment.
No matter what the sales people or some managers want to believe, Win-based environments are still not ready to replace a mainframe environment. . . Again, imho.
Moving database definitions and data is the easiest part. . . Depending on which types of files are used, which utilities are used, and what level of integration exists on the mainframe there may be major re-work needed.
There are some stand-alone departmental systems that can be moved with not too much effort, but major systems may take years to move (if the project is even completed).
Several of the places i've worked with over Y2K* and since then have asked if i might participate in moving their migrated processes back to the mainframe. . .
If part of your migration is to port the application "code" as well, better pack a lunch - it will take quite a while to convert/re-write all of the functionality . . .
* (Y2K was the spearhead to get many things replaced on Win-based systems rather than remediate the applications to be Y2K compliant - many of those managers wanted badly to hear that buying a replacement would only require converting the data and using the newly purchased applications) |
|
| Back to top |
|
|
|
|
