Converted programs may be deployed on the platform of choice
The resultant converted programs may be deployed on the platform of choice, as the choice of a relational database supported by MigrationWare includes all of the major relational databases which will deploy on the mainframe or distributed platform.
- Close to 100% automatic translation
- Conversion of ADABAS :
- Microsoft SQL Server on Windows
- IBM DB2 (or UDB) on the mainframe
- IBM UDB on Windows
- IBM UDB on Unix
- Oracle on the mainframe (existing z/OS Oracle License)
- Oracle on the mainframe (z/Linux)
- Oracle on Windows
- Oracle on Unix
- Supports deployment to both EBCDIC and ASCII
- No black boxes or run-time dependencies
- No license or maintenance fees
COBOL programs generally interface to ADABAS in one of two ways: By means of ADASQL or through the Direct Call interface. ADASQL requires that SQL like code be embedded into the COBOL, whilst the Direct Call Interface executes calls to the ADABAS API after setting up a number of parameters with information intended to direct the nature of the database interaction.
In both cases MigrationWare’s approach is to address the conversion by retaining the original database record structure that is used by the programs and to replace the calls to ADABAS with a combination of embedded SQL for primary tables and a call to I/O modules for any child tables. From these databases access the original database record is reconstructed.
In this way the converted programs retain their original structure and flow and require minimal code intervention.
A conversion of ADABAS to relational database format, must consider the essential differences between what is a record level database and a file level database, thus normalising the data structures entails eliminating group levels, and recurring groups. Recurring groups are handled in one of two ways, if the numbers of occurrences fall below an agreed threshold then the structure is flattened out and included into the primary table, if however the number of occurrences exceeds an agreed threshold then a new child table is generated.
The new table DDL is refined with agreement from the customer and once finalised, data migrations programs are automatically generated that will read the data from the original ADABAS database, and reformat it into the require load file format for the target database. If a change in character set is required as a result of a platform change, then the conversion from EBCDIC to ASCII is performed by the data conversion programs.
The standard approach entails MigrationWare delivering a conversion service that will require a client (or partner) to deliver all applicable code, including program source code and dataset definitions to MigrationWare. MigrationWare would then undertake the conversion of the program code and database DDL to the required target format. The clean compiling converted programs as well as the new database DDL and data migration programs would be delivered to the client for testing and implementation.
MigrationWare would remain active in a support role throughout the testing phase should any issues surface that are related to MigrationWare's conversion service.