3.3 PowerCOBOL Development Environment

Information described here applies to the following products.

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

Table 3.3 Program fix list for the PowerCOBOL
No.	V/L(*)	P number	Content
1	V10.1.0	PH01836	Under the following conditions, when the program with tens of thousands of lines, PowerCOBOL might fail in building and terminate abnormally. [Condition] Event procedures are written in PowerCOBOL. And, the number of lines for event procedures is tens of thousands of lines.1 1: The number of lines depends on a way of writing of MOVE statement to access a property, INVOKE statement to call a method, and any other statements. This error might be occur if the number of lines of the .PRC file which is generated when the project built is more than 40 thousand.
2	V10.1.0	PH03380	Under the following conditions, it might be fail in compiling with the following message output. 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=@1@, module-name=@2@, detail-code=@3@, linenumber=@4@) [Condition] The sqlpcob command of Symfoware Server is available in the pre-compiler settings. And, SQL statements are written as event procedures in PowerCOBOL. And, the module is built on each of the following modes. "Debug Mode" is selected. "Release Mode" is selected and, "Use Diagnostic Function" is selected. And, the following letters do not exit after "END-EXEC" statement at the end of SQL statements. Separator Period Separator Space followed by Separator Comma Separator Space followed by Separator Semicolon And, the next line of the "END-EXEC" statement of 4 is a comment line. And, column 12 in the next line of the comment line of 5 is space. And, any statements are written at 13 column or later in the line of 6. And, the same statement with that of 7 is written after the line of 7.1 1: Whether the level of the compile error is U depends on where the event procedures are developed in the COBOL program. If the level of the compile error is not U, object files are generated correctly. However, it might fail in stopping at break point or Step Into execution.
3	V10.1.0	PH03539	Under the following conditions, PowerCOBOL terminates abnormally. [Condition] 1. A COMPUTE statement is written in event procedures. 2. And, a COMPUTE statement is followed by a COBOL reserved word. 3. And, when the project is built or rebuilt in PowerCOBOL.
4	V10.1.0	PH04704	The following issues may be encountered under certain specific conditions while debugging PowerCOBOL programs: A data item cannot be detected by the debugger. Failure to stop at a defined break point or Step Into execution, or, incorrect line positions are reported by the diagnostic function. () : The diagnostic function can be used in V5.0 or later. [Condition] The sqlpcob command of Symfoware Server is available in the pre-compiler settings. And, SQL statements are written as event procedures in PowerCOBOL. And, SQL statements of 2 are written in each of the following way. SQL statements are multiline. Separator letters () do not exit after "END-EXEC" statement at the end of SQL statements, and the next line of SQL statements is a comment. And, the module is built on each of the following modes. "Debug Mode" is selected. "Release Mode" is selected and, "Use Diagnostic Function" is selected. : A space is excluded.

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