Differences between Interactive COBOL 5.xx 03-May-2016 and Interactive COBOL 4.xx NOTE: Envyr offers consulting services to assist with the upgrade to ICOBOL 5, if needed. (If you are coming from ICOBOL 2 you should review the fromicobol2 file.) (If you are coming from ICOBOL 3 you should review the fromicobol3 file.) 1. ICOBOL 5 supports new ISAM version 8 files. Version 8 files can contain up to 4 giga-records versus version 7 files, which are limited to 4 giga-bytes in size. Version 8 is now the default for newly created ISAM files. However, as of 5.20 there is a configuration option on the system page to create version 7 files by default in the runtime system. Version 7 files are still fully supported. ICREORG can be used to convert files to/from previous versions. In addition, ICREVUP can be used to convert version 5 and 6 files automatically to version 7 or 8. Please see the documentation for icrevup. 2. There is NO runtime support for version 5 or 6 ISAM files. These files must be converted to version 7 or 8 files using ICREORG or ICREVUP before they can be used by ICOBOL 5. 3. There is a new 64-bit release of the ICOBOL 5 product for both Windows and Linux. The 64-bit release does NOT provide all the functionality of the 32-bit release for programs using SP2 and FormPrint. See the appropriate readme for more information. 4. Under Windows, the services (icexec, icnetd, icpermit) will now place their log files in the c:\programdata\icobol folder instead of the windows folder. In addition any surrogates started from the client/server service (icnetd) will also place their logfiles in the c:\programdata\icobol folder if logging is requested. 5. The logon.cx and sp2logon.cx files have been moved from the main installation folder to the examples\programs subfolder. Under Windows, ICCODEPATH is now set to include the examples\programs subdirectory by default. 6. The convention for finding .tdi, .pti, and .pdf form files has changed. They are no longer stored in subfolders of the installation folder. They are now found by using the ICCONFIGDIR environment variable, or by searching the current directory. Note that the default .pti and .tdi definitions are built into the system, so this mechanism is only needed for user-customized definitions. 7. The tcs subdirectory has been renamed icnet and ALL surrogate executables are released in that directory. (icios, iclogs, icrunrs, icsqls) 8. The icrevw utility on Windows and the icdump utility (Windows and Linux) are no longer a part of the installed system. 9. The facilities to access ICOBOL ICISAM files from other programming languages (called the User Library or icapi) and the ability to integrate custom calls into the runtime (called the link kit) are no longer part of the standard release, but they are still available. Please contact Sales for assistance if either of these are needed. 10. On 64-bit systems, certain 32-bit components are also installed. These include the development tools, which are only available as 32-bit components, and the following components for which we install both the 32-bit and 64-bit versions: the runtime system, the ODBC driver, and the icrunrs and icsqls surrogates started by icnetd. On a 64-bit system, 32-bit components are installed in an x86 subfolder. 11. A COBOL library file can only be used for program files (.cx). ICDATAPATH can no longer specify a COBOL library file. 12. Certain features that were licensed options or that required a separate license are now bundled into ICOBOL 5, such as WATCH, PDF, ICSQL, and WRITE on the ODBC driver. End of Differences from ICOBOL 4