PRIMA Migration Cost Calculator
to get background on current state of PowerCOBOL and use of the calculator.
Please select your options from the Shopping List by entering a resource type and quantity for each option, then click "calculate" when you have completed your selections. You can select ONE or MULTIPLE options. That would allow you to partially outsource some of the migration work you would be doing yourself. Option 7 for PowerCOBOL is a complete End-to-End process and combines several of the other options, but at lower cost than if you selected them individually.
The Shopping List
Shopping list option Description
CREATE an OPTIMIZED Relational Data Base (ANY flavour) table set, in Third Normal Form, from your COBOL INDEXED FILE definitions (PC ISAM, or mainframe VSAM/KSDS, COPY books, or from definitions in COBOL code).A set of normalized tables is created for each indexed file with OCCURS, REDEFINES, Group levels and data types all catered for.
CREATE COBOL LOAD programs to load the existing INDEXED FILE data into the new RDB table sets.
CREATE a DATA ACCESS LAYER of objects in COBOL (using Embedded SQL) that can manage your new table sets. These compiled objects do all possible actions against data and manage each table set more efficiently than scripted or interpreted DB access.
CREATE a DATA ACCESS LAYER of objects in C# (using LINQ) that can manage your new table sets. These compiled objects do all possible actions against data and are (on average) 5 times faster than ESQL. Ideal for cases where exceptional performance is required, but only available for Network RDBs.
REFACTOR your existing COBOL Legacy code (ANY flavour COBOL '85 compliant) to replace INDEXED FILE access with DAL access. (Requires that RDB and DAL have been created...) This Transformation replaces all COBOL indexed file access in your code, with invocation of DAL object methods, using separate threads (instances) for READ and WRITE.
Legacy COBOL programs
TRANSFORM Fujitsu PowerCOBOL sheets into Windows Forms, with the scriptlets stripped out to a separate OO COBOL code-behind Class for each sheet. File access and business logic remains untouched.
MIGRATE Fujitsu PowerCOBOL END-TO-END. PowerCOBOL Projects are replaced with a modern Windows system. Sheets become WinForms, scriptlets become code-behind Class methods, INDEXED FILE access becomes RDB access using DAL objects (LINQ or ESQL). Your antiquated PowerCOBOL Projects are replaced by a modern Windows .NET system.