<< January 2014 | Home | March 2014 >>


Gradual COBOL to Java migration: one piece at a time

Feedback area

This page provides a feedback area for the high level overview document :

Gradual COBOL to Java migration: one piece at a time - when a big-bang approach won't do.

Please feel free to leave any constructive comments.

How To Manage COBOL to Java/C# Projects

Feedback page.

This page provides a feedback area for the high level overview document :

How To Managing COBOL To java/C# Projects

Please feel free to leave any constructive comments.

MicroFocus Rehosting vs SoftwareMining Translation to Java or C#

Why moving to new technology is a better option

Re-hosting vs Translation – 10 reasons for choosing a good translation to Java/C# over MicroFocus Rehosting solutions.

  • Maintenance - COBOL developers are getting close to retirement age. All new developers know java and C#
  • Technology – moving to java or C# opens up the system to all kind of newer technologies: from open-source code coverage, documentation tools, performance optimizers, databases, and so on
  • Integration: Much easier to integrate Java / C# applications with other applications
  • Data-Migration (KSDS/VSAM to SQL Databases – where each COBOL field maps to an SQL Column)
  • Data-Migration – Sequential files to can be migrated to MS-Excel Spreadsheet format,
  • Data-Mining: Moving Indexed/KSDS data files to SQL databases opens up the system to host of data-mining tools
  • Costs – translation has no associated runtime costs
  • Free of COBOL legacy – in a good translation, the generated code does not require in-depth familiarity with COBOL.
  • Performance – generated code should avoid COBOL emulations where possible. For example, where possible it remove GOTOs, and REDEFINES and un-necessary formatting such as COMP-3.
  • Welcome to 21st Century ! (Well, I had to say something very positive at the end :)
Of course, that just my views !

Mainframe Apps on mobile phone

Accessing Mainframe Apps from Mobile phone

My company (www.softwaremining.com) translates COBOL applications to Java and C#.
Recently we were asked if it was possible to access the java translation of a mainframe application from mobile phones. The answer was yes off-course. Since the CICS BMS, or COBOL Display screens are translated to HTML, they it can be accessed from any cell-phone with a good browser - although the screens will be a bit on the small side. The new system however does new JSP or ASP screens to be simply plugged in without having to alter a single like of the business logic. This would allow a new screen to be designed specifically for cell phones.
Of course no one will expect the Data-Entry department to use the new cell-phone centric pages for their work. But if the cell phone centric site is merely another interface to the existing migrated application, well, it could be utilized as a public facing ecommerce site. For example, if the original application is related to Personal-Tax, a user may login using his cell-phone, name and id fields to be auto populated (and made invisible to save on screen real-estate), certain features disabled (e.g. search for other users, and etcetera.) and then the user allowed to enter his own data.
I know there will be area’s which will require careful consideration (e.g. security), but the ability to open-up the existing applications to a wider audience must be enticing!