The core migration and management engine delivers a fully functional and modern DB2 database, which is key for leveraging business analytics, cloud, and mobile computing.
AO Foundation migrates the legacy ISAM-like database engine (DDS) to the native SQL database (DDL). The resulting database supports SQE and incorporates sound risk and SDM/MDM management principles. The import/migration process builds the metadata from object descriptions. The AO Foundation toolset simplifies the process of sanitizing data definitions, implementing constraints, and generating triggers and I/O servers. The metadata repository is central to the modernization process. Changes made to the metadata can be implemented at your discretion. You retain control over when the metadata changes are implemented, right down to the field level. The flexibility provided by AO Foundation alleviates the challenges of modernization.
Sanitize, consolidate and reduce heritage code base by up to 80%, reducing code complexity and improving code readability and maintainability.
AO Foundation manages the sanitization of data elements and the purification of the field reference file. It is not uncommon to find multiple definitions for customer numbers across various files, perhaps differing only by a unique prefix or some minor differences. By utilizing the DB2 database engine (constraints & triggers), we can reduce your codebase by an average of 80% (depending on coding standards and techniques) while simultaneously achieving significant performance improvements. Standardizing the code enhances maintainability. The structure of the trigger programs ensures that each field has its own procedure containing the validation code, making it easier to locate issues and allocate resources. Efficiency arises from standardizing business logic in the database, which boosts both readability and maintainability.
DB2: The foundation of true modernization
We (IBMi users) have probably the most advanced commercial implementation of the DB2 database at our disposal. However, most installations continue to use it primarily as we did in the early 1990s. As a result, many advances in the database engine on this wonderful platform have passed us by.
The AO Foundation and the SQL engine are used to gradually begin sanitizing your heritage database and managing the database using the metadata repository. Then, initiate an enrichment process of the Metadata, using the new Open Access (OA) Metadata Open Standard.
If you’re still accessing your database using ISAM (DDS/CQE) and not taking advantage of SQL (DDL/SQE), you are working harder than necessary. If you want to become even more productive with SQL, constraints, trigger programs, and I/O servers, you need the structure and experience built into the AO Foundation.