SELECTED MIGRATION ASPECTS
The accompanying graphic exemplary outlines the architecture of a BS2000 COBOL application and the resulting target system – in this case a Java system. The individual components of the basic system are converted tool-supported and thus automatically in the corresponding components of the target system.
Program migrationThe migration of the programs will be done depending on the base and target programming language with the following tools:
- CoJaC (COBOL to Java Converter): This tool accomplishes the conversion of COBOL programs into Java. CoJaC converts embedded, static SQL statements to dynamic SQL statements. A Java runtime system contains methods for managing the database access and connection, for reading and writing data into host variables and for error handling.
- C2C (COBOL to COBOL Converter): This tool converts COBOL programs from the dialect of the basic system to the dialect of the target system. Thereby the adaptation of incompatible commands or interfaces (e.g. file interface, middleware etc.) can be realised according to customer's requirements.
- S2C (SPL to C++ Translator): This tool realises the conversion of SPL (System Programming Language) into C++.
- S2P (SDF to Perl Translator): For the conversion of the SDF procedures (System Dialog Facility) into Perl the S2P tool is available. The generated Perl scripts use a runtime system, which emulates important features of the basic system (working with job variables, user and job switches, ...).
Database and file migrationDuring the migration, the data files used under BS2000 are transferred into database tables. In coordination with the customer LEASY, ISAM and possibly also SAM files are migrated with our tool FiRe automatically. The table structure is derived from the record structure, which is defined in the COBOL programs. The runtime system encapsulates the database access and provides methods for mapping the COBOL statements for file processing. If there exists already a database, so we also offer the possibility of an automated change of the database system including a dialect migration of the existing SQL statements.
Middleware migrationThe middleware UTM (Universal Transaction Monitor) can be replaced by our tool MidaS. UTM is used among others for controlling the dialogue programs, information exchange and user management. MidaS is designed as a Java Web Service with a SOAP interface. It emulates the required middleware functionality in the migrated COBOL or Java servers: encoding/decoding and forwarding the message, coordinating of the call sequence of the dialogue programs and masks and session management. MidaS can act as a standalone program. So it is not mandatory to use an application server such as WebSphere or JBoss.
Alternatively, we also support an automated change to another, commercial middleware product.
Screen mask migrationThere are several options for screen mask migration, any of which can be carried out according to customers' requests:
- Automated migration: The screen masks can be converted automatically by our tool MaTriX into Web-2.0-based user interfaces.
- New development: The screen masks can be newly developed corresponding to customers' requests, e.g., as JavaServer Pages.