Legacy Datastore Migration via DML Mapping and Script Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy datastores, such as IMS DB, IDMS, ADABAS, and VSAM, are complex and difficult to maintain or expand, and their integration with new systems is hindered by non-extensibility, incompatibility, and limited openness, making it challenging to achieve IT agility and requiring skilled programmers.
Innovation Solution
A system and method for migrating legacy datastores to target database management systems by converting legacy datastore information into target database system information, mapping legacy datastore calls to DML statements, and generating scripting language for the target database management system, allowing migration to NoSQL or relational databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If legacy datastore structures (IMS DB, IDMS, ADABAS, VSAM) are maintained, then data storage and retrieval functionality is preserved, but system complexity increases and adaptability to modern systems decreases
Solution Approach 1:
The patent introduces a migration system as an intermediary that converts legacy datastore structures into modern database formats. The system includes a conversion module that translates legacy data models (IMS DB hierarchical structures, IDMS network models, ADABAS files, VSAM datasets) into contemporary relational or NoSQL database schemas, enabling integration with modern systems while preserving the original legacy systems.
Solution Approach 2:
The migration process is divided into distinct segments: analysis of legacy datastore structure, extraction of data and metadata, transformation to target database schema, and loading into the modern database. This segmentation allows each legacy system type to be handled with specialized conversion rules while following a unified migration framework.
2Reliability
If legacy datastore structures are maintained, then existing applications continue to function, but ease of operation and maintenance deteriorates
Solution Approach 1:
The migration system creates a copy of the legacy datastore in a modern database format. The copying process preserves all data and structural relationships while transforming the physical storage format. This allows the original legacy system to continue operating unchanged while the copied modern version is easier to maintain and extend.
3Manufacturing precision
If manual migration processes are used, then conversion accuracy can be maintained, but productivity and time consumption decrease
Solution Approach 1:
The migration system performs self-service by automatically analyzing legacy datastore structures, generating appropriate conversion scripts, and executing the migration process without requiring manual intervention for each data element. The system includes built-in conversion rules for common legacy formats that automatically translate to modern schemas, maintaining accuracy through systematic rules while achieving high productivity through automation.
Solution Approach 2:
The system performs preliminary analysis of the legacy datastore structure before actual conversion, generating a migration plan that identifies all data elements, relationships, and conversion requirements. This preliminary action allows the system to prepare transformation scripts in advance, ensuring accuracy while reducing actual migration time.
4Reliability
If legacy datastore systems are used, then existing data is preserved, but device complexity and skill requirements increase
Solution Approach 1:
The patent replaces the mechanical complexity of legacy datastore management with an automated software system. The migration tool substitutes manual programming and data manipulation with automated conversion processes that handle complex transformations between different data models (hierarchical to relational, network to relational, etc.), reducing the need for specialized programming skills while preserving data integrity.
Data Source
AI summary
System and method for migration of a legacy datastore include converting legacy datastore information from the legacy datastore to a target database system information. The target database system information belongs to a target database management system. A legacy datastore call is mapped to a data manipulation language (DML) statement. The legacy datastore call requests the legacy datastore information. Scripting language for the target database management system is generated using the DML statement.