Table 3.1 Program fix list for the NetCOBOL Development EnvironmentNo. | V/L(*) | P number | Content |
|---|
1 | V10.1.0 | PG63211 | The compiler terminates abruptly during compilation. [Condition] If a level 02 or above item that is subordinate to the detail report group is specified for the GENERATE statement. Notes: As per the specification, it is the rule that data name to be specified to GENERATE statement should be "Detail report group" (Language reference 6.4.21 GENERATE statement). The "Detail report group" is the report group where the TYPE clause is specified with DETAIL or DE specified to it, this TYPE clause can only be written in 01 level (Language Reference 5.7 Report group description entry Syntax Rules 1 and 5.7.8 TYPE clause) Therefore GENERATE statement specified with data name with level 02 or above as shown in condition has violated the specification, in right manner it should be compilation error. |
2 | 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. Compiler option RCS(UCS2,LE) or RCS(UTF16,LE) is specified. And, there is a size comparison of National item and 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.
|
3 | V10.1.0 | PG85966 | Under the following conditions, a wrong debugging information file is created, and the COBOL program cannot be debugged. The compilation option TEST is valid. The text-name literal is specified for the COPY statement. The library(*1) taken by the COPY statement in 2 contains the COPY statement for which text name is specified. The compiler terminates abnormally.(*2)
*1: When the nested library, the library is either of library to the last hierarchy. *2: COBOL compiler returns return codes other than 0-3 without outputting the compiler message. |
4 | V10.1.0 | PG86728 | Under the following conditions, the compiler outputs an unjustified compile message. The interface for method 'mmmmm' must conform to that of the overridden method. Method 'mmmmm' is ignored. The OVERRIDE clause is specified in the Method definition. The method in 1) and the method of the same name are in the parent class. When the USING parameter specified for each method meets the following requirements. The parameter of the other method is a group item. And the parameter of the other side method is group item or an alphanumeric item. The size of the parameter is the same.
|
5 | V10.1.0 | PG88107 | Under the following conditions, COBOL compiler terminates abnormally and outputs the following message. JMN0102I-U The compilation process cannot be continued. If other diagnostic messages have been generated, correct those errors and try the compilation again. (substep-name=JMN300, module-name=SC30MKTT, detailcode=3209, line-number=nnn) When there is either of the following statements: |
6 | V10.1.0 | PG88615 | Under the following conditions, the compiler outputs an unjustified compile message (JMN1477I-I). The SPECIAL-NAMES paragraph is declared. The coding mistake of severity code S is found in special-names paragraph.
Note: Even if it satisfies all of the conditions, this event might not occur according to the state of the memory. |
7 | V10.1.0 | PG88616 | When [condition 1] or [condition 2] shown below occurs during the compilation of a COBOL program, there are times when the COBOL compiler outputs a wrong message such as the following. JMN1019I-W line-no marked area should be '-', '*', '/', 'D' or space. Will be taken as space. JMN1123I-S line-no not allowed word 'nnn' appeared.Will be disabled till next recognizable clause, paragraph, section or division. JMN1255I-S line-no 01 without specifying the item level 02 - 49 level item is specified. Will be taken as 01 level. JMN1356I-W line-no header part incorrect word 'nnn' is specified. Will be disabled till next paragraph or division. line-no: line number nnn: Number
The above messages are examples and not a comprehensive list of all the possible messages. [condition 1] The COBOL program that includes the embedded SQL statement is being pre-compiled using the precob command of the Oracle Pro*COBOL., And, the COBOL program is being created from the Pro*COBOL program of 1 above using the INSDBINF command,. And, the COBOL program created in 2 above is compiled by specifying compile option "NUMBER".
Or [condition 2] The COBOL program (including the embedded SQL) is being pre-compiled after option "-g" is specified in the sqlpcob command of Symfoware. And, the COBOL program created in 1 above is compiled by specifying compile option "NUMBER".
|
8 | V10.1.0 | PG89665 | When all of the following conditions are met, error messages are output during the compilation and the COBOL program cannot be compiled. JMN2206I-S KEY IS clause's data name 'xxxxx' cannot be an address variable item. The KEY IS specification of the OCCURS clause is being described. And, the data name specified in 1 above is at a variable position in the records.
|
9 | V10.1.0 | PG81806 | When all of the following conditions are met during compilation of the COBOL program, the COBOL compiler terminates abnormally. Any of the following statements is described. And, the statement in 1 above is being described in the conditional statement. And, the hierarchy (*1) of the conditional statement in 2 above is more than 180. *1: In the following code, hierarchy 1 is the EVALUATE statement and hierarchy 2 is the COMPUTE statement. EVALUATE
WHEN
COMPUTE
ON SIZE ERROR
CALL
END-COMPUTE
END-EVALUATE
However, depending on the amount of computer memory, there may be no abnormal termination. |
10 | V10.1.0 | PG97391 | During the execution of the COBOL program the value is not correctly set to the item written to RETURNING phrase of the CALL statement. [Condition] Compile option OPTIMIZE(*)is effective. And, internal program exist in the program. And, identifier is specified in the CALL statement. And, in the CALL statement of RETURNING phrase of (3) following item are specified. Items of 1,2,4,8 bytes Index data item Pointer data item Object reference
And, in the CALL statement of (3) ON EXCEPTION/NOT ON EXCEPTION or ON OVERFLOW is specified. And, when the CALL sentence of (3) calls the external program at run time.
*: NOOPTIMIZE is default option. |
11 | V10.1.0 | PG98620 | Under the following conditions when compiling, the COBOL program terminates abnormally without giving an error message. Compiler option OPTIMIZE is specified (*1). And, the CALL statement in which the called program is specified in the identifier is described. And, the USING phrase in the CALL statement of 2. And, the RETURNING phrase in the CALL statement of 2. And, pointer data item is set or referred to. And, an internal program exists. And, when the USING phrase is omitted in the header of the Procedure Division of 6.
*1: The compiler option default value differs based on the OS on which product is installed. |
12 | V10.1.0 | PG98742 | When a COBOL program is executed, it might not behave correctly. Or while compiling the COBOL program, the compiler might terminate abnormally. The following conditions help identify when that situation might occur. [Condition 1] When a data item is declared either in WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION (*1) or CONSTANT SECTION. When a group item of level-number 01 that has subordinate data item specifying the TYPE clause is defined. And, in the group item of 1 REDEFINES clause is being specified. And, when the length of the data item in 1 is smaller than the length of the data item being redefined in 2.
Or [Condition 2] When data item is declared in the FILE SECTION. When record description which includes the TYPE clause is being defined. And, the file description entry that contains the record description entry of 4 contains two or more data description entries of level-number 01.(*2) And, when the length of record description items in 4 is smaller than the length of record description items in 5. *1: LOCAL-STORAGE SECTION functionality is supported in x64 V10.4 and later. *2: The record description item's area is redefined implicitly when more than 2 record description items are mentioned in the same file description items in the file section.
Example 1) When a data item is declared either in WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION or CONSTANT SECTION. 01 D1 PIC X(20). *> SIZE 20 BYTE D1 is larger than D2.
01 D2 REDEFINES D1. *> SIZE 8 BYTE
02 D21 TYPE T1. *> SIZE 8 BYTE
01 T1 TYPEDEF.
02 TD1 PIC X(8). *> SIZE 8 BYTEExample 2) When data items are declared in the FILE SECTION. FD FILE1.
01 R1 PIC X(20). *> SIZE 20 BYTE R1 is larger than R2
01 R2 TYPE T2. *> SIZE 8 BYTE It is implicitly redefine
*> and allocated in the same region as R1 and R2
01 T2 TYPEDEF.
02 TD2 PIC X(8). *> SIZE 8 BYTE |
13 | V10.1.0 | PG99190 | When compiling a program which meets the following conditions, the compiler terminates abruptly after generating the following message (*1). (*1) JMN0124I-U This source file has an invalid character. The compilation is terminated. (substep-name=JMNALO, line-number=0.) Compilation option RCS(UTF16), ENCODE(UTF8,UTF16) or ENCODE(UTF8,UTF32) is specified. And, compilation option CHECK(PRM),CHECK(ALL) or SAI is specified. And, the encoding of the COBOL program is Shift_JIS. And, a nonnumeric literal(except National character constant)is specified in the BY CONTENT phrase of CALL Statement or INVOKE Statement. And, a national character is included in the nonnumeric literal of 4.
|
14 | V10.1.0 | PH00165 | Under the following conditions, when dependency analysis is performed in NetCOBOL Studio, NetCOBOL Studio might terminate abnormally. [Condition 1] A COBOL source file where compile error occurs is created. And, when a file is dragged and dropped in or copy into another project, the length of the file pass characters in destination is more than 260.
Or, [Condition 2] The variable format is specified for the reference format of a COBOL source file. And, when dependency analysis is performed from the context menu in the "Dependency" view. Or, when a project is imported. And, the COBOL source is in the following condition. 3-1. Each of the following COPY statements is described. 3-1-1. The text name is specified in the COPY statement. 3-1-2. And, there is no definition for the COB_LIBSUFFIX environment variable. Or, the COB_LIBSUFFIX environment variable is "None". 3-1-3. And, the characters length of the text name is more than 256. Or, 3-2-1. The text name is specified in the COPY statement. 3-2-2. And, the COB_LIBSUFFIX environment variable is specified with any other "None". 3-2-3. And, the sum of the characters length of the text name and the value length of the COB_LIBSUFFIX environment variable are more than 259. Or, 3-3-1. The text name is specified in the COPY statement. 3-3-2. And, the library name is not specified with IN/OF in the COPY statement. 3-3-3. And, the LIB compile option is specified. 3-3-4. And, the characters length of the text name is more than 255. Or, 3-4-1. The text name is specified in the COPY statement. 3-4-2. And, the characters length of the text name is more than 260. Or, 3-5-1. The COPY statement with the XMDLIB/XFDLIB phrase is specified in the library name. 3-5-2. And, the characters length of the text name is more than 256. Or, 3-6-1. The text name is specified in the COPY statement. 3-6-2. And, the library name is specified with IN/OF in the COPY statement. 3-6-3. And, the COB_LIBSUFFIX environment variable is specified with any other "None". 3-6-4. And, the characters length of the text name is more than 260. Or, 3-7-1. The length of the class name of the COBOL class repository is more than 256. 3-7-2. Or, the length of the class name of the class definition of the COBOL class repository is more than 256.
|
15 | V10.1.0 | PH01579 | Under the following conditions, the COBOL compiler terminates normally without generating an error message. A paragraph name or section name is specified in the USING phrase of CALL statement.
|
16 | V10.1.0 | PH01938 | Under the following environment and conditions, a part of letters in a COBOL source file are converted to "?" when it is sent to a remote server from NetCOBOL Studio. [Environment] Remote server OS is Windows(x64). [Condition] MS932 is specified as the encoding form of the text file in COBOL project created in NetCOBOL Studio. And, a server name that Shift_JIS is specified as the encoding form of the source file is set in "Remote Development" preferences dialog box. And, the server name of 2 is used for remote development of the COBOL project of 1. And, the COBOL source file includes any of the following letters. 0x8160(Shift_JIS) (WAVE DASH) 0x8161(Shift_JIS) (DOUBLE VERTICAL LINE) 0x817C(Shift_JIS) (MINUS SIGN) 0x8191(Shift_JIS) (CENT SIGN) 0x8192(Shift_JIS) (POUND SIGN) 0x81CA(Shift_JIS) (NOT SIGN) 0xFA55(Shift_JIS) (FULLWIDTH BROKEN BAR)
And, the COBOL source file is sent to the server using any of the following functions for remote development in NetCOBOL Studio. Create a Makefile Build Rebuild
|
17 | V10.1.0 | PH02032 | Under the following conditions, while compiling the COBOL program, at times regarding the continuation line of the literal the compiler generates the following message. JMN1022I-S The ending quotation mark of the literal is missing. The characters at the end of Area B are assumed to be a literal. JMN1021I-S The continuation line of the literal must have a hyphen in the indicator area and must start with a quotation mark. The continuation of the literal is assumed. REPLACE statement is used. When there is the following description in of the range(*1) where replacement is done by REPLACE statement of 1). a) COPY statement is used. b) The character(*2) ahead of the COPY statement of (a) is not one of the following characters. "(", ")", ";" and "." c) Continuation of lines of the nonnumeric literal(*3) is described after the COPY statement of (a). d) Continuation of lines of the COBOL words(*4) is not described between the COPY statement of (a) and the continuation lines of the nonnumeric literal of (c).
*1: Until the next REPLACE statement appears or the end of the compilation unit *2: The space and the comment line are excluded *3: Nonnumeric literal, hexadecimal nonnumeric literal, national nonnumeric literal or boolean literal *4: PICTURE character-string or COBOL words excluding national language user-defined word |
18 | V10.1.0 | PH02168 | Under the following conditions, while compiling the COBOL program the following error message is generated. JMN1479I-S The concatenation expression is too long. A literal is created using the first parts of the expression so that it does not exceed the maximum length. JMN0124I-U This source file has an invalid character. (substep-name=JMNxxx, line-number=nn.) The compilation is terminated. Encoding of COBOL source is UTF-8. And, Concatenation expression is described for National character constants (*1) When the number of characters concatenated at 2 are 54-80 characters.
(*1) Including named constants and symbolic constant. |
19 | V10.1.0 | PH02265 | Under the following conditions, a compilation error may not be generated. Concatenation expression is described in the external name of program, class or method. And, one of the following is described at the beginning of the concatenation expression. And, when one of the following is described in the concatenation expression.
|
20 | V10.1.0 | PH02733 | Under the following conditions, the last character of the class name or interface name of a COBOL source code that is generated by the java2cob command might become a hyphen, and the following error message be generated. JMN1123I-S An invalid word '-' was found. The invalid word and any following code is ignored until the next valid paragraph, section or division. [Condition] The 28th character of a Java class name (*) that generates an adapter class is a period or a dollar sign. The 28th character of a Java interface name (*) that generates an adapter class is a period or a dollar sign.
* : The package name is excluded. |
21 | V10.1.0 | PH02992 | Under the following conditions, a part of letters of path that is set as an operand of a compile option (like LIB compiler option) are converted to "?", and a build error occurs because the correct file path is not referred. For example, in case of the path that is set as an operand of LIB compile option, the following error occurs because the COBOL library file is not read. JMN1057I-S An I/O error occurred while processing the COBOL library text. Processing of the library text was terminated. [Condition] Japanese double-byte letters are used path that is set as an operand of a compile option. And, any of the following letters are used in the path. 0x8160(Shift_JIS) (WAVE DASH) 0x8161(Shift_JIS) (DOUBLE VERTICAL LINE) 0x817C(Shift_JIS) (MINUS SIGN) 0x8191(Shift_JIS) (CENT SIGN) 0x8192(Shift_JIS) (POUND SIGN) 0x81CA(Shift_JIS) (NOT SIGN) 0xFA55(Shift_JIS) (FULLWIDTH BROKEN BAR)
|
22 | V10.1.0 | PH03188 | Under the following conditions, the characters of file path in a COBOL project are corrupted, and the following phenomena [Phenomenon 1] or [Phenomenon 2] might occur. [Phenomenon 1] When the letters of source file path set in source folder are corrupted, the source files are skipped to build. [Phenomenon 2] Build error occurs because the compiler or the linker is not able to find the reference files. For example, when the literal string set to LIB compiler options are corrupted, library file are not read correctly and the following messages is output. JMN1057I-S An I/O error occurred while processing the COBOL library text. Processing of the library text was terminated. [Condition] Other than ASCII code are used in letters that are in the file path or folder path specified for setting COBOL project. And, when the COBOL project of 1 above is imported into a workspace.
|
23 | V10.1.0 | PH04722 | Under the following conditions, it might fail in building a COBOL project with the following message displayed in the "Problem" view in NetCOBOL Studio. Target "cobol_buildtool-clean" does not exist in the project "XXX".
It is used from target "clean build". (XXX means a COBOL project name.) [Condition] The type of dynamic link libraries is selected as TARGET type. And, when the COBOL project 1 is imported into the workspace. And, when the COBOL project name of 2 is changed from [Rename] of the context menu in the [Navigator] view.
|
24 | V10.1.0 | PH05002 | Under the following conditions, COBOL compiler terminates abnormally and outputs the following message. JMN0102I-U The compilation process cannot be continued. If other diagnostic messages have been generated, correct those errors and try the compilation again. (substep-name=JMN645, modulename=SA64RTXT, detailcode=6427, line-number=0) When there are both of the following ALPHABET clause of SPECIAL-NAMES paragraph: |
25 | V10.1.0 | PG80311 | Under the following conditions, when a file is dragged and dropped in the "Dependency" or "Structure" view in NetCOBOL Studio, it might be deleted. [Condition] When a COBOL project is opened in the COBOL perspective in NetCOBOL Studio. And, a file in any of the following virtual folders is dragged in the "Dependency" or "Structure" view. And, the file is dropped in the area of any other than folders of the "Dependency" or "Structure" view.
|
26 | V10.1.0 | PG80826 | Under the following conditions, the monitoring data items might not be used because of waiting status in the remote debug function of NetCOBOL Studio. [Condition] PROGRAM-ID includes lowercase letters. And, in NetCOBOL Studio, ALPHAL and NOALPHAL compile option and specified in the COBOL Project including the COBOL source program of 1 by any of the following combinations. For local build: ALPHAL or not specified For remote build: NOALPHAL For local build: NOALPHAL For remote build: ALPHAL or not specified
And, when the COBOL Project of 2 is debugged. And, a data item defined in the COBOL source program of 1 is added to the "Watch" view.
|
27 | V10.1.0 | PG70346 | Under the following conditions, when the directory is selected clicking "Browse" button by "Project > Remote Development > Server directory" of NetCOBOL Studio, an improper error message "Cannot open file "{0}"because specified path is invalid." might be displayed. The user's access authority refusal is set to the directory of the server used by remote development. The Remote Development page is opened from the property of the project remote to be developed. The server is selected from the combobox of "Server". Click "Browse" button, the directory in 1 is selected and click "OK" button.
|
28 | V10.1.0 | PG70339 | Under the following conditions, Waiting time continues for 20 minutes or more when COBOL source program is opened with NetCOBOL Studio. The following character strings are described in a library name, a data name, a constant character string, or a part of constant character string in COBOL source program as a noncontiguous token. PROGRAM-ID CLASS-ID METHOD-ID
|
29 | V10.1.0 | PG79738 | Under the following conditions, NetCOBOL Studio might be down while being debugged with the message "javaw.exe has terminated abnormally." output in messages dialog box. [Condition] NetCOBOL product development package for Windows is installed. When a COBOL program is debugged. And, the program of 2 includes a CALL statement. And, the subprogram called by the CALL statement of 3 is different file from the program of 3. And, when the subprogram is debugged by using "Step Into" from the line of CALL statement in the program of 4. And, when the operations from 2 to 5 are done repeatedly.
*1: The incidence depends on the memory state. |
30 | V10.1.0 | PG72245 | Under the following conditions, the build fails when a local build is executed while effectively set with NetCOBOL Studio for remote development. COBOL project is created by NetCOBOL Studio. Precompiler link information for the project is set (Property > Build Tools > Precompiler). Server information for the project is set (Property > Remote Development). Precompiler link information for remote development is never set (Project > Remote Development > Makefile Creation > Option setting > Precompiler) The project is built.
|
31 | V10.1.0 | PG71240 | Under the following conditions, INSDBINF command outputs the following message mistakenly. Line number control information and file name control information cannot be correctly output. Check the input file or the command option. Pro*COBOL is used. Key word (*) with which Pro*COBOL develops is described in the input source of Pro*COBOL. "/" or "D" is described in indicator area of the line in 2 and it is assumed comment line.
* : SQL statement, Pseudo-type data, etc. |
32 | V10.1.0 | PG71241 | Under the following conditions, INSDBINF command outputs the following message mistakenly. Line number control information and file name control information cannot be correctly output. Check the input file or the command option. Pro*COBOL is used. The line feed code of the input source file of Pro*COBOL is a LF "EXEC SQL" and other statements in EXEC SQL statement are described separately for two lines or more. Example)
EXEC SQL
INCLUDE INCFILE
END-EXEC
|
33 | V10.1.0 | PG71243 | Under the following conditions, INSDBINF command outputs the following message mistakenly. Include file is not found. Pro*COBOL is used. There is an INCLUDE statement in the program. The specification of the include file is enclosed with the quotation (single quotation or double quotation) and specified.
or Pro*COBOL is used. There is an INCLUDE statement in the program. The include file is specified without the extension path. Example 1)
INCLUDE D:\INCLUDE_DIR\INCF
Example 2)
INCLUDE ..\INCLUDE_DIR\INCFExtension of the include file is specified by the -S option of INSDBINF command.
|
34 | V10.1.0 | PG71244 | Under the following conditions, INSDBINF command outputs the following message mistakenly. Include file is not found. Pro*COBOL is used. There is an INCLUDE statement in the program. INCLUDE and the include file name are described in a separate line, and it changes line just behind character string INCLUDE. Example)
EXEC SQL
INCLUDE(*)
INCFILE
END-EXEC
(*): Line Feed Code
|
35 | V10.1.0 | PG72054 | Under the following conditions, INSDBINF command outputs the following message mistakenly. Line number control information and file name control information cannot be correctly output. Check the input file or the command option. Pro*COBOL is used. EXEX SQL statement in the input source of Pro*COBOL is described separately for two lines or more. EXEC SQL statement in 2 includes the line of 5 columns or 6 columns (*). Example 1 (The line of 5 columns) ----+----1----+----2----+----3----+----4
000090 EXEC SQL
000100 SELECT ENAME FROM EMP
00011(*)
000120 WHERE ESAL > 3000
000130 END-EXEC
(*): Line Feed CodeExample 2 (The line of 6 columns) ----+----1----+----2----+----3----+----4
000090 EXEC SQL
000100 SELECT ENAME FROM EMP
000110(*)
000120 WHERE ESAL > 3000
000130 END-EXEC
(*): Line Feed Code
* : Line Feed Code is not counted. |
36 | V10.1.0 | PG68785 | Junk characters may occur within compiler messages under the following conditions: [Condition] At the runtime code set is Unicode(*1). And, Program which generates compile messages is compiled and, If the word that caused the error is national hexadecimal nonnumeric literal.
(*1) In case of Windows-based products, it is applicable when compile option RCS(UCS2) or RCS(UTF16) is specified. In case of Solaris/Linux, it is applicable when locale is Unicode(LANG=*.UTF-8). |
37 | V10.1.0 | PG67603 | In case of following occurrence condition, invalid compile error is generated during compilation (*1)(*2). [Condition] At the runtime code set is Unicode(*3). And, Line sequential file exist. And, File record has 2 or more level of group items (*4). Or identifier name specified in the FROM of WRITE statement has 2 or more level of group items (*4). And Group items of (3) are composed of only national item or national edited item.
(*1) Following compile message is generated. JMN5159I-S If the runtime code set of national data is Unicode, the line sequential file record cannot have both national and non-national items. (*2) If WRITE statement with FROM specified is written, following compile error message is generated. .NET JMN3514I-S When compile option RCS(UTF8-UCS2) or RCS(SJIS-UCS2) is specified, group item @1@ which contains a national item and other items cannot be specified in a WRITE statement with a line sequential file. Solaris/Linux JMN3516I-S If the runtime code set of national data is Unicode, group item @1@ which contains a national item and other items cannot be specified in a WRITE statement with a line sequential file. Windows JMN3473I-S When compile option RCS(UTF16) is specified, group item @1@ which contains a national item and other items cannot be specified in a WRITE statement with a line sequential file.
(*3) In case of Windows-based products, it is applicable when compile options RCS(UCS2) or RCS(UTF16) is specified. In case of Solaris/Linux, it is applicable when locale is Unicode(LANG=*.UTF-8). (*4) Example of 2 level of group items is shown. E.g.) 01 A.
02 A1.
03 A11 PIC N.
03 A12 PIC N.1 level group items as shown below does not corresponds with the occurrence condition. 01 A.
02 A1 PIC N.
02 A2 PIC N. |
38 | V10.1.0 | PG66674 | The compile message (JMN1073I-S or JMN1104I-S) notifying that there is no program name paragraph at the time of compilation is generated under the following circumstances: [Condition] The external program that specifies 31 bytes or more national program-name or program-name literal are defined, And, The internal program that specifies (1) and till 30 bytes same national program-name or program-name literal is defined.
|
39 | V10.1.0 | PG77383 | Under the following conditions, the execution results are incorrect. The compilation option OPTIMIZE is valid. (*1). There is a statement that sets packed decimal item to numeric edited data item. The number of digits for integer part of packed decimal item and numeric edited data item are the same and neither both of them does not have decimal-part. The numeric edited data item specifies only zero suppression for the edit (Only '9', 'Z', and '*' are used for PICTURE character-string). Before the statement in 2 (*2), there is a statement that sets data item (or intermediate result) to packed decimal item. The relation between number of digits for the data item in 5 (or intermediate result) and number of digits for the packed decimal part in 2 is the following : ---------------------------------------------------------
Data item (or intermediate result) Packed decimal item
---------------------------------------------------------
2 3
4 5
6 7
8 9
10 11
12 13
14 15
16 17
---------------------------------------------------------The data item in 5.(or intermediate result) and the packed decimal item in 2 don't have the decimal-part.
*1 : NOOPTIMIZE is the default. *2 : MOVE statement, COMPUTE statement, and so on. |
40 | V10.1.0 | PG64051 | The compiler terminates abruptly during compilation (*1) under the following conditions: [Condition] In-line method invocation exists. And LENGTH OF special register is specified for argument of in-line method invocation.
(*1) .NET "Problem has occurred, F5FGCBL.exe needs to close." message box is displayed. Windows "Problem has occurred, COBOL32.exe needs to close." message box is displayed. Solaris "Segmentation exception (core dumped)" is generated. Linux "Segmentation error" message is generated.
Notes: Identifier must be SELF, EXCEPTION-OBJECT, NULL, a class name specified in the REPOSITORY paragraph, or a data item defined in the FILE, WORKING STORAGE, or LINKAGE section. (Language reference 11.3.3.2 In-Line Method Invocation) Therefore description shown in occurrence conditions are in violation of the syntax rules, in right manner it should be compilation error. |
41 | V10.1.0 | PG74245 | Under the following conditions, the compilation terminates abnormally. PROCEDURE division has 10,000-line (*) or more. Object specifier is used.
* : 10,000 lines or more are standards. There is a possibility to be generated by 10,000 lines or less according to the writing of the program, too. However, if it is not tens of thousands of lines or more if it is a program of a standard form that does not write two or more sentences in one line, the possibility of terminating abnormally is extremely low. |
42 | V10.1.0 | PG72507 | When the compile option THREAD(SINGLE) is specified, an abnormal execution result might be generated. When compile option THREAD(MULTI) is specified, abnormal termination or an execution abnormal result might also be generated. [Condition] In the COBOL program calculation of fixed point attribute exists where digits(*1) of intermediate results will become 28 digits.
-- NetCOBOL Language Reference Start -- *1: The number of digits of the intermediate result is determined by the number of digits of the variable that is used for the calculation. The digit number for the intermediate result can be requested by the following calculations. Addition Number of digits of the intermediate result=MAX(Number of digits in the integer part of the Summand, Number of digits in the integer part of the Addend) + MAX(Number of digits in the decimal part of the summand, Number of digits in the fractional part of the Addend) +1 Subtraction Number of digits of the intermediate result=MAX(Number of digits in the integer part of the minuend, Number of digits in the integer part of the meiotic) + MAX(Number of digits in the decimal part of the minuend, Number of digits in the decimal part of the meiotic) +1 Multiplication Number of digits of the intermediate result=Number of digits of the multiplicand + Number of digits of the multiplier Division Number of digits of the intermediate result=Number of digits in the integer part of the dividend + MAX(Decimal part reference digits(*2), Number of digits in the decimal part of the dividend - Number of digits in the decimal part of the divisor)
*2: All operands in arithmetic statements and arithmetic expressions (including destination items) are used. Use the maximum number of digits in the decimal part operand as the reference number of digits in the decimal part. However, when using arithmetic statements and expressions, floating-point data items and any operands used as an exponent in an exponent or division divisor and as function arguments should be excluded. When ROUNDED is specified in the destination, increase the number of digits in the decimal part of the destination item and use that result for the destination item. If no operand is used to determine the reference number of digits in the decimal part, 0 is used as the reference number of digits in the decimal part. -- NetCOBOL Language Reference End -- An example of computing the intermediate result where it will become 28 digits is shown below. 18-digit integer and a decimal point below is the addition of decimal with 9 digits 01 DATA11 PIC S9(18).
01 DATA12 PIC S9(18).
01 DATA13 PIC S9(9)V9(9).
:
COMPUTE DATA11 = DATA12 + DATA13
*> Addition of Integer 18 digits and decimal nine-digitIn the above example, during addition there is a possibility that increase in digits could occur, in the intermediate result 28 digits of area is reserved, 19 digits for integer part and 9 digits for decimal part. Multiplication of 10-digit integer and 18-digit integer 01 DATA21 PIC S9(18).
01 DATA22 PIC S9(10).
01 DATA23 PIC S9(18).
:
COMPUTE DATA21 = DATA22 * DATA23
*> Multiplication of 10-digit integer and 18-digit integerIn the above example, during multiplication in the intermediate result 28 digits of area is reserved. 10-digit integer and 10 digit integer and decimal point below is the multiplication of decimal points having 8 digits 01 DATA31 PIC S9(18).
01 DATA32 PIC S9(10).
01 DATA33 PIC S9(10).
01 DATA34 PIC SV9(8).
:
COMPUTE DATA31 = DATA32 * DATA33 * DATA34
*> Multiplication of 10 digit 10 digit and 8 digit In the above example, area reserved for intermediate results during the first multiplication is 20 digits, 28-digit during the second multiplication.
Please see below for more information on the intermediate results. "NetCOBOL Vxx.xx COBOL Language Reference Appendix D Intermediate Results" "NetCOBOL for Windows Vxx.xx Language Reference Appendix D Intermediate Results" "NetCOBOL for Linux Vxx.xx COBOL Language Reference Appendix D Intermediate Results"
|
43 | V10.1.0 | PG78440 | Under the following conditions, the execution results are incorrect. The BINARY(BYTE) or BINARY(WORD, MLBOFF) compiler option is specified, along with The following intrinsic functions: [A] FUNCTION MAX FUNCTION MIN FUNCTION MEAN FUNCTION MEDIAN FUNCTION RANGE
[B] FUNCTION ANNUITY FUNCTION NUMVAL FUNCTION NUMVAL-C FUNCTION RANDOM
The arguments of the function in 2) above are fixed point of 9 digit or less. The number of the arguments in [A] above is 4 or more.
|
44 | V10.1.0 | PG63990 | In the following environment and conditions, at run time, the SEARCH statement execution result is incorrect (* 1). (*1) The result will be any one of either a) or b). However with 0 search will have normal results. a) In spite of satisfying the WHEN condition, procedure specified in WHEN condition is not executed. b) In spite of not satisfying the WHEN condition, procedure specified in WHEN condition gets executed. [Condition] SEARCH statement (SEARCH ALL) exists. And Multiple conditions are specified to WHEN of SEARCH statement, or, A multi-dimensional index is specified in the key item of WHEN phrase. And, To the left-hand side (key item) of the condition, any of the following USAGE items is mentioned. And, If to the right-hand side (the comparison object item) of the conditions, a floating-point item or floating-point constant is mentioned.
|
45 | V10.1.0 | PG67763 | In the following environment and conditions, during the compilation by the COBOL compiler, the compilation processing is aborted. [Condition] In the Procedure division of the source program, CLOSE statement is mentioned immediately after the DISPLAY statement. And, In the DISPLAY statement of (1) UPON is specified, and NO ADVANCING is not specified. And, In the end of DISPLAY statement of (1) period is not given. And, Compile option NUMBER is specified, or CLOSE statement of (1) is included through COPY library. And, Regarding the CLOSE statement of (1) [COPY qualification-value](*1), when it is expressed in hexadecimal of 2 bytes, it becomes a particular value (*2).
(*1) Regarding [COPY qualification-value], please refer to the NetCOBOL User's Guide of each product. For other than NetCOBOL for .NET Please refer to the section of "Source Program Listing". In case of NetCOBOL for .NET Please refer to "NetCOBOL User's Guide for .NET" > "Reference" > "Compiler options/compile options" > "NUMBER". Will be applicable to those which are expressed as "special numbers" "label".
(*2) Corresponding value differs for products. |
46 | V10.1.0 | PG69138 | In case of following environment, occurrence condition, during execution COBOL program terminates abruptly. [Condition] There is a SORT or MERGE statement with the USING or GIVING phrase. And, In USING or GIVING phrase specified at (1), Relative file of sequential access with the RELATIVE KEY clause is specified. And, Relative file of (2) is not an EXTERNAL specified file. And, RELATIVE KEY clause data item of (2) is not a data item defined in the LINKAGE section. And, OPEN statement of the relative file of (2) is not executed before SORT or MERGE statement of (1) is executed.
|
47 | V10.1.0 | PG73470 | Under the following conditions, the message (JMN9333I-W (STD)Number of USING phrase in CALL statement must not exceed 5.) is output at the compilation time. The compilation option FLAGSW(STDM) or FLAGSW(STDI) is valid. There is a USING phrase in CALL statement. The number of parameters specified for USING are 5 or less, and identifier. One or more reference modification or subscript is specified for identifier in 3. The identifier is specified to reference modification or subscript in 4. The total number of identifier in 3 and 5 is 6 or more.
|
48 | V10.1.0 | PG68532 | When debugging an executable file in interactive debugger which was created as per the following occurrence conditions, interactive debugger failed and debugging cannot be started. [Condition] The libraries are included in the COPY statement with REPLACING phrase. And, The last token of the last line of the included library is a nonnumeric literal closed with quotes. And, There is no period or separator immediately after the nonnumeric literal of (2), quote of the nonnumeric literal is at the right end of Area B. And, The compile option TEST is specified.
|
49 | V10.1.0 | PG77217 | Debugging cannot begin because interactive debugger terminates abnormally when the execute form file made on the following conditions is debugged with interactive debugger. Library is included in a program using COPY statement. The included COPY library is only PROCEDURE DIVISION header. The program is compiled specifying the compilation option TEST.
|
50 | V10.1.0 | PG64947 | Under the following conditions, the remote server connection fails. When it log in the client, login ID of client (Windows) contains the character treated as a special character with the shell of a remote server. The NetCOBOL Studio of the client is started, and either is operated as follows. Select the project > Property > Remote Development, and click the Browse button. Select the project > Remote Development > Makefile Creation.
|
51 | V10.1.0 | PG84741 | Under the following conditions, the precompiler link information or the resource compiler options are not saved in the COBOL projects. Open the properties dialog box of the COBOL project by using NetCOBOL Studio, and change the set value on either of the following pages: Target page Build > Compiler Options page Build > COBOL Library name page Build > Linker Options page
The OK button of the properties dialog is not clicked. It changes to either of the following pages: The set values are changed, and the OK button of the properties dialog is clicked.
|
52 | V10.1.0 | PG70814 | Under the following conditions, the message (<error occurred retrieving value>) is output at the remote debugging time. The NetCOBOL development package for Windows is installed in the client. Server OS is Windows Server 2008 R2. The NetCOBOL development package for Windows (x64) is installed in the server. The server is set for remote development. Debug your application on the server side by using remote debug function of NetCOBOL Studio. The data item is added to the Watch view. Use any of the following methods to perform unconditional execution: The program is executed to the last.
|
53 | V10.1.0 | PG83344 | Under the following conditions, the INSDBINF command terminates abnormally, or the COBOL program that INSDBINF command output is not correctly compiled. Pro*COBOL is used. The character code of COBOL source program is UTF-8. The national character (3byte character) is described in COBOL source program.
|
54 | V10.1.0 | PG90027 | Under the following conditions, when a COBOL project is imported, the following information might not be set. Conditions: After NetCOBOL Studio starts, the dependency view is not opened. And, an existing COBOL project is imported.
|
55 | V10.1.0 | PG92450 | When all of the following conditions are met during execution of a program with a valid OPTIMIZE compile option, there is a move of wrong character (zero) in the leading zero string in the compilation option OPTIMIZE in regards to a numeric edited move with zero suppression. Compilation option OPTIMIZE (*1) is enabled. And, a statement to move to the numeric edited item is described. And, in the 100 lines before the position of the statement described in 2 above, the following are not described. And, in the numeric edited item of 2 above only zero suppression is specified in the edited method (in the string of the PICTURE clause a combination of '9', 'Z', '*' is used).
*1: The default value of the compile option is NOOPTIMIZE. *2: The comment line and the blank line are not counted. Since this is affected by the internal condition of the compiler, there are times when a correct move is performed even after it matches with the occurrence conditions. *3: Points to the statement that explicitly transfers the control to the statement. |
