EOL.Wiki EOL.Wiki
← ← Back to all products

Visual COBOL

Active
Applications Latest Version: 10.0 Latest Release: N/A

Visual COBOL by Micro Focus enables COBOL application development in modern IDEs and platforms.

Versions

12

Latest Version

10.0

Active Support

3

EOL

9

Lifecycle Timeline

Today
10.0
10.0
9.0
9.0
8.0
8.0
7.0
7.0
6.0
6.0
5.0
5.0
4.0
4.0
3.0
3.0
2.3
2.3
2.2
2.2
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
10.0Jul 19, 2024YesJul 31, 202810.0No
Active
9.0Jun 29, 2023YesJul 31, 20279.0No
Active
8.0Jul 13, 2022YesJul 31, 20268.0No
Active
7.0Sep 14, 2021NoSep 30, 20257.0No
EOL
6.0Jun 18, 2020NoJun 30, 20246.0No
EOL
5.0Jun 21, 2019NoJun 30, 20235.0No
EOL
4.0Jun 14, 2018NoJun 30, 20224.0No
EOL
3.0Jul 7, 2017NoJul 31, 20213.0No
EOL
2.3Oct 3, 2016NoSep 30, 20192.3No
EOL
2.2Nov 19, 2014NoJul 31, 20182.2No
EOL
2.1Apr 5, 2013NoMay 31, 20172.1No
EOL
2.0Apr 27, 2012NoDec 31, 20142.0No
EOL

Frequently Asked Questions

Which versions of Visual COBOL have reached end of life?
The following Visual COBOL versions have reached end of life and no longer receive security updates: 7.0, 6.0, 5.0, 4.0, 3.0, 2.3, 2.2, 2.1 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Visual COBOL 7.0?
Visual COBOL 7.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Visual COBOL?
The latest version of Visual COBOL is 10.0, released in the 10.0 release cycle.
How many versions of Visual COBOL are currently supported?
Visual COBOL currently has 3 actively supported version(s): 10.0, 9.0, 8.0.
When does Visual COBOL 10.0 reach end of life?
Visual COBOL 10.0 is scheduled to reach end of life on Jul 31, 2028.
What should I do when Visual COBOL reaches end of life?
When a Visual COBOL version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.