Technology
AMXW includes a Windows-based GUI migration tool and server components for HP e3000, HP 9000, Integrity Itanium, Windows, Linux, Sun and AIX platforms. Using the intuitive optional Windows interface, developers have access to a number of features, including the ability to review their source and target codes - side-by-side - to easily understand and compare the code changes suggested by AMXW. The Windows client is optional, since the migration may be executed directly between the source and target platforms using automatically-generated migration scripts.
AMXW includes the necessary technology to maintain references to current MPE functionality, including TurboImage, KSAM and MPE system intrinsics, file equations, JCW variables, CIERROR checking, JCL batch file, and command file execution to name a few. The MPE functionality is mapped to equivalent platform-native functionality to provide the most efficient execution.
AMXW also includes an MPE shell, referred to as 'nlsh', which can execute MPE commands with the equivalent platform-native functionality.
AMXW can be used in conjunction with other migration technologies including Eloquence (Marxmeier) to replace TurboImage, EZV (Screenjet) or edWin (Ordina-Denkart) to replace VPLUS. In addition, AMXW is compatible with the following other languages/software: MicroFocus ServerExpress/NetExpress or AcuCOBOL-GT compilers (Micro Focus), Powerhouse (Cognos), Renaissance Architect [Powerhouse to .Net] (Core migrations), T2C [Transact to Cobol] (Screenjet), SUPRTOOL (Robelle), Protos and OpenTurbo (Imaxsoft).
In addition, AMXW automates database migration for TurboImage, KSAM, KSAM-XL, Allbase and flat-file databases to the following:
- Oracle, SQL Server (using Microsoft SQL Server ODBC), DB2*, Sybase, Eloquence, Informix, Ingres, and AcuCORP's Vision.
* Requires the use of ORDAT's technology. Please contact your account manager for details.
AMXW also supports a wide range of flat file types including Sequential, Message, Circular, RIO, Catalog, Byte-Stream and temporary files. No manual intervention is required on the source code related to the flat file access and AMXW supports the exact same functionality as you currently enjoy on MPE today.
Here's how easy it is to migrate your application environment with AMXW:
First, migrate your database and files using the tool's built-in database migration functionality. For complex database migration efforts, Speedware's DBmotion (a complementary database migration utility), can be used.
Next, transfer the application source code, including your COPYLIB files, UDCs, and command and batch files to the PC where AMXW is installed and import the code into AMXW. Adapt the migration parameters to reflect your desired migration environment. Re-compile the application with the new compiler and your MPE-specific functionality will continue to run in your new environment without the need for manual intervention.
|
