The secure way to remove Mainframe Assembler


Until the end of the 1980s insurances, financial institutes, government authorities, and airlines had no choice but to develop their core applications in Mainframe Assembler. Changed and extended over and over, the knowledge about the inner detail logic of these systems died away. While the old-time programmers retired, thousands of these systems are still alive – difficult to maintain and blocking strategical moves.



How often have you heard about Assembler projects failing because they believed in this “we’ll convert 70% automatically” or “our offshore Assembler experts will solve the problem”. Let us be fair: The error-free transformation of Assembler code to a “real” computer language is one of the most challenging tasks in IT. We know, because we accomplished it: the latest extension to our Njema product offers the solution.



The project’s success depends on knowing in advance all the details of every single Assem­bler statement in the whole application.

Hence Njema analyzes system and user macros, coding conventions, programmers’ tricks and habits, addressing, register usage, self-modifying code, and so forth and stores this into the Njema Metadata Repository. Njema also creates a complete inventory of all data fields, their usage properties and - very im­portant – their interrelations.

This massive amount of data allows to apply AI algorithms for smart transformation and a final re-engineering across program boundaries. Thus the transformation rules do their job with respect to all other state­ments within the the whole application. Based on this knowledge a project-specific Njema Transformation Engine is built by choosing hundreds of transformation rules from the Njema Rule Repository. This engine is capable to transform all of the As­sembler entities in one processing cycle. Every cycle will reveal new possibilities for more auto­mation, which are then added to the Rule Repository.

Unique code constructs which may occur seldom or just once are covered by specific rules. In the end, the transformation engine has learned to convert the complete Assembler ap­plication into a functionally identical Cobol incar­nation: 100% automatically.


The Reward

This methodology provides a low-risk and plannable flow of the transformation project.

Your dedicated assembler Transformation Engine is built and tested while regular devel­opment and application mainte­nance is not affected at all. Continuous Code Monitoring makes sure that the code to be transformed and tested is up­dated regularly to the produc­tive program versions. Transformation errors discovered in a test cycle are never corrected in the Cobol code. They are corrected in the Njema Rule Repository, instead. The inter-connection between programs, macros, fields, data structures, files can be presented graphically from the stored metadata (s. a.). Once the final test is successful, an Integration Test will prove that the new Cobol code can go live, because it matches exactly the functionality of the former Assembler programs. The resulting Cobol code is well structured and easy to read, so regular program maintenance can continue with the Cobol programs right away.


How can all this be done when there is no documentation? Well, in fact there is reliable documentation: it is the hexadecimal so-called Object Code which Njema uses as the ultimate directive. The Object Code is what drives the Assembler program’s logic. So being able to use it will al­ways produce the correct Cobol equivalent.


Supported platforms

Currently Njema supports Assembler transfor­mations for MVS, TPF, and VSE.

Terms and Conditions


Transformation is provided as a service or by deploying your individual Modernization Fac­tory into a cloud as a Continuous-Build Pack­age. This means you will use the Engine and ITM will extend and maintain it.

Here is a simple and unbinding way to prove why this is the safest way to get rid of the Assembler. ITM performs free of charge:

1. Transformation of some hundred up to some thousand lines of source code

2. Analysis of a complete Assembler application resulting in an estimate of cost and project duration


Millions of Mainframe Assembler lines converted to Micro Focus Cobol in only a few hours

Are you kidding? No.
Any magic involved? Maybe a little.
Will the code work immediately? Yes!
What about code quality? You’ll get plain, well readable, structured Cobol.
Any manual adaptation needed? No.
Is my operating system supported? As long as it is z/OS, VSE, or TPF.
Can you prove it? Yes and for a first impression you can find a little demo and the corresponding report. We have also included a flyer here.