Interactive COBOL Release Notes 5.33 Nov-2017 The release notes are organized primarily by revision number, from newest to oldest for the 5.2x releases. For information on all of the 5.xx releases, see readic.txt. Within each revision number section, there are up to three subsections: "Bug Fixes", "Changes and New Features", and "Known Problems". ********************************************************** NOTICE: Previous ICOBOL 5 Beta versions should be uninstalled before installing a final ICOBOL 5. ********************************************************** **** Revision 5.33 **** Bug Fixes in 5.33 ----------------- 1. In the COMPUTE statement, the ON SIZE condition was not being processed when it was caused during the evaluation of the arithmetic or date/time/interval expression to the right of the = sign (e.g., by a divide by zero). This bug has been present in the runtime since version 3.40. **** Revision 5.32 **** Bug Fixes in 5.32 ----------------- 1. Opening a sequential file with the pdf option could potentially overwrite internal file handle information of another file leading to a runtime crash or unexplained i/o errors. The problem is more likely to occur in the 64-bit builds, but is also dependent on the exact order of operations. The problem has been present since version 5.00. 2. When selecting certain paper sizes on the PDF tab of a configuration file (.cfi) in ICEDCFW, part of the summary size display could be truncated. The size of the display area was increased to fix this. Changes and New features in 5.32 -------------------------------- 1. The enhanced auditing for IND, REL, and SEQ (or when using ALL) now logs OPENs that fail. **** Revision 5.31 **** Bug Fixes in 5.31 ----------------- 1. The configuration utilities (ICCONFIG and ICEDCFW) was not saving the character map table in a .pti file in the proper format, and so it would appear to be unchanged when it was reloaded and it would not work correctly at run time. **** Revision 5.30 **** Bug Fixes in 5.30 ----------------- 1. The base64 encoding routine used by IC_SEND_MAIL for encoding attachments would generate an encoded line that exceeded the limit of 76 characters when the attachment size MOD 57 was equal to 1 or 2. Some SMTP engines do not handle the long line and delivered an attachment with no content. 2. When SQL SMALLINT and INTEGER data types were used to specify column data types, the runtime system was improperly limiting the range of values that could be used to set the column value to 4 digits and 9 digits respectively. 3. The filename processing routine could return exception 133 (The parameter string is not valid for this object) for filename strings that were all spaces. This was observed for blank attachment names being passed to IC_SEND_MAIL. 4. The AUTH CRAM-MD5 method in IC_SEND_MAIL was sending the response in an incorrect format and it was calculating the response hash incorrectly - resulting in AUTH CRAM-MD5 always failing to authenticate. Changes and New features in 5.30 -------------------------------- 1. Envyr Corporation is no longer an authorized reseller of the U/FOS data management suite that was used by the VX/COBOL dialect to support the INFOS data manager. As a result, the runtime system no longer includes runtime support for this product. A VX/COBOL program that uses these features will receive an exception 230 "The requested feature is not available". The VX/COBOL dialect can still be used with standard INDEXED data files. 2. Since the VX/COBOL dialect can no longer support INFOS data management at runtime, all such statements will now generate a warning at compile time unless -R 6 or earlier is specified. 3. Several new exception codes were added to the runtime system to enhance the error reporting from IC_SEND_MAIL: 2133 - The authorization mechanism is too weak 2134 - The SMTP command failed with a 400 level error 2135 - The SMTP command had a 300 level status 2136 - The SMTP command had a 200 level status 2137 - The SMTP command had an unknown error Previously IC_SEND_MAIL returned exception 511 - Unexpected operating system error. 4. IC_SEND_MAIL was changed to always prefer more secure AUTH methods over less secure methods, whether or not TLS or SSL is being used. The priority is AUTH CRAM-MD5, AUTH LOGIN, and AUTH PLAIN. 5. The compiler was enhanced to support the SQL BIGINT type. It is equivalent to an 8 byte signed COMP-5. Due to limitations of our implementation, the range of values is limited to 16 decimal digits. This feature may not work correctly on runtime versions prior to 5.30. **** Revision 5.26 **** Bug Fixes in 5.26 ----------------- 1. The runtime was incorrectly computing the destination size when processing a STRING statement with the POINTER clause, which could result in overwriting the next item in memory. **** Revision 5.25 **** Bug Fixes in 5.25 ----------------- 1. The compiler was generating bad code for a MOVE of a date-time data-item to multiple TO items. 2. The Language Reference Manual was corrected to add a specification of the storage format for (ISQL) USAGE NUMERIC. 3. The Language Reference Manual had incorrect entries for the default values of DATE, TIME, and TIMESTAMP items under the specification of the INITIALIZE statement. 4. A TIME or TIMESTAMP item with fractional digits could be displayed incorrectly in the screen section or in the debugger. The display could omit the decimal point and/or truncate the number of fraction digits. 5. When specifying a VALUE clause for a date-time item, the compiler could give an Internal Error instead of reporting the incompatible VALUE clause for a literal that was not of the same date-time type. 6. In ICIDE, the property sheet for data and screen items was not displaying the Usage property for ISQL usages. 7. The INITIALIZE statement for date, time, timestamp, and interval data items being initialized to the default value was not being handled by the runtime system and would result in a fatal internal error. 8. The debugger was not properly displaying the value of ISQL NUMERIC data items in the TYPE and DUMP commands. It typically displayed +0 even when the value was not zero. 9. The debugger TYPE command was displaying random values for unitialized storage for DATE, TIME, TIMESTAMP, and INTERVAL data items. 10. The compiler was not correctly enforcing the rules found in "TABLE 25. Legality of Types of MOVE Statements" in the Language Reference Manual, resulting in some cases where bad code was generated or the runtime system did not handle the invalid move. The same was true for the MOVE command in the debugger. This table is now enforced. 11. The compiler was not handling several ambiguous cases involving the reserved word TO when specifying an INTERVAL literal. For example, the following MOVE statement is correct: MOVE INTERVAL "2000" YEAR TO WS-YM-INTVL but it gave an error at WS-YM-INTVL that the beginning or end of an interval range was expected there. The compiler assumed the TO was part of a range specification (YEAR TO MONTH) instead of recognizing that the it was the TO that precedes the destination operands in the MOVE. The compiler now resolves the ambiguity by looking ahead for a valid end of range reserved word and if it does not find one, the interval is assumed to have a single field. Changes and New features in 5.25 -------------------------------- 1. DATE, TIME, TIMESTAMP, and INTERVAL literals are now supported as the source operand in the MOVE command in the debugger. 2. The range of values used by debugger messages in runerr.h has changed. For those who may be using custom translations of the messages, the translation input will need to be adjusted and system.ms will need to be rebuilt. **** Revision 5.24 **** Bug Fixes in 5.24 ----------------- 1. The compiler was not correctly handling MOVE of date-time and interval data items when there were multiple TO arguments. Sometimes this would result in an unexpected error and sometimes it was generating bad code. 2. The Language Reference Manual was corrected with respect to the type resulting rom the difference of two DATE values in an expression - the correct type is a date-time interval not a year-month interval. 3. An OPEN where the filename had lengthy extended open options could cause a stack corruption in the runtime system. At times this would result in an unexpected Illegal Filename error, but it could lead to a runtime system crash. This bug first appeared in 5.20. Changes and New features in 5.24 -------------------------------- 1. Under Windows, ICINFO has been updated to find both 32 and 64 bit Flexus SP2 .dlls when using -G f. **** Revision 5.23 (updated) **** Bug Fixes in 5.23.01 ODBC Driver -------------------------------- 1. Some older ODBC calls were inadvertently optimized out of our build because they were o longer directly referenced. Bug Fixes in 5.23 ------------------ 1. When using client-server i/o where the client was a different bit width than the server (32 -> 64 or 64 -> 32), sequential file opens would fail and cause the surrogate process to terminate. The fix will allow earlier 5.xx clients to work correctly with a 5.23 or later server and a 5.23 or later client will operate with an earlier 5.xx 32-bit server only. Compatibility Matrix: Server -> IC4 5.00-5.22 5.00-5.22 5.23 5.23 32-bit 32-bit 64-bit 32-bit 64-bit Client IC4 32-bit Yes Yes* Err* Yes* Yes* 5.00-5.22 32-bit N/S Yes Err Yes Yes 5.00-5.22 64-bit N/S Err Yes Yes Yes 5.23 32-bit N/S Yes Err Yes Yes 5.23 64-bit N/S Yes Err Yes Yes N/S - not supported Err - will get this error that was fixed *NOTE: ic4 must set ICNETUSESHEARTBEAT=1 to force IC4 to use a protocol revision that is above he IC5 minimum revision. 2. A number of ODBC 2 compatible calls that worked pre 5.xx were returning an error. Some applications connecting as ODBC 3 applications still used the outdated calls and were failing. 3. Fixed a problem where iccreate was not correctly creating version 8 indexed files. Changes and New features in 5.23 -------------------------------- 1. Under Windows, Flexus SP2 has been updated. For more see the readsp2.txt. **** Revision 5.22 **** Bug Fixes in 5.22 ------------------ 1. When using the compiler or compling in ICIDE, the compiler could crash if an undefined identifer was referenced in the argument list of a function. 2. When using the debugger, the runtime could crash due to an incorrect memory allocation in the debugger. Changes and New features in 5.22 -------------------------------- 1. Under Windows, Flexus SP2 and QPR have been updated. For more see the readsp2.txt. **** Revision 5.21 **** Bug Fixes in 5.21 ------------------ 1. Under Linux, the icconfig utility was not properly displaying the system parameters page of the .cfi file such the the number of PDF formats was not displayed and could not be modified. This was broken in 5.20. 2. The IC_SEND_MAIL built-in would return exception 36 "Filename is not valid" when an attachment specification had both a blank mime type argument and a blank filename argument. This was broken in 5.20. Changes and New features in 5.21 -------------------------------- 1. A change was made to some compiler error messages to clarify the potential causes for the error. **** Revision 5.20 **** Bug Fixes in 5.20 ------------------ 1. The IC_DECODE_CSV built-in call could return an exception 137 when the last field in the input record was quoted. 2. Under Windows, Flexus SP2 has been updated. For more see the readsp2.txt. 3. The IC_SEND_MAIL builtin would sometimes continue processing after getting an error response to an authentication request instead of returning the error. This would sometimes lead to additional errors in the mail session that could be considered by some SMTP servers as behavior typical of spam senders. In particular, it could return a "mailbox unavailable" error when the underlying actual error was the authentication error. Changes and New features in 5.20 -------------------------------- 1. A change was made to how the debugger processes numeric literals used in debugger commands when debugging programs that use DECIMAL POINT IS COMMA. 2. When configuring the system configuration (.cfi) file, the system page in icedcfw and icconfig now has a new option labelled "Create ver. 7 files". When this option is checked or set to "Y", the runtime system will create version 7 INDEXED and RELATIVE files by default instead of version 8 files. This allows for easier interchange of files for those who are supporting a mix of ICOBOL 4 (or before) and ICOBOL 5 systems. It is not necessary to update the .cfi file if you want to continue to have version 8 be the default. This change updates the version number of the .cfi file from 8.3 to 8.4 when the .cfi is saved or created and so .cfi files edited with version 5.20 and up cannot be used on systems with versions below 5.20. 3. The Windows character-mode keyboard processing was enhanced to allow special characters to be entered by holding ALT and entering a numeric value on the numeric keypad (NumLk on). This affects ICCONFIG and ICRUN. Note that an appropriate code page must be loaded in order for the characters to be displayed properly by Windows. Also, the terminal definition file (.tdi) in use must define the code as a regular character in the keyboard section and have a mapping in the display section. 4. The special named pipe file used by ICEXEC in Linux was moved from /dev to /var/opt/icobol, and the name was changed from ics.69637302 to icexec.pipe.69637302. 5. The Windows runtime system (ICRUN, ICRUNW) now accepts the -C option (filename case conversion) like the Linux runtime system. The default remains the same - converting to lowercase. 6. A new builtin call, IC_WHOHAS_LOCKS, was added that enables a program to determine the records that are locked in the system. The call requires both the "Terminal Status" and "System Information" privileges; otherwise, it will return exception status 221 - "This operation is not permitted." The builtin call takes a single argument, a group with the following structure: 01 WHOHAS-GROUP. 02 MAX-COUNT PIC 9(4) COMP-5 VALUE 10. *> #table elements (input) 02 CUR-COUNT PIC 9(4) COMP-5 VALUE 0. *> actual count (output) 02 INFO-TBL OCCURS 10 TIMES. *> set occurs count as needed 03 TERM-NUM PIC 9(4) COMP-5. *> terminal holding the lock 03 USERNAME PIC X(16). *> user holding the lock 03 PROGNAME PIC X(30). *> program holding the lock 03 FILENAME PIC X(64). *> file with the locked record 03 LOCK-POS PIC 9(9) COMP-5. *> record position of the lock 03 PID-NUM PIC 9(9) COMP-5. *> PID of locking terminal The OCCURS count can be set as needed. Typically there are only a handlful of locked records active at any given time, so usually only a small number is needed. The OCCURS count that is set must also be specified in the VALUE clause of the MAX-COUNT field. The builtin uses MAX-COUNT to make sure that it does not exceed the storage allocated to the table. If the number of actual locks exceeds the MAX-COUNT limit, an exception 220 - "There are no more entries in the table" is returned and the CUR-COUNT field is set to the number needed. 7. A new builtin call, IC_SEND_KEY, was added that enables a program to send a single key to another terminal. The call requires both the "Terminal Status" and "Watch Other Terminals" privileges; otherwise, it will return exception status 221 - "This operation is not permitted." The call takes two arguments: the first is the terminal number to which the key is being sent and the second is a KEY-STRUC group with values as described under the IC_GET_KEY builtin. The effect of this builtin is similar to the full sequence of (a) watch the terminal with control, (b) enter the keystroke, (c) cancel the watch. 8. We have added a new "extended open" option that can be added to a filename to fine-tune the filename case mode handling. By default the runtime system in Linux and Windows convert filenames to lower case before passing them to the operating system. This behavior can be changed globally with a command line option to the runtime system, but sometimes that handling needs to be changed for just particular files - e.g., to meet the naming requirements of a third part application. This is now possible on a file by file basis with the new option. The new "extended open" string is ",c=l" to convert to lowercase, ",c=u" to convert to upper case, and ",c=n" to not convert the case. This option will over-ride the global option for the filename it is added to. This option must be the first option in the list when multiple options are specified. In general, the option applies in OPEN, DELETE FILE, and where filenames are specified in the built-in calls and the # and ## system calls in CALL PROGRAM. For example, to rename a sequential file named "output-file" to mixed case, one could use: MOVE "output-file" to OLD-NAME. MOVE "OutputFile,c=n" to NEW-NAME. CALL "IC_RENAME" USING OLD-NAME NEW-NAME. End of Release Notes