<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/d69501870e8246529e95564082bf0490&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/d69501870e8246529e95564082bf0490-00001.gif</thumbnail_url><duration>229.5666666666666</duration><title>Loom: Exploring Legacy Application and Transpiling to Python</title><description>In this video message, I discuss a second scenario where we are dealing with a large legacy application written in RPG, COBOL, and using CL scripts. Our goal is to understand the application and create a web application that allows software architects to navigate between different modules and see the connections. To achieve this, we need to process the existing code and store the data in a model repository. We require RPG, COBOL, and CLL parsers to understand the code and store the results in a homogeneous way. The web application will query the model repository and provide necessary visualizations for software architects to make decisions, such as migrating components to Python. I invite you to watch the video for more details.</description></oembed>