Copyright (C) 2008-2023 COBOL-IT.
There are two versions of COBOL-IT in active release.
| Version | Description |
|---|---|
| 4.11 | This is the current COBOL-IT release. All new features will be based on this release. |
| 3.21 | This is the maintained COBOL-IT release. Only critical issues will be fixed in this release. |
Older supported releases:
| Version | Description |
|---|---|
| 4.2 | This is the previous release on the current branch. The latest hotfix is 4.2.6. |
| 3.11 | This is the previous release on the maintained branch. The latest hotfix is 3.11.1. |
The current Developer Studio release:
| Version | Description |
|---|---|
| 2.2 | Updated to JDK 11 and Eclipse 2022-03. |
Version 4 is the current version of COBOL-IT. For information about this release, see the COBOL-IT 4.11 Release Notes.
Version 3 is the "maintained" version of COBOL-IT. After version 3.21, version 3 will only receive fixes for critical issues. All version 3 users should migrate to version 4 as soon as feasible.
This major release contains new features and corrects a number of issues.
| Feature | Description |
|---|---|
| Embedded SQL | The existing SQL separate product CitSQL has been replaced by a new SQL component as an integral part of the standard COBOL-IT distribution. This addition aims to ensure seamless compatibility with the latest platforms and databases while bringing forth several enhancements over the current implementation. Existing SQL functionality CitSQL is now End of Life. |
| Visual Studio 2022 | COBOL-IT now supports Visual Studio 2022. |
| Windows Installation | The Windows installers have been upgraded. Previously, there was a single executable installer for 32-bit and 64-bit that contained separate installers for each Visual Studio version. Beginning with this release, there are separate MSI installers for each combination of version number, 32 or 64-bit, and supported Visual Studio version. The installation programs have been renamed to make it easy to install the desired version: cobol-it-3.21-32-x86-vc2015-windows-enterprise-328540-setup.msicobol-it-3.21-32-x86-vc2017-windows-enterprise-328540-setup.msicobol-it-3.21-32-x86-vc2019-windows-enterprise-328540-setup.msicobol-it-3.21-32-x86-vc2022-windows-enterprise-328540-setup.msicobol-it-3.21-64-x64-vc2015-windows-enterprise-328540-setup.msicobol-it-3.21-64-x64-vc2017-windows-enterprise-328540-setup.msicobol-it-3.21-64-x64-vc2019-windows-enterprise-328540-setup.msicobol-it-3.21-64-x64-vc2022-windows-enterprise-328540-setup.msi |
This release corrects the following issues.
| Issue | Description |
|---|---|
| 382071 | Allow the COB_EXTFH environment variable and other environment variables exist but be set to an empty value. If empty, they will be treated as if they did not exist and the defaults will be used. This fixes an issue where the value of the environment variable would be set to an empty or blank string and generate an error that the "" library could not be found. |
| 526090 | On Windows, link EXTSM (the SORT access method) into libcobit_dll.dll. This makes it possible to CALL "EXTSM" using opcode, fcd in a COBOL program, providing direct acess to SORT. Note that version 4 already has this functionality, as does version 3 on UNIX. |
| 306127 | Corrected a problem where, when a COBOL source file contains two COBOL programs and one calls the other, and when the source file is compiled with the -fnull-param and -fstatic-call options, the generated C program has a syntax error on Linux. |
| 313036 | The COBOL-IT compiler now properly emits the initialization of Numeric Display fields, when the parent group has been initialized using binary zeros (LOW-VALUES). For most of the numeric types, a field of binary zeros is indeed a zero, and when optimization is enabled during the compilation of the source module, the compiler will skip the initialization of field with a VALUE of 0 because the group was initialized to binary zeros already. However, this is not the case for Numeric Display fields, as a zero is the character 0. |
| 318054 | Issue concerning out of range OCCURS DEPENDING ON has been resolved. |
| 375044 | Corrected a problem where a VBISAM indexed file with duplicate prime keys, and the last two record in the file's prime key are duplicate, when the current record position is the last record, a READ NEXT will not detect the EOF condition, but will instead return the last record again. |
| 384034 | Fixed the file creation date in header of variable length indexed file. |
| 105132 | Fixed issue with 78 level data item if incorrectly given a typedef type. |
| 170046 | The Add/Remove Programs or Programs and Features Windows applications now shows all simultaneously installed versions of COBOL-IT, instead of just the last installation. COBOL-IT can be uninstalled from within this window and the specific installation to be removed can be chosen. Automated removal is also possible using WMIC or other Windows tooling. As a consequence, an UNINSTALL.EXE is no longer created in the installation directory. |
| 173052 | The COBOL-IT Start Menu folders have been reorganized for clarity and to reduce clutter. Right-clicking on a start menu entry offers the usual options and the Uninstall option. |
| 202074 | If multiple versions of Visual Studio or the Microsoft Visual C tools are installed, the setenv_cobolit.bat script, referenced by the desktop icon, would choose the most recent version but always the same as or higher than the version of COBOL-IT that was being installed. The script will now set up the proper version of Visual Studio or the Visual C tools, and only choose the next-highest version if the version that matches the COBOL-IT installation is missing. |
| 204124 | Fixed issue in 3.x source that was assigning sysout file to the cob_file_error during a display. A subsequent check in the code would cause the program to terminate because the cob_file_error was not specified in a select statement. The solution was to guard against setting the cob_file_error in this case. |
| 204195 | The COBOL-IT compiler no longer crashes when compiling a COBOL program with an END PROGRAM clause without a program name. |
| 259006 | Updated libexpat version 2.1.0 to 2.4.9 for security fixes. |
| 363224 | The filename-mapping flag was being overridden and the external-mapping flag was not being passed appropriately when files were marked external. Both of these were fixed and now the behavior matches what we see in the 4.x code which we decided was behaving appropriately. |
| 384009 | The ISAM file header now includes the creation date when creating a variable length record file. |
| 204007 | An intermittent problem in the v3 64-bit cobc compiler that caused a failure when compiling a program with a REPORT section has been corrected. |
| 374018 | Issue preventing the successful processing of a SORT using file when using an external sort module was corrected. The previous error would have resulted in a null fill output/giving file from the sort. |
Issues corrected in version 3.11:
| Issue | Description |
|---|---|
| 203142 | CITSORT will now properly sort a line sequential file with empty lines into a binary sequential file. |
| 207015 | A problem with converting VMS data into a numeric edited field was fixed if the undocumented displayalphanumeric-vms:yes option is set. |
| 231017 | COBOL-IT now correctly computes the scale when an integer literal is added to PIC S9(11)v9(7) COMP field. |
| 259114 | The 64-bit COBOL-IT Windows installations now contain a 64-bit Report Writer. Previously, they contained a 32-bit Report Writer. |
| 244111 | Fix for external SORT statement input procedure. If an external sort routine is used and the input procedure overrides the file assigned in the giving clause, the program will recognize this modification and adjust the output file accordingly. |
| Issue | Description |
|---|---|
| 113015 | The setenv_cobolit.bat files in the installation directories have been completely rewritten. The script now finds the specified Visual Studio installation in the proper way, rather than using the default installation locations.The previous scripts contained a PAUSE that prevented Developer Studio from using the script. A PAUSE is no longer required because the new batch files leave the console window open, and return an errorlevel on failure, along with displaying the cause of the error. |
Updated to JDK 11 and Eclipse 2022-03.