Control / modernize your Mainframe

 

Controlling/Modernizing Your  Mainframe

With the rise of efficient technologies, particularly in the Cloud,  the modernization of Mainframe environments has become a strategic priority for many companies. 

But modernizing systems that you don't necessarily have a strong grasp of isn't always easy.  Automation is a real option.   

 

The Mainframe is  still very much alive  !

The mainframe, with over 60 years of history, owes its survival to its security, a key characteristic. As it hosts strategic data, it is distinguished by its reliability, fault tolerance, and advanced encryption systems, essential for certain sectors. 

 
 

2  main strategies

are being implemented here and there

1-  Mainframe   Output

The strategy adopted in recent years has often consisted of simply withdrawing from the market, keeping the applications as they were, or modernizing them. This approach is now less popular. 

 

2-  Mainframe   Modernization

More and more companies are turning to modernizing applications directly on the Mainframe, by streamlining them, migrating them to more "current" languages, or by leveraging third-party technologies, which is now possible on the Mainframe.

In any case, although the mainframe remains a key platform for 89% of large companies, it is gradually becoming less reliant on it or evolving into a hybrid model by shifting towards the cloud. This is according to  a recent study by the IT services company Kyndryl, conducted by the consulting firm Coleman Parkes.

But removing or modernizing the Mainframe  is not simple... 

Skills are scarce: young engineers are rarely trained in these technologies, which are considered outdated. On the other end of the age spectrum, if we mention Cobol, the emblematic language of the Mainframe, Cobol programmers are often retired or nearing retirement...

As for the processes managed in the Mainframes, they are sensitive, massive, and there cannot be the slightest interruption of service or regression.

 

2  strategies

to change things gently

1-  Continuous mapping  of the system with data lineage 

Our approach is to perform dynamic reverse engineering of the Cobol code using {openAudit}, and to present the flows graphically, in the form of "maps" based on data lineage. These dynamic maps can be ultra-granular, or more ensemble-based.

The specific features of Cobol are addressed:  

  • The Programs (.cbl),
  • Structures files (.cpy).


Enhanced with a search engine, this data lineage allows you to define the origin and history of each data point.   It also provides access to the underlying business rules. Information usage patterns can be included in the analysis. 

This data lineage is based on a continuously refreshed, open and documented database, which allows for countless analyses. 

 

Thus, the platform holds no more secrets for anyone, whether they are COBOL programmers or not. It can be easily maintained, optimized, partially decommissioned, etc. 

This data lineage can be extended to a wide range of technologies to encompass the entire Information System (including the data visualization layer). This is particularly true with DB2, which is often associated with COBOL in the Mainframe.

 

2-  Catalyze   migrations to standard SQL  by automating the process

  • {openAudit} will "parse" the COBOL code, breaking down its complexity using a grammar that allows for exhaustive and ultra-granular analysis. All the subtleties of COBOL will be taken into account. 
  • {openAudit} deduces the overall kinematics and intelligence, which will be reconstructed in an agnostic algorithmic tree,
  • Based on this, {openAudit} will produce "standard SQL",
  • Then the intelligence will be minimally rebuilt in the specific SQL of the target database. 
  • All complex processes, which cannot be reproduced in simple SQL, will be handled by a third-party language. 

 

The migration can therefore be carried out efficiently and qualitatively. 

 

Conclusion 

While many companies are still hesitant to modernize their mainframe and COBOL systems, the combination of dynamic flow mapping via data lineage and migration automation with  openAudit  offers a clear and efficient solution for taking this step. Modernization can move forward rapidly, with your eyes open.

Commentaires

Posts les plus consultés de ce blog

Power BI libère les utilisateurs… Mais comment garder la maîtrise de sa plateforme dans le temps ?

De la source à la cellule du dashboard : Cartographier le SI pour le reconstruire intelligemment

Migrer de SAP BO vers GCP Looker - Garder ses données en source ? Possible ?