3.2 NetCOBOL Runtime Environment

Information described here applies to the following products.

NetCOBOL Enterprise Edition V11.0.0 for Windows (32bit)

Table 3.2 Program fix list for the NetCOBOL Runtime Environment
No.	V/L(*)	P number	Content
1	V10.1.0	PG76651	When all of the following conditions are met while executing a COBOL program, a size comparison of national items varying in length (national language edited item, including the intrinsic function) was incorrect. Compile option RCS (UCS2,LE) or RCS (UTF16,LE) is specified. And, there is a size comparison of a National item and a National item or National language character constant. And, at least one side is an item with the ANY LENGTH clause is specified or reference modification. And, the length of the compared targets differs.
2	V10.1.0	PG91976	Under the following conditions, the OPEN statement terminates abnormally. () (EXCEPTION_ACCESS_VIOLATION) : The occurrence frequency depends on the state of the memory. A line sequential file or print file without a FORMAT clause. Using a File Identifier in the ASSIGN Clause. The file is not allocated in the file identifier. The OPEN statement in 1 above is executed.
3	V10.1.0	PG96520	Under the following conditions, the message that should be outputted to a trace information file is outputted to a file that is not a trace information file (a socket is included). A TRACE function is used. The file name of the same trace information is specified from two or more processes.
4	V10.1.0	PG97090	Incorrectly replacing the alternative character specified for argument-2 when there is no national character corresponding to the character converted by the NATIONAL-OF function when the COBOL program is executed under the following conditions. It is a program translated specifying translation option RCS (UTF16,BE)., And, the NATIONAL-OF function is used. And, argumen-2 is specified in the function of 2 above. And, data that is not alphanumeric characters is specified for argument-1 specified for the function of No.2, and the code conversion error (there is no corresponding National character) occurs internally.
5	V10.1.0	PH00632	Under the following conditions, when COBOL application does the error diagnosis by the diagnostic function, "JMW0013I-W" message is output and the dump file is not made. When COBOL application is executed, the application error or execution error at U level (JMP0009I-U,JMP0010I-U,JMP0370I-U) are generated. The diagnostic function is started. There are ten dump files that are the upper limit in the dump file making folder.
6	V10.1.0	PH04053	An error code 13 (detail code 10109 or 11004) may occur with the application communication routine "COBCI_OPEN" under the following conditions: [Environment] Operating on Windows Server 2012, Windows Server 2012 R2 or Windows 8, Windows 8.1. [Condition] Inter communication between simple applications is used. And Subroutine "COBCI_OPEN" is called from multiple processes at the same time.
7	V10.1.0	PH04922	The following message may be displayed while debugging your COBOL application: [Example: Debugging sample program "SALES" of PowerFORM] SALES: SALES.EXE - Entry Point Not Found * The procedure entry point Iser32.CharNextExa could not be located in the dynamic link library api-ms-win-downlevel-user32-l1-1-0.dll [OK] The operating system is Windows 7. Internet Explorer version is 10. The dll importing DLL of MinWin(). : It is dll where file name originates in "api-ms-win".
8	V10.1.0	PG72597	The execution of WRITE AFTER ADVANCING PAGE does not become effective at COBOL program execution time in the following conditions (1). It is coordinated with external file handler in the line sequential file. And, WRITE statement of the AFTER ADVANCING PAGE specification is executed immediately after the execution of OPEN statement corresponding to 1. 1 This phenomenon depends on the specification of cooperating external file handler.
9	V10.1.0	PG77099	Under the following conditions, the execution environment variable @CBR_SSIN_FILE=THREAD does not become effective, and one input file is shared by file input of ACCEPT statement in the process. () It is an application that operates by multi-thread. The execution environment variable @CBR_SSIN_FILE=THREAD is specified. ACCEPT statement is executed, and data is input from the file. : When the execution environment variable @CBR_SSIN_FILE=THREAD is specified, input file of each thread can be opened by file input of ACCEPT statement.
10	V10.1.0	PG79650	Under the following conditions, the call of method fails and outputs the following message. JMP0221I-U ERROR OCCURRED IN '' OF THE METHOD INVOCATION. 'BIND' : The garbled method name is output. The class definition (method) is called from the program definition. Compile option RCS (UCS2,LE) or RCS (UTF16,LE) is specified. When the method name specified for the INVOKE statement is multi bytes character.
11	V10.1.0	PG73346	Under the following conditions, at the execution, Unnecessary zero string is set to four subordinate position digits of the hexadecimal character of eight digits buried under execution time message JMP0320I-I/U. File operation using COBOL file system () is done. Either of the following I/O statements is executed. READ statement WRITE statement REWRITE statement DELETE statement START statement The execution of I/O statement failed. : It does not correspond when BSAM is specified.
12	V10.1.0	PG73242	Under the following conditions, at execution time, the following message is output and COBOL application terminates. "Fatal Application Exit insufficient storage available. MSGNO=65535 ERR=9d" The alias associated with function-name SYSERR is described in DISPLAY statement. The output destination of DISPLAY statement is a standard error output or a file (file specified for @MessOutFile). The environment variable @CBR_SYSERR_EXTEND is not specified. The (1024*n+1) byte of the data specified for the DISPLAY sentence is LOW-VALUE(X"00"). (n=0,1,～)
13	V10.1.0	PG73288	Under the following conditions, the log information of web subroutine is not output to the log file. The Web subroutine is used. Compile option RCS (UCS2,LE) or RCS (UTF16,LE) is specified. The log information output of the Web subroutine is set to the environment variable.
14	V10.1.0	PG64106	Under the following conditions, the mistake is found in the execution result of the table search of SEARCH statement (SEARCH ALL). SEARCH statement (SEARCH ALL) exists. And, Two or more conditions are described in the WHEN specification of the SEARCH statement or, the subscript specified for the key item of the WHEN specification is multi-dimensional. And, The item of either of the following USAGE is described in the subject of condition (key item). And, COMP-5 (The one considered by compiler option ASCOMP5 is included). BINARY-SHORT BINARY-LONG BINARY-DOUBLE When you describe the floating-point item or the floating-point constant in the object of condition (object of comparison item).
15	V10.1.0	PG75429	Under the following conditions, the input file becomes 0 bytes and the message of "0 Records were restored." is output in the execution of the indexed file recovery function. Either of the following indexed file recovery function is executed. Recovery Command of COBOL File Utility File recovery command(cobfrcov) Indexed File Recovery Function Index file recovery function will generate error when the file specified as index recovery file corresponds to either of the following. The file is being accessed by COBOL program, etc. The file is not an index file.
16	V10.1.0	PG77518	Under the following conditions, the COBOL program terminates abnormally(EXCEPTION_ACCESS_VIOLATION) A COM client function is used When the COM client is called again in the same process() after runtime environment closes. : For details 2-1-1. The program is compiled by single thread. 2-1-2. The COBOL application is called from the other language. 2-1-3. When COBOL application is called again after all COBOL applications end in the process. or 2-2-1. The program is compiled by multi thread. 2-2-2. After calling JMPCINT4, when JMPCINT2 is called again and COBOL application is called.
17	V10.1.0	PG82410	Under the following conditions, the SORT statement fails and outputs the following message. JMP0601-I/U SORT OR MERGE STATEMENT ERROR. CODE=208. PowerBSORT is not installed. The folder name that exceeds 113 bytes (1) is specified for environment variable BSORT_TMPDIR or TEMP. The SORT statement (2) is executed. 1: Lengths except "\" of end 2: The phenomenon might not be generated by the size of input file or record.
18	V10.1.0	PG83883	Under the following conditions, the opening of the file fails in the execution of the COBOL file access subroutine. Error Number: FA_EFNAME(114) I-O Status : 90 The COBOL file access subroutine inputs and outputs the index file. As for API function (1), the following are specified. The file name is enclosed with the double quotation mark. and The NULL pointer is specified for the record key list. (2) The API function in 2 is executed. 1: cobfa_open cobfa_openW 2: If the NULL pointer is specified for the record key list to open an indexed file, this function automatically identifies the key list structure, record format, and record length of an existing file, and opens the file.
19	V10.1.0	PG84270	Under the following conditions, the SQL statement fails and outputs the following message. SQLSTATE=S1010 SQLCODE=0 SQLMSG=[Microsoft][ODBC Driver Manager]Function sequence error. It connects to the Database with ODBC by using the remote database access function. The FETCH sentence is executed. The COBOL program compiled by the COBOL97 V40L20 or before version compiler is executed. *: The occurrence frequency depends on the state of the memory.
20	V10.1.0	PG84545	Under the following conditions, COBOL File Utility outputs the following message and recovery fails. System error occurred. code = 0x44 cobfrcov command is used. The path name including the comma (,) is specified for the unrecoverable-data-filename.
21	V10.1.0	PG87520	Under the following conditions, The move result by internal Bool item is incorrect. Note: The move result is different according to the state of the area allocated just behind the sending data item. [Condition 1] Move from the internal Boolean item to the internal Boolean item. Data starting location () of the sending data item is different from data starting location of the receiving data item. [a] + [b] > 32, or [c] + [d] > 32 a: Data starting location () of the sending data item b: The length of sending data item or the length of receiving data item, whichever is smaller. c: Data starting location () of the receiving data item d: The length of receiving data item The receiving data item is subordinate to the group item. Data starting location of the receiving data item is not byte boundary of the group item in 4. "Bit length of sending data item" < " Bit length from bit data starting location on the receiving side to the first byte boundary " The bit data of the sending data item steps over byte boundary, or there is byte boundary between from starting locations of the sending data item to "Bit length from bit data starting location on the receiving side to the first byte boundary" in 6. : relative bit position in byte Example of Condition 1 DATA DIVISION. WORKING-STORAGE SECTION. 01 DATA1. 02 DATA1-1 PIC 1(5) BIT. 02 DATA1-2 PIC 1(4) BIT. 02 DATA1-3 PIC 1(7) BIT. 01 DATA2. 02 DATA2-1 PIC 1(1) BIT. 02 DATA2-2 PIC 1(32) BIT. 01 ANS-DATA PIC 1(32) BIT VALUE B"1111". PROCEDURE DIVISION. MOVE X"FFFF" TO DATA1. MOVE DATA1-2 TO DATA2-2. IF DATA2-2 = ANS-DATA THEN DISPLAY "OK" ELSE DISPLAY "NG" > B"11111110-00000000" END-IF. [Condition 2] Move from the internal Boolean item to the internal Boolean item. The sending data item or the receiving data item is referred by the subscript. "The length of receiving data item" > 1 It is either the following. "The length of sending data item" > 1 The receiving data item is referred by the subscript. "The length of receiving data item" > 25 There is not the data starting location of the receiving data item on byte boundary. "Bit length of sending data item" < " Bit length from bit data starting location on the receiving side to the first byte boundary " The bit data of the sending data item steps over byte boundary, or there is byte boundary between from starting locations of the sending data item to "Bit length from bit data starting location on the receiving side to the first byte boundary" in 6. Example of Condition 2 DATA DIVISION. WORKING-STORAGE SECTION. 01 DATA1. 02 DATA1-1 PIC 1(5) BIT. 02 DATA1-2 PIC 1(4) BIT. 02 DATA1-3 PIC 1(7) BIT. 01 DATA2. 02 DATA2-1 PIC 1(10) BIT OCCURS 5 TIMES. 01 ANS-DATA PIC 1(10) BIT VALUE B"1111". 01 CNT PIC 9 VALUE 2. PROCEDURE DIVISION. MOVE X"FFFF" TO DATA1. MOVE DATA1-2 TO DATA2-1(CNT). IF DATA2-1(CNT) = ANS-DATA THEN DISPLAY "OK" ELSE DISPLAY "NG" > B"11111110-00000000" END-IF.

*: V/L is a scope where the bug exists.