PKS - Solutions - System i - Making Applications Platform-Independent

Migration Tools 400 OCC

The migration tools 400 OCC create executable code for Windows, Linux and UNIX based on existing RPG, Cobol, CL and DDS source code. System i developers can execute their applications in any desired production environment without having to learn Java.

Solutions at a Glance

IBM EGL

System i

Prolong the Lifecycle
of Applications
------------------------------
Improve the Acceptance
of Applications
------------------------------
Making Applications Platform-Independent
------------------------------
Cutting System Costs
------------------------------
Improving
Competitiveness

Solutions - System i - Making Applications Platform-Independent

Evolution ²·º = Technological Innovation x Process Innovation

Making Applications Platform-Independent

The Problem

An application has been developed in System i in RPG or Cobol. This very application is now needed in a production environment on a Windows, UNIX or Linux platform with an Oracle database, SQL server or DB2/UDB. Due to time and cost constraints, rewriting the application would not be a wise approach.

The Solution

Using automated tools, the existing application is migrated to the desired production environment. Up to 100% of this procedure can be automated. Maintenance and further development can be done in System i as usual because only the application's source code (RPG, Cobol, CL, DDS, etc.) is needed for the migration procedure.

Alternatively, it is also possible to make the entire development environment platform-independent in addition to the production environment. To do so, RPG and Cobol source code is transformed once into IBM's Enterprise Generation Language (EGL). Further development is then done in the platform-independent EGL environment, which offers highly improved possibilities in contrast to RPG and Cobol. The applications can then either be run natively in System i or in Java on any platform.

Procedure

Analysis of the application and rough draft of concept with initial cost estimate (1-2 weeks)

Through a prototype (proof of concept), the procedure is controlled on the basis of a small

part of the application (2-4 weeks)

Migration project with customer involvement (3-9 months)

Suitable Tools

Server Builder 400	Universal Client
Migration Tools 400 OCC
Migration Tools 400 EGL
Reengineering Tools 400 EGL
Transformation Workbench	Service Library 400

Success = Stability x Evolution ²·º

up | back

Sitemap | Disclaimer | Home

Migration Tools 400 EGL

The migration tools 400 EGL transform existing RPG and Cobol applications into IBM's Enterprise Generation Language (EGL). This opens up entirely new perspectives for modern software development that go way beyond RPG while simultaneously protecting the application’s existing functionality.

Universal Client

The Universal Client consists of a well-balanced range of various clients for the web, Windows and the green screen, all of which can communicate via the XML standard with migrated apps in Windows, Linux or Unix, as well as the original RPG and Cobol programs in System i.

Service Library 400

Service Library 400 is a library of services (C++) that pro-vides System i with functio-nality for Windows, Linux and UNIX. The library comprises all relevant interfaces like data-base access, dialog interface, printer interface, system APIs, and over 200 CL commands including all pertinent object types such as queues, data areas, spool files, libraries, messages, etc. The library can be used in conjunction with C, C++, OCC, EGL, Micro Focus Cobol and Java.

german

Downloads

Direct contact
for:
System i / AS/400,
System z
Adabas / Natural, IBM EGL,
License Center, Public Relations