Visual COBOL features

Hi All,

We are considering to buy the license and use Visual COBOL for our solution.

However, first we need to be sure that it fits our requirements.

If anyone can provide a code example (or link with this solution described) for the following that would be greatly appreciated:

1. Ability to allocate huge limits of RAM - we need a working example of creating 7 GB array and reading/writing data from its veryt last item.

2. Working example of calling a DLL written in Visual COBOL from the code written on C# - the matter is that we will be integrating the COBOL program into existing project, so we need to be sure we can do this.

3. A proof that Visual COBOL is easily integrated with could solutions (like Amazon EC2, MS Azure, etc.). Maybe examples of some existing solutions written in COBOL that are running in the clouds?

We would love to use Visual COBOL for our development. If we are sure that it fits the above requirements - we would buy the license right away.

Thanks,

Artem

Tags:

Parents
  • Verified Answer

    1. Ability to allocate huge limits of RAM - we need a working example of creating 7 GB array and reading/writing data from its veryt last item.

    This will only be possible in a 64-bit program (a 32-bit address space is only 4GB), if it's possible at all. I haven't tried it. It should be straightforward for you to install a trial copy of Visual COBOL on a 64-bit system with adequate resources and try it.

    2. Working example of calling a DLL written in Visual COBOL from the code written on C# - the matter is that we will be integrating the COBOL program into existing project, so we need to be sure we can do this.

    From the Visual COBOL documentation:

    Managed COBOL programs can interoperate seamlessly with programs in other managed languages.

    Non-COBOL projects that call COBOL code require a reference to the MicroFocus.COBOL.Runtime assembly.

    There is a small performance overhead for calls between native COBOL and managed code. There is no performance penalty for method invocations between managed COBOL and other managed languages.

    To invoke Managed COBOL from C#, you compile your COBOL as managed code into an assembly, add a reference to that assembly to your C# project, and then invoke static methods, construct objects, invoke object methods, etc. It's the same process as with any other .NET language.

    3. A proof that Visual COBOL is easily integrated with [cloud] solutions (like Amazon EC2, MS Azure, etc.). Maybe examples of some existing solutions written in COBOL that are running in the clouds?

    See community.microfocus.com/.../481.cobol-on-azure.aspx for information on Visual COBOL running on Azure. (There's extensive information in the product documentation on Enterprise Server for .NET on Azure, but that's for migrating mainframe COBOL applications, so it's not directly relevant to what you're doing.) I don't know whether we officially support running managed Visual COBOL applications on EC2 Windows images, or have any examples of that.

Reply
  • Verified Answer

    1. Ability to allocate huge limits of RAM - we need a working example of creating 7 GB array and reading/writing data from its veryt last item.

    This will only be possible in a 64-bit program (a 32-bit address space is only 4GB), if it's possible at all. I haven't tried it. It should be straightforward for you to install a trial copy of Visual COBOL on a 64-bit system with adequate resources and try it.

    2. Working example of calling a DLL written in Visual COBOL from the code written on C# - the matter is that we will be integrating the COBOL program into existing project, so we need to be sure we can do this.

    From the Visual COBOL documentation:

    Managed COBOL programs can interoperate seamlessly with programs in other managed languages.

    Non-COBOL projects that call COBOL code require a reference to the MicroFocus.COBOL.Runtime assembly.

    There is a small performance overhead for calls between native COBOL and managed code. There is no performance penalty for method invocations between managed COBOL and other managed languages.

    To invoke Managed COBOL from C#, you compile your COBOL as managed code into an assembly, add a reference to that assembly to your C# project, and then invoke static methods, construct objects, invoke object methods, etc. It's the same process as with any other .NET language.

    3. A proof that Visual COBOL is easily integrated with [cloud] solutions (like Amazon EC2, MS Azure, etc.). Maybe examples of some existing solutions written in COBOL that are running in the clouds?

    See community.microfocus.com/.../481.cobol-on-azure.aspx for information on Visual COBOL running on Azure. (There's extensive information in the product documentation on Enterprise Server for .NET on Azure, but that's for migrating mainframe COBOL applications, so it's not directly relevant to what you're doing.) I don't know whether we officially support running managed Visual COBOL applications on EC2 Windows images, or have any examples of that.

Children
No Data