Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.

Managed COBOL - An Overview

Managed COBOL - An Overview

Introduction

Speaking to a NetExpress user recently I sensed some fear at the idea of moving to Visual COBOL – a new IDE and a new language (.NET COBOL or JVM COBOL). Understandably daunting.

So I thought it might be worthwhile to give an overview of this “new language” and demonstrate that it is a force for good – not to be feared. So let’s take a look at .NET COBOL and JVM COBOL (or Managed COBOL**) and see how they fit in with procedural COBOL and the new frameworks. (We won’t discuss actual syntax in this document.)

  • Background - Visual COBOL
  • Getting Started in Visual COBOL
  • Managed Code
  • Managed COBOL running on .NET
  • Managed COBOL running on JVM
  • Managed COBOL Programming Language

Background – Visual COBOL

There are 2 Visual COBOL products:

Visual COBOL for Visual Studio

and

Visual COBOL for Eclipse

With these IDEs come .NET COBOL & JVM COBOL* respectively, or Managed COBOL as we'd prefer to collectively call them. * *

Managed COBOL is COBOL with extensions to support the .NET & JVM frameworks. This offers OO syntax support and syntax to allow us to access the available class libraries. If you are familiar with COBOL dialects, you could envisage Managed COBOL as a new dialect.

NB Both Visual COBOL for Visual Studio and Visual COBOL for Eclipse provide support for native (unmanaged) and managed COBOL projects.

Getting Started with Visual COBOL

What code changes do I need to make to get started with Visual COBOL?

None - so long as your app does not use features that are not supported in Visual COBOL (for example Panels2, DS and ACU-GT.) Core COBOL is fully supported.

Assuming this to be the case :

You can take your existing app and compile it to native code – no code changes.

You can take your existing app and compile it to managed code – no code changes.

Managed Code

This is where the 2 IDEs differ. The COBOL language looks the same (nearly **) but the output from the compiler is different depending on your IDE.

Comparing Managed COBOL compiled for .NET & Managed COBOL compiled for JVM :

 

Managed COBOL running on .NET

Now let's take a closer look at Visual Studio & .NET.

At compile time a .NET compiler converts the .NET source code into CIL code. At runtime, the CLR's just-in-time compiler converts the CIL code into code native to the operating system.

    

This means you can write mixed language applications, for example a COBOL app with a C# web front-end.

 

Managed COBOL running on JVM

Now let's take a closer look at Eclipse & the JVM.

At compile time a JVM compiler converts the source code to Java bytecode. Don't be put off by the word "Java" - the JVM was initially designed to support only the Java programming language, the associated Java programs had been compiled to a format called Java bytecode. However, as time has passed, more and more languages have been designed to run on the Java platform – including COBOL. Their compilers compile to this common format – Java bytecode.

At runtime, the JVM's just-in-time compiler converts the Java bytecode into code native to the operating system.

 

This means that COBOL can take advantage of Java Platform's original objective of "write once, run anywhere" (WORA). So JVM COBOL can run on any device equipped with a Java virtual machine (JVM), be it Red Hat, AIX or an Android phone.

 

Managed COBOL Programming Language

The ultimate aim is for .NET COBOL & JVM COBOL to be syntactically identical.

We're not quite there yet (partly because .NET COBOL is more mature than JVM COBOL), but we're working on it. **

Hence they are collectively called "Managed COBOL".

So are there now 3 COBOL compilers?

No. Just one.

The IDE takes care of this for you, but the compiler knows the format of code to generate depending on the compiler directive.

  • ilgen directive compiles to CIL
  • jvmgen directive compiles to bytecode

Summary

Procedural COBOL

  • Procedural code can be compiled to native (unmanaged) or managed code (.NET or JVM)

Managed COBOL

  • Managed COBOL provides extensions to COBOL to support the .NET or JVM frameworks
  • Compiled with the ilgen directive to run on .NET
  • Compiled with the jvmgen directive to run on JVM

 

*Product Information

JVM COBOL is available with Visual COBOL R3 as an Early Access Program. It is GA in Visual COBOL for Eclipse R4 which was released June 2011.

** Aim to get .NET COBOL and JVM COBOL to look and behave the same

This is work in progress. It is ambitious. We are not expecting 100% success and will document any differences. Therefore our preference is to collectively call .NET COBOL & JVM COBOL – "Managed COBOL".

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments

I very happy to read this good news. Thank You Paula Willis.

Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2012-06-21 16:58
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.