AO Roadmap will guide you thru the changes to architecture and programming.
AO Roadmap guides you through the architectural and programming changes necessary to safely modernize your database. Defining the architectural changes involves separating the database layer (Model), the User Interface (View), and the business’s unique logic (Controller). The second part of modernization is taking advantage of RPGILE and DB2. AO employs Modules, procedures, user spaces, and service programs to generate trigger and I/O server programs.
In legacy applications, all three of these elements (MVC) are present in large monolithic programs, which makes maintenance complex, slow, and error-prone. AO Roadmap provides the strategy to help you reach your goals.
When code is repeated across multiple programs, such as those for tax or pricing calculations, it is better consolidated into service programs. This practice will foster consistency and reduce maintenance effort.
By adopting MVC architecture, IT development teams can become significantly more responsive to business changes.
Roadmap
- Migrate ISAM data to the SQL engine, one file, one library, one database, or one system at a time. By following the standard roadmap, you become competent and confident in the process. No level id (LVLID) changes! Phase 1 above manages the transition from DDS to DDL and the copying of the data. The migration/import process also establishes the metadata needed for a more serious modernization of the database. AO facilitates running parallel databases concurrently, mirroring DDS to DDL and DDL to DDS with each other. This means that both the ISAM and SQL constructs are in sync all the time.
After the transition to SQL
- AO generates a single (or multiple) data dictionaries, which facilitates the GRADUAL clean-up of the metadata and resulting tables.
- AO changes the perception of the database to modern by using long field names as aliases.
- The gradual consolidation and sanitizing of the database continues until you exhaust ROI.
- AO produces IO Server and Trigger programs from modifiable templates, providing the vehicle for change.
- Replace master file validations with DB2 constraints and migrate business logic to trigger programs. This reduces the actual code that needs to be maintained by about 80%, depending on coding standards and techniques.
- The metadata version of the database allows for the gradual implementation of MVC architecture. Low-risk testing and implementation planning keeps the process safe.
- AO associates business rules with fields/elements providing a “competitive advantage”, by allowing these discrete business rules to become reusable components.
- AO OPEN generates a javascript/html user interface based on a file. The user interface is simplified because the business logic is part of the file and constraints are handled by DB2. An API accesses the database and produces a JSON file which drives the USER interface.