Intelligent, Custom and Highly Automated Cross Platform Database and Application Migration

COBOL to IBM DB2 Migration

Migrate from COBOL to DB2 with the help of our Ispirer Migration and Modernization Toolkit! It supports Cobol to IBM DB2 conversion of any complexity and can be easily customized according to the particular requirements of any migration project.


Why Ispirer MnMTK 2015 for COBOL to IBM DB2 Conversion?

The main purpose of Ispirer Systems is to carry out a high-grade and top-of-the-line database migration. We personalize our migration tool Ispirer MnMTK in such a way that a customized version can fully satisfy a client's business requirements.

Our main advantages:

  • High quality and experiences technical support: our technical team has a tremendous experience in migration projects of different levels of complexity.
  • Customer-oriented approach and Fast Customization: we personalize our migration tool in such a way that a customized version can fully satisfy our client’s business needs, custom conversions and optimizations are made within 1-2 business days;
  • Pre-Sales Engagement: we demonstrate a full conversion during the evaluation before you make a decision.
  • Flexible pricing: we can offer you a wide range of options, among which you will definitely find the one which suits you;
  • Optimized Conversion: after the conversion you get an intelligent and maintainable code, without using any Ispirer's middleware.

Assessment Process

The assessment of your migration project could definitely help to weigh up efforts and the approximate cost of your migration. In order to facilitate the process, you're welcome to fill in our:

Live Presentation

Ispirer Migration Solution

COBOL to DB2

Request

Request a Quote

Ispirer Migration Solution

COBOL to DB2

Service Toolkit

Conversion Features

COBOL Program Structure

  1.  
  2. IDENTIFICATION DIVISION.
  3. PROGRAM-ID. DemoId.
  4. ENVIRONMENT DIVISION.
  5. DATA DIVISION.
  6. PROCEDURE DIVISION.
  7. FIRST-PARAGRAPH.
  8. DISPLAY "First DEMO".
  9.  

There are the four divisions:

  • IDENTIFICATION DIVISION: This is where you must enter the program name.
  • ENVIRONMENT DIVISION: This is where you define the files the program needs.
  • DATA DIVISION: This is where you declare variables, records, files etc.
  • PROCEDURE DIVISION: This is where you write the program. In the sample above this is all in one paragraph. A paragraph is a series of statements named by a label. There is no specific mark to the end of a paragraph.

Main Conversion features

  • Migrates database of COBOL’s application to DB2 database
  • Converts COBOL's programs to DB2 procedures

  • DB2:

    1.  
    2. CREATE OR REPLACE PROCEDURE DemoId()
    3. LANGUAGE SQL
    4. BEGIN
    5. CALL DBMS_OUTPUT.PUT_LINE ('FIRST DEMO');
    6. END
    7.  
  • Converts WORKING-STORAGE section with declaration variables and records to DB2 DECLARE statements

  • COBOL:

    1.  
    2. WORKING-STORAGE SECTION.
    3. 01 MY_STRING_1 PIC X(20).
    4. 01 MY_STRING_2 PIC X(30).
    5. 01 MY_NUMBER PIC 9(2) VALUE 1.
    6.  

    DB2:

    1.  
    2. DECLARE MY_STRING_1 VARCHAR(20);
    3. DECLARE MY_STRING_2 VARCHAR(30);
    4. DECLARE MY_NUMBER INTEGER;
    5. SET MY_NUMBER = 1;
    6.  
  • Converts COBOL records to separate DB2 variables

  • COBOL:

    1.  
    2. 01 MY_DATA_RECORD.
    3. 03 MY_NAME PIC X(20).
    4. 03 MY_ADDRESS PIC X(40).
    5. 03 MY_ID PIC 9(2).
    6.  

    DB2:

    1.  
    2. DECLARE SWV_MY_DATA_RECORD_MY_NAME VARCHAR(20);
    3. DECLARE SWV_MY_DATA_RECORD_MY_ADDRESS VARCHAR(40);
    4. DECLARE SWV_MY_DATA_RECORD_MY_ID DOUBLE;
    5.  
  • Converts COBOL MOVE TO/COMPUTE statements to DB2 assignment statements

  • COBOL:

    1.  
    2. MOVE 5 TO MY_NUMBER.
    3.  

    DB2:

    1.  
    2. SET MY_NUMBER=5;
    3.  
  • Converts COBOL sections (group of paragraphs or statements) to DB2 procedures. The SECTION could be called using PERFORM statement. PERFORM is converted to call of DB2 stored procedure.

  • Converts COBOL control structures to DB2 control statements

  • COBOL:

    1.  
    2. IF/ELSE/END IF
    3.  

    DB2:

    1.  
    2. IF/ELSE/END IF;
    3.  

    COBOL:

    1.  
    2. PERFORN UNTIL/END-PERFORM
    3.  

    DB2:

    1.  
    2. WHILE <condition> LOOP
    3. <loop_body>
    4. END LOOP;
    5.  
  • Converts Screen output (DISPLAY statement) to DBMS_OUTPUT.PUT_LINE

  • Converts EXEC SQL/ END-EXEC(select, insert, update, delete, CURSOR statements) statements to DB2 SQL statements (SELECT, INSERT, UPDATE, DELETE, CURSOR statements)

  • COBOL:

    1.  
    2. EXEC SQL
    3. SELECT cur_date
    4. FROM val_date
    5. WHERE cur_date < CURRENT
    6. END-EXEC.
    7.  

    DB2:

    1.  
    2. SELECT cur_date
    3. FROM val_date
    4. WHERE cur_date < CURRENT TIMESTAMP
    5.  
  • Automatically converts SQL statements in Embedded SQL (EXEC SQL/END-EXEC.) to conform to DB2 syntax

  • You can also reach us via Contacts page.

     
    Testimonials
    December 3, 2012Epicor Software Corporation, United States
    Progress 4GL to C# .Net Migration

    "Epicor has engaged with the Ispirer team to create and refine prototype techniques for migrating certain parts of the Epicor Progress ABL code to well...

    ...

    Case Studies
    May 26, 2014COBOL to .NET Conversion, United States

    Our client was a major player in market-driven innovation and science. For more than two hundred years, it has been presenting world-class science and engineering to the global marketplace...

    ...

    September 12, 2014Delphi to C# .NET, United States

    Our client was a U.S.-based health insurance company providing care services since six decades through its extensive network of hospitals and other institutions.

    ...

    Feedback

    There are blob objects in the table, and I did not know how to handle them. Thanks for the good product, in general the conversion process went perfectly.

    Read more
    Industry Events