French Portugese German Danish Dutch Spanish Italian Japanese

Breathing life into
legacy applications

       Home > Platforms > AS400/iSeries

Modernization of IBM COBOL ILE As400 iSeries DB400 - Specific issues

The COBOL ILE Dialect is fairly close to standard IBM COBOL Implementations.

The primary difference is enhancements in Screen handling, and a wrapper layer around Operating-System calls.

DDS, Sub-Files Conversational Screens

COBOL ILE allows definition of COBOL screens in DDS Sub-files. Such screens tend to be used within Conversational programs, designed for a "client-server" type deployment. The screens are accessed via READ and WRITE statements, similar to VSAM file handling. SoftwareMining converts such Conversational applications to a Application-Server architecture. DDS screen definitions translated to XML/XSLT architecture which works with an Web-Server, to produce HTML screens at run-time. Although in HTML, The translated AS400 DDS screens would still have a "green-screen" look and feel. As a part of an application modernization project, many sites redesign the screens to benefit from a new look and feel.

DB400 Data Access

COBOL ILE uses standard COBOL READ and WRITE type statements to access data structures which have been assigned to DB400 (SELECT record ASSIGN TO database-record.). Ie AS400 / ISeries uses the same API as VSAM handling (keyed/ Indexed Files) for accessing DB/400 database.
SoftwareMining translates the DB400 FD's (file definitions) and record access API into Object-Relational data access classes. These classes use standard SQL for communication to the DB400 or any other SQL database. The Java translation of the COBOL ILE applications can continue running an AS/400 (iSeries) box, and access the same DB400 database. Alternatively, the database and code can be deployed on another machine (Microsoft Windows, Linux, or Solaris.

RPG on iSeries / AS400

May AS400 and Iseries boxes contain applications written in RPG and COBOL.
SoftwareMining can offer migration of RPG to Java or C# though associated partners.
In such cases, translated RPG and COBOL applications (java or C#) will continue to communicate to offer the same functionality.


IBM COBOL ILE COBOL Migration, Modernization and Rehosting Project Phases

The translation of to Java or C# applications involve
  • Asset Management: Identify all the artifacts required for translation .
  • (Optional) Business Rule Extraction.
  • Translate to target language
  • Database and Data Migratation
  • Migrate JCL / WFL / CL
  • Creation and Population of Test Database
  • System acceptance testing
  • System acceptance testing
  • User Acceptance Testing
  • (Client): Interation 2 Improvements: Screen Redesign, SOA Integration, Cloud Deployments, Coding Improvements and cleanup

IBM COBOL ILE (AS400 and iSeries) Migration, Modernization and Re-hosting References

IBM
IBM AS400, System I, I Series
SoftwareMining on Wikipedia

  For further information please contact sales@softwaremining.com


 News:


2010 May State of Maine Revenue Services Tax Office: New Java system goes live

2010 Apr COBOL to Java transformation now supported on IBM z/OS and System Z

2009 Computer Weekly Magazine article - outlines benefits of SoftwareMining's Automatic Migration.

Short Cuts:


Contact Us
Online Technology Videos
Legacy Modernization Blog

Brochures & White Papers

COBOL to Java/C# Transformation White Paper

Business Rule Extraction Brochure

Manual Rewrite vs. Automatic Transformation: Risks and benefits.


 

  © 2010 , SoftwareMining. All Rights Reserved.
SoftwareMining Ltd. Reg. Eng. 02733107. Reg Offices: 8b Accommodation Road, London NW11 8ED, United Kingdom.

http://www.softwaremining.com