Channels ▼


Veryant vCOBOL: Mainframe Migration and Modernization

Veryant has refined its vCOBOL Enterprise tool with a view to increasing its adoption as a means of migration and compatibility with legacy mainframe and Micro Focus COBOL dialects.

Upping its debugging capabilities at the same time, Veryant says that vCOBOL Enterprise is a cost-effective alternative to legacy COBOL dialects commonly found running business-critical transaction processing systems.

"With an estimated 200 billion lines of COBOL still in use at enterprises worldwide, there is enormous need to preserve these large investments in data, yet evolve existing COBOL applications into more modern and useful resources at the same time," explained Dovid Lubin, vice president, Veryant.

To date, vCOBOL has proved useful when migrating COBOL applications off of IBM mainframes. The product has also been used to drive interactive and batch type applications on open systems. This new release tries to extend the value of companies' existing COBOL assets by decreasing annual software licensing expenses and enhancing interoperability with enterprise technologies such as XML.

"Developers using vCOBOL Enterprise are able to develop and deploy business-critical COBOL applications across UNIX, Linux, and Microsoft Windows based systems from a single source code base without the need for any platform-specific work," said Lubin. "This makes COBOL investments easily accessible to virtualized cloud and traditional client-server environments, and increases their value to enterprises."

In the latest vCOBOL release, Veryant has added:

  • enhanced compatibility with legacy COBOL dialects (support for XML PARSE and GENERATE)
  • support for common Micro Focus COBOL compatible library routines
  • debugging improvements so users can trace paragraphs and programs as they execute
  • mainframe compatible date, time, and delay callable services support, to provide current local time and date in several formats and conversion of dates and times
  • the ability to make recursive calls, so a program can now directly or indirectly execute itself

These enhancements, along with continued integration with UniKix Mainframe Rehosting technology from Clerity, make vCOBOL an ideal, cost-effective alternative to legacy COBOL dialects on open systems.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.