Jumps was developed by RDBMS, Java and MUMPS experts to automate the migration process from MUMPS. It addresses each of the migration process stages, from data migration and code translation to deployment and maintenance.
|
|
Jumps Compiler |
|
|
|
The first migration task is to convert the MUMPS code into Java™ code. Jumps Compiler performs this task automatically. It takes MUMPS code and generates equivalent Java™ code. Each MUMPS routine is compiled into a Java™ class. The compiler is written in Java™, and it is used in two modes: Statically, during migration process, it is used to compile each MUMPS routine into a Java™ class. During runtime, for runtime code execution which is supported by the language and commonly used (XECUTE command, indirection).
|
|
Read more...
|
|
Jumps Runtime |
|
|
a Java™ implementation of MUMPS runtime: Context: stack frame (NEW, KILL, SET), label calls (DO). Functions, commands, operators, special variables. Flow of control: For loops, conditionals. Devices (OPEN, USE, CLOSE). Environment: Naked reference, namespace, etc.
|
|
Read more...
|
|
Jumps Database Mapping |
|
|
|
The migrator uses a mapping GUI tool to map MUMPS trees into tables. The mapping is used for the following: Create the relational database schema, once per site. Migrate the data from MUMPS to a relational database, once per migration phase. Translate data access, during runtime, from global references into relational access (SQL and DML), over JDBC.
|
|
Read more...
|
|
Jumps IDE |
|
|
|
Jumps IDE is a state of the art MUMPS IDE that works seamlessly with Cache', DTM, GT.M and Jumps. Jumps IDE, called MDE, is an Eclipse plugin that lets a MUMPS programmer develop and deploy the same MUMPS software over MUMPS implementations or over Jumps. Since the migration may be an ongoing process, it is crucial to provide the programmers a uniform and convenient development environment. |
|
Read more...
|
|
Home 
Technology