Database and Data Conversion

The Database and Data Conversion phase includes the construction of new relational database structures designed to provide the same traversal and performance capabilities as the former database. All requirements for table and column naming, date conversion, element grouping, occurs clause handling and data cleansing are handled in this phase.

ATERAS® is capable of converting the following databases:

The Database and Data Conversion phase begins very early in the migration and conversion process. The new database designs become the basis for conversion and re-generation of all related applications. We offer this database and data conversion as an independent service or as part of the overall solution. If you just want a relational database we are happy to help!

Overview

ATERAS works with the customer’s database administration team to select options and define the rules used for modernization to ensure the resulting database conforms to the customer’s naming standards. Together these teams also define the rules for data cleansing, handling of “occurs” clauses, “group level” elements and “redefines” clauses.

DB-Shuttle® generates the new databases according to the naming rules and options defined. ATERAS delivers the first pass of the new SQL data definition language (DDL) within the first few days of this conversion phase. The teams make rule adjustments and re-generate the DDL as required until the DDL fully meets the customer standards.

The Database and Data Conversion is typically performed simultaneously with the application software conversion. These project phases may be performed independently. The ATERAS conversion process creates independent database and application access layers.

Process

The Database and Data Conversion phase includes the de-construction of the legacy database definitions into metadata artifacts. ATERAS enters additional rules based upon customer workbook entries which include: column and table naming date type formats, overrides for redefines and group level clauses, and preferences for each statement and clause in the resulting DDL.

The generation of brand new DDL defines a complete relational database providing the same data access as the legacy database.

This a well-defined process that includes the collection and automated inventory, analysis and measurement of the software and database components collected from the customer environment. The assessment begins with a question-and-answer workbook section and ends with the presentations of final findings and plans regarding the environment and the modernization effort. Iterations of re-collection and re-assessment may be required and performed as additional components are identified and brought into the assessment scope. The DB-Shuttle assessment process is 100% automated, so it is fast, simple and comprehensive.

The resulting relational database definitions are installed at ATERAS prior to delivery to the customer to ensure that the generated code is syntactically correct. For mainframe-to-mainframe conversions, ATERAS even delivers the JCL required to compile and execute the extracts from the legacy database. Workbenches for date type handling allow the new databases and applications to take advantage of all of the “date and time” data types in the relational database.

The legacy database definition can be re-collected and re-converted anytime throughout the project life cycle. This prevents the need to put a freeze on changes to the legacy database structure

Deliverables

The resulting relational database definitions are packaged and delivered, ready for installation in the new target environment. The data extract programs are packaged and delivered, ready for compilation and execution in the former database processing environment.

The Database and Data Conversion phase begins very early in the conversion project. The new database designs, with their new naming conventions, become the basis for the conversion and generation of the related applications.

The application software conversion takes place simultaneously with the database and data conversion. It is recommended that the database administration teams be involved in the Database and Data Conversion thread, and that the application teams be involved in the Application Conversion thread.

The following high-level tasks take place during the database and data conversion phase:

Provide a Database Definition form for each IDMS schema listed in the Environment Form
Provide reports regarding occurs clauses, redefines clauses, group levels and potential date fields
Provide guidance in correctly and completely filling out the Database Definition form(s)
Import the schema/database definition report(s)
Generate the initial SQL Imager load summary reports for the schema(s)
Review the complexity reports for the schema(s)
Review log messages for any errors during the import and initial parse phases
Load the table naming rules defined in the submitted Database Definition form(s)
Load the column naming rules as defined in the submitted Database Definition form(s)