View all
Technical Capabilities
LANGUAGES
VX/COBOL - OpenVMS COBOL to ANSI COBOL
VX/C - OpenVMS C to ANSI C
VX/FORTRAN - OpenVMS FORTRAN to ANSI FORTRAN
VX/PASCAL - OpenVMS PASCAL to ANSI C++
VX/BASIC - OpenVMS BASIC to ANSI C
DCL
VX/CDD - OpenVMS CDD
VX/SOR - OpenVMS SORT MERGE
VX/JSP - OpenVMS Print & Batch
VX/DCL - OpenVMS DCL
VX/CLD - OpenVMS CLD Compiler
VX/MMS - OpenVMS MMS to make and XML
VX/LCKMGR: OpenVMS Lock Manager
API
CLI$ - OpenVMS Command Interface
CONV$ - File Conversion
VX/RT APIs
STR$ - STRING Interface Routines
LIB$ - General Routines
COB$ - COBOL Support Routines
SYS$ - SYS$ Interface Routines
PAS$ - PASCAL Support Routines
FORMS$ - DECFORMS Integration
OTS$ - Data Conversion Routines
MTH$ - MATH Routines
BAS$ - BASIC Runtime Support
EXE$ - Operating System Interface
FOR$ - FORTRAN Support Routines
EDT$ - Callable Editor
FMS$ - Forms Management System
LBR$- Callable Librarian
SMG$ - Screen Management
SOR$ - Interface to SORT
SQL$ - SQL Database Interface
FDL$ - File Definition Language
DEC FORMS/SCREENS
VX/SMG - SMG
VX/FMS - OpenVMS Forms Management
VX/DECFORMS - DECforms IFDL Compiler and FORMS$
RMS
VX/DATAX - OpenVMS RMS Data exchange
VX/FDL - File Description Language Routines
VX/RMS - SYS$ Routines for RMS
ACMS
VX/RTR - OpenVMS RTR V2 to Async RTR V3
VX/DMQ - OpenVMS DMQ (PAMS) for x86 Linux
VX/ACMS - OpenVMS ACMS(TDF,MDF,GDF,ADF) to C++
RDB
VX/PF2PC-FORTRAN - FORTRAN with embedded SQL to Pro*C
VX/SQLMOD- SQLMOD to Embedded SQL
UTILITIES
VX/CDD - OpenVMS CDD
VX/JSP - OpenVMS Print & Batch
VX/CLD - OpenVMS CLD Compiler
VX/MSG - OpenVMS Message Compiler
VX/MMS - OpenVMS MMS to make and XML
VX/LCKMGR: OpenVMS Lock Manager
VX/DATAX - OpenVMS RMS Data exchange
Having trouble finding what you need?
Get in touch with us, so we can answer your specific questions directly.
Get In Touch
technical
/
3GL
/
VX/COBOL - OpenVMS COBOL to ANSI COBOL

VX/COBOL - OpenVMS COBOL to ANSI COBOL

Overview

VX/COBOL enables VMS / OpenVMS COBOL applications to run seamlessly on x86 Linux with zero manual modifications. It automatically converts legacy COBOL to ANSI-compliant COBOL, supporting Fujitsu and Micro Focus COBOL compilers.

Designed for continuous integration, VX/COBOL allows ongoing development in VMS / OpenVMS COBOL, while automatically migrating each release to Linux, ensuring 100% functionality.

Key Features

✔ 100% Automated COBOL Migration – No manual changes needed.

✔ Continuous Integration Ready – Develop in VMS, deploy on Linux.

✔ Preserves COBOL Logic – Original structure is maintained.

✔ Fully Compatible with RMS – Uses VX/RMS for complete RMS file support.

✔ Optimized for Linux – Adjusts for 32-bit vs. 64-bit architecture differences.

✔ Supports Modern ANSI COBOL Standards – Converts VMS-specific syntax & semantics.

COBOL Migration: Key Differences & Solutions

Pointer Handling

VMS / OpenVMS initializes pointers by reference. ANSI COBOL does not allow this. VX/COBOL modifies the initialization to NULL and generates a MOVE statement in an init section.
‍

VMS / OpenVMS COBOL Migrated ANSI COBOL
05 POINTER VALUE REFERENCE FILE_NAME. 05 ANON_POINTER_001 POINTER VALUE NULL.

**Inserted in PROCEDURE DIVISION:** PERFORM /s7/INIT THRU /s7/INIT_END.
MOVE FUNCTION ADDR(FILE_NAME) TO ANON_POINTER_001.

COMPUTE Statements

VX/COBOL adjusts floating-point precision issues by appending /s7/PREC to division operations.
‍

VMS / OpenVMS COBOL Migrated ANSI COBOL
COMPUTE PCT_CNT ROUNDED = (SUB_CNT / TOT_CNT) * 100 COMPUTE PCT_CNT ROUNDED = (SUB_CNT / TOT_CNT) * 100 + /s7/PREC

**Constant Definition:**
77 /s7/PREC PIC 9V9(5) VALUE 0.

CALL Statement Changes

VX/COBOL replaces GIVING with RETURNING, adjusts OMITTED parameters to BY VALUE 0, and converts program names to lowercase for consistency.

VMS / OpenVMS COBOL
CALL "LIB$GETJPI" USING  
    BY REFERENCE GETJPI_ITEM_CODE  
    OMITTED  
    OMITTED  
    BY REFERENCE GETJPI_GROUP_NO  
    OMITTED  
    OMITTED  
GIVING RETURN_CODE.
Migrated ANSI COBOL
CALL "lib$getjpi" USING  
    BY REFERENCE GETJPI_ITEM_CODE  
    BY VALUE 0  
    BY VALUE 0  
    BY REFERENCE GETJPI_GROUP_NO  
    BY VALUE 0  
    BY VALUE 0  
RETURNING RETURN_CODE.

I-O Control and File Locking

VX/COBOL modifies the APPLY LOCK HOLDING statement to LOCK MODE IS AUTOMATIC.

VMS / OpenVMS COBOL
INPUT-OUTPUT SECTION.  
FILE-CONTROL.  
    SELECT OPTIONAL CUST_FILE ASSIGN TO CUST  
    ORGANIZATION IS INDEXED  
    ACCESS IS DYNAMIC  
    FILE STATUS IS FILE_STATUS_BYTE  
    RECORD KEY IS CUST_KEY  
    ALTERNATE RECORD KEY IS CUST_ALPHA_CODE.  

I-O-CONTROL.  
    APPLY LOCK HOLDING ON CUST_FILE.
Migrated ANSI COBOL
INPUT-OUTPUT SECTION.  
FILE-CONTROL.  
    SELECT OPTIONAL CUST_FILE ASSIGN TO "CUST,EXFH"  
    ORGANIZATION IS INDEXED  
    ACCESS IS DYNAMIC  
    FILE STATUS IS FILE_STATUS_BYTE  
    RECORD KEY IS CUST_KEY  
    ALTERNATE RECORD KEY IS CUST_ALPHA_CODE  
    LOCK MODE IS AUTOMATIC.

Why VX/COBOL?

✔ Seamless Migration with 100% Automated Code Conversion

✔ Preserves COBOL Development Workflow – Continue using VMS / OpenVMS COBOL

✔ Full RMS Support – VX/RMS ensures file operations work identically on Linux

✔ Optimized for ANSI COBOL – Fujitsu & Micro Focus compatible

✔ Supports Continuous Integration – Migrate & deploy with every release

VX/COBOL is the most complete and efficient solution for migrating VMS COBOL applications to Linux.

On this page
I
Example H2
II
Example H3
III
Example H4
IV
Example H5
II
Example H6

Frequently Asked Questions

Curious about how Sector7 can facilitate your application migration? Explore our FAQs for expert insights.

Free Code Assessment
Contact Us
Which COBOL compilers do you support on Linux?

Right now, there are two such compilers:  Fujitsu’s NetCOBOL from Agaraphobia and Micro Focus COBOL.  We have been using NetCOBOL as a compiler on Linux for many years due to its low cost, free runtime support and overall performance, continued support and development and breadth of features.  Other ANSI COBOL compilers can be accommodated if required.

What is the percentage of translation for OpenVMS COBOL to NetCOBOL, for example?

The percentage of translation is near 100%.  In terms of lines of code, where an application represents 5 million lines, there can be a few dozen places where some pre-translation updates are required.  These updates can usually be taken back to the OpenVMS environment, but a few may remain.  We have a mechanism to account for those issues.  What is more important is that there are no fixes required, post-translation.

How long does it take to automatically convert 5 million lines of OpenVMS COBOL to ANSI COBOL?

The translation is done on Linux and can take about 15-20 minutes on a small Linux instance.

How does VX/COBOL ensure no code freeze is necessary even on a long project ?

The key to a zero-code-freeze migration project—which is absolutely critical for any effort lasting more than five months (as is typical with large applications)—is 100% automated conversion from OpenVMS COBOL to ANSI COBOL.

Our clients face no restrictions when it comes to ongoing maintenance or development on OpenVMS during the migration. It's Sector7's responsibility to ensure that the toolchain is precisely tuned so that there is never any manual intervention required to translate, compile, link, and test the application on Linux

How do you test the translated code?

Immediately after the translation is performed, the remedied code is compiled on Linux using a compiler listed above.  For instance, NetCOBOL will compile the 5 million lines of remedied code in about 15 minutes.  These Linux-based compilers are really fast.

Our OpenVMS application makes use of multiple System Services. How do you support that?

Sector7 has an extensive library of these services running on Linux to perform the same functions as on OpenVMS.  our language conversion tools will adapt the arguments in the procedure API to work with this library.  For instance, VX/COBOL or VX/FORTRAN etc will transform the argument passed BY DESCRIPTOR to a method that will work on Linux.

When the code is compiled on Linux, the compiled objects are linked with the Sector7 library of system services and the program executes on Linux just as it does on OpenVMS, making full use of the various system services.

The critical point here is that there is no need to touch the original source code, the Sector7 tools do all the work.

What is VX/COBOL and how does it help businesses?

VX/COBOL is a comprehensive solution designed to migrate legacy COBOL applications from mainframe environments to modern, flexible Linux-based systems. It allows businesses to retain their valuable, time-tested business logic without needing to rewrite code from scratch.

This approach helps organizations significantly reduce the high operational costs associated with mainframe hardware and software licensing. By moving to a Linux environment, companies can modernize their IT infrastructure, improve performance, and ensure their critical applications are future-proof. Many businesses, like Sprint T-Mobile, have successfully leveraged similar migration strategies. To discover how we can help you, please contact us.

What are the key features of VX/COBOL?

VX/COBOL includes a powerful suite of tools to ensure a seamless migration and high performance on Linux. The key features are:

  • High-Performance Compiler: Supports various COBOL dialects, which minimizes the need for code changes during recompilation.
  • Mainframe Emulation: A robust runtime environment that emulates essential mainframe services like CICS, IMS, and JCL, allowing applications to run on Linux without modification.
  • Data Migration Utilities: Tools to convert mainframe data formats such as VSAM and sequential files into Linux-compatible formats.
  • Integrated Debugging: A complete set of tools for testing and debugging to ensure the migrated application is functionally identical to its mainframe predecessor.

For more details on how these features can benefit your organization, contact us.

How does the VX/COBOL runtime environment handle mainframe dependencies?

The VX/COBOL runtime environment is specifically designed to bridge the gap between mainframe and Linux systems. It works by emulating the core services and APIs that COBOL applications rely on in a mainframe environment, such as CICS for transaction processing, IMS for database management, and JCL for batch job control.

This emulation layer allows your existing COBOL applications to execute on Linux without requiring any changes to the source code that interacts with these services. It effectively tricks the application into thinking it's still running on the mainframe, ensuring a smooth transition and preserving years of investment in your business logic. Companies like Allianz have found great success with this kind of modernization. If you have questions about your specific dependencies, contact us to discuss them.

What is the typical process for migrating an application using VX/COBOL?

The migration process with VX/COBOL is a structured, multi-phase approach designed to minimize risk and ensure a successful transition. The typical stages are:

  1. Assessment: We start by thoroughly analyzing your existing COBOL application to understand its architecture, dependencies, and complexities.
  2. Planning: A detailed migration plan is created, outlining timelines, resource requirements, and a comprehensive testing strategy.
  3. Execution: This phase involves recompiling the COBOL source code, migrating all necessary data from mainframe formats to Linux-compatible ones, and deploying the application in the new environment.
  4. Testing: Rigorous testing is conducted to verify that the migrated application meets all functional and performance benchmarks, ensuring it behaves exactly as it did on the mainframe.
  5. Deployment: The final step is rolling out the application into production and decommissioning the legacy mainframe system.

To get a personalized plan for your migration, contact us today.

What are the main benefits of migrating from mainframe to Linux with VX/COBOL?

Migrating COBOL applications to a Linux environment with VX/COBOL offers significant strategic advantages for any organization.

  • Major Cost Reduction: The most immediate benefit is the elimination of expensive mainframe hardware maintenance and software licensing fees.
  • Infrastructure Modernization: It allows you to move to a flexible, scalable, and modern platform that easily integrates with cloud and other modern technologies.
  • Improved Performance: You can leverage the power of modern commodity hardware and the efficiency of the Linux operating system for better application performance.
  • Future-Proofing: By moving to a widely supported and actively developed platform, you ensure the long-term viability and maintainability of your critical business applications.

Organizations like Amprion GmbH have realized these benefits. Find out what you can achieve by contacting us.

Does VX/COBOL require rewriting our existing COBOL code?

No, one of the primary advantages of VX/COBOL is that it minimizes the need for code modification. The solution is built around a "recompile and run" philosophy. Its high-performance compiler supports various COBOL dialects, and the runtime environment emulates mainframe services, which means your existing business logic can be preserved.

The goal is to recompile the source code on the Linux platform with minimal to no changes, ensuring that the core functionality of the application remains intact. This dramatically reduces the risk, time, and cost associated with a full rewrite. To see how this applies to your codebase, contact us for an assessment.

How are mainframe data formats like VSAM handled during migration?

VX/COBOL includes a set of specialized data migration tools designed to handle the conversion of mainframe-specific data formats. These utilities can read data from formats like VSAM (Virtual Storage Access Method) and sequential files and convert them into modern, Linux-compatible formats, such as indexed files or relational database tables.

This ensures that all your critical business data is migrated accurately and efficiently, maintaining data integrity throughout the process. The migrated application can then access this data seamlessly in the new Linux environment. This approach has been proven in projects for companies like BNY Mellon. For specific questions about your data, please contact us.

What kind of testing support does VX/COBOL provide?

VX/COBOL provides a comprehensive suite of debugging and testing tools to ensure the functional equivalence of your application after migration. These tools are designed to help developers validate that the application behaves exactly the same on Linux as it did on the mainframe.

The testing phase is critical to the success of any migration project. With VX/COBOL, you can conduct thorough testing to identify and resolve any discrepancies, ensuring that the application meets all functional requirements and performance expectations before going live. This rigorous process is how we ensure success for clients like Amco. To learn more about our testing methodologies, contact us.

In a typical OpenVMS COBOL conversion to NetCOBOL or MF COBOL how many changes are made to the code

In a typical OpenVMS application of approximately 4 million lines of code, VX/COBOL can perform up to 100,000 fully automated transformations to align with ANSI COBOL syntax and semantic requirements.

While the volume of changes is substantial, every modification is handled programmatically—with zero manual intervention required.

‍

Transform Your Legacy Software Today!

Get In Touch
Unlock the potential of your legacy software with our expert migration services.