Tightly coupled with other ASNA .NET technologies, ASNA Monarch migrates green-screen RPG to ASNA Visual RPG for .NET. Once migrated, you compile that code with ASNA Visual RPG's compiler. You are in full control of the project along the way. Improved usability with better graphical user interfaces, increases in programmer productivity with Visual Studio, and enabling more persistent integration with other front and back office applications are just a few of the benefits.
Monarch Methodology
Over the years, we have gathered vast experience and we have developed a clear Monarch methodology that consists of four main steps:
Once the scope of the transformation project has been set and the organization has committed to follow through on the migration, then the Monarch Migration Process can be set in motion. This process consists of four main steps.
- Object Inspection: detailed information about all of the OS/400 objects involved The inspected objects include:
- Menus
- Programs
- Modules
- Database Files
- Display Files
- Printer Files
- Data Areas
- Message Files
- Visual Analysis and Strategy Generation: process used to determine how different OS/400 objects are transformed to the equivalent .NET components, and to create GamePlans for the transformation of all the objects.The Object Gallery may be broken down into several GamePlans to facilitate object migration and reuse (redundancy avoidance). Each migrated GamePlan constitutes a Visual Studio/Visual RPG Project.
- Source and Data Migration: the actual migration of the application or programs is performed. Several migration agents are run to convert each object in a GamePlan to its final Windows .NET form. Each agent will use the directives defined for each object during the previous step. The whole process will be logged in detail and errors will be separately logged to assist during the conflict resolution step.There are multiple agents used to migrate specific object types and one agent responsible of creating the Visual Studio project and solution. This diagram shows the agents with their inputs and outputs:
- Unsupported Features Resolution: detect and resolve any problems while transforming the RPG objects into .NET components. The migration logs will indicate all the issues that require further handling.