AWS, Google and Azure demo of modern mainframe card application

What's modern or mainframe about this since the entire application is transpiled COBOL courtesy of MicroFocus (which I have memory of from another non adjacent decade) and the underlying VSAM record structure which is simply ETL'd?

Before submitting this I double took because I first encountered Microfocus migration tools in the early dotnet days, because I was wondering if I missed the possibility that AWS has a JCL runtime. Then I realized that the portability claims meant that everyone would need a JCL cloud runtime, which is unlikely, and you can find the Microfocus JCL documentation here: https://www.microfocus.com/documentation/server-express/sx51...

This is still a CICS implementation. I happen to think CICS, sanity checked, is invaluable. But licensing costs are commensurate with IBM philosophy. MTS Microsoft Transaction Server that appeared in NT 3.1 and justified learning to lock down the object interface security of every dll we had on disk back in the day (NT group permissions all the way down to SYSTEM heterogeneous masking of what can possibly talk to what. Wanna run notepad.exe without written sign off, nah. These boxen were on public IPs.) Such was the licensing value proposition. MTS has long been deprecated. But it's impossible to quickly appreciate what free transactions with mainframes meant in 1995. This should be leveraged again for the current multi systems and legacy parity cloud.

Microfocus JCL runtime I think is unique, deriving from a Seven Dwarfs hangover reverse engineered codebase.

Thus nothing here is open or cross anything without Microfocus licensing. Not inexpensive iirc. And I couldn't imagine that without support even if my experience was recent.

Edit invaluable not invalid about CICS. How is Chrome changing the literal meaning of my writing with complete word substitution /after/ I've seen my original intended word on screen for minutes and made no change in my text whatsoever? :: Ed2 added question mark.

Interesting demo. The GitHub here and the demo (need LinkedIn account?) is in linked discussion by https://www.linkedin.com/in/garycrook

“Last week, Amazon Web Services (AWS) published their IBM #Mainframe Card application as open-source.

In 3 HOURS, using Heirloom®, we deployed it to 3 different cloud platforms - AWS Elastic Beanstalk, Google Cloud App Engine, and Microsoft Cloud Azure App Service. All 3 provide cloud-native infrastructure for resiliency and dynamic scaling. No additional vendor proprietary software needed - literally plug & play.

Hour 1 - pull from the repo, organize the project workspace, and transpile the application code into a single Java application package (.war). ~35K LOC processed in < 3 seconds, zero changes to the application code, zero errors.

Hour 2 - migration of VSAM data into target relational cloud database - an RDS PostgreSQL instance on AWS.

Hour 3 - application configuration and deployment to the 3 cloud platforms (using exactly the same Java package on each).

With provisioned infrastructure and configuration complete, the entire process can be automated using a CI/CD pipeline, migrating the application to the cloud in just a few minutes.

#agilityMatters #humbleBrag #mainframeMigration #mainframeModernization #COBOL #PL1 #cloudAgnostic #multiCloud” and a video posted by him under LinkedIn.

The beatings will continue until Andy, Sundar, and Satya own all the machines.