This is the most efficient and agile way of transforming legacy applications.

Re-hosting: Running the legacy applications, with no major changes, on a different platform.

Thus it can provide greater compatibility to legacy applications.

This is done for backward compatibility reasons, as many legacy applications are hardcoded to use that path.

Furthermore, legacy applications that attempt to access hardware directly cannot do so in user mode.

More specifically, legacy applications that aren't supported by other platforms.

Once the legacy application is installed, we see the first part of the integration in action.

It was targeted for a mainframe market, where many legacy applications tend to use a lot of very short tape volumes.

They are long-running and implemented through legacy applications hosted by providers.

Both versions can run 32-bit legacy applications without any performance penalty as well as new 64-bit software.