DEV Community

Discussion on: Who’s Suffering From Cobol?

Collapse
 
joshnuss profile image
Joshua Nussbaum

Thanks! Great overview

I wish Cobol had unit and integration tests. Would make it easier to migrate to newer tech.

Many of the companies using Cobol seem to think of their systems as permanent objects that will eventually be "finished". I wonder if that is the underlying problem, that systems really are impermanent things and we should design everything with an attitude of impermanence, ie planning and accepting obsolescence

Collapse
 
igr profile image
Igor Spasić

Excellent point, thanks!
Now thinking about it, I would say there are two 'forces': one is a wish of having permanent systems, so they can be sealed and finished and re-used forever, and then the opposite force of constant change (quite natural). So I guess the planned future changes should be taken into the software design...

Collapse
 
spgennard profile image
spgennard

Both Micro Focus COBOL and IBM COBOL have support for Unit Tests.

Micro Focus runs off the mainframe and can also run in Windows & Linux containers, making it easy to integrate with Jenkins, locally and in the cloud. You have the choice of either deploying the application as native code or jvm bytecode, .net or .net core.

The development experience includes Eclipse/Visual Studio, so the projects from these can be used to build, test, analyze, and deploy the applications.

Plus if you want to migrate an application off the mainframe you can use azure/amazon either using VMs or kubernetes.

A quick start guide on Amazon, is a good place to start.

aws.amazon.com/quickstart/architec...

microfocus.com/documentation/visua...