Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

After the migration, which are the possibilities to continue evolving the application into “modern” languages like C#, C++, etc., even without relying on XFRAME?

0
Posted

After the migration, which are the possibilities to continue evolving the application into “modern” languages like C#, C++, etc., even without relying on XFRAME?

0

If, when migrated, you want to rewrite the application, there is no limitation. Therefore, the reply is: whatever you like. You may integrate existing applications using one of the many connectors XFRAME provides for the Java and .NET worlds. Furthermore, if you want to get rid of XFRAME too, you may rewrite programs as you prefer. The JCL is converted into standard system scripting that may invoke whatever executable. The online part, when rewritten, can obviously be of whatever type. Data coming from DB2 or DL/I are stored in an RDBMS, and, as you know, it can be accessed by “modern”, languages. VSAM data are stored on ISAM: for them you have two possibilities: a) to use ISAM APIs for C; b) to use the V2R feature of XFRAME, which stores VSAM over RDBMS (with some limitations), so C or C# can access data directly from DB. Sequential files are pure system flat files, and even here, other languages may do whatever they like.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123