The flow of using compiler listings and debugging tools to locate an error is shown below.
Figure 5.6 Flow of debugging using an Object Program Listing
It is recommended that NONUMBER (default value) be made effective when the COBOL source is compiled. The following explanations assume and describe the case where NONUMBER is effectively compiled.
A file relationship diagram is shown below.
Figure 5.7 A file relationship diagram
Note
The data that can be referred when terminating abnormally is data used in the method that programs or terminates abnormally terminate abnormally, and data of caller. The data of the program and the method that doesn't appear to "Call Stack" of WinDbg cannot be referred to.
Data might not be able to be referred to correctly for the program or the method from which OPTIMIZE of the assembler option is effectively translated because no storage of the execution result in the area and the statement might be moved and be deleted by optimization.
Because data might be stored in the register to confirm data, the knowledge of the assembler is necessary. The knowledge of the assembler is debugged and it is possible to debug it by machine instruction by using, and outputting Object Program Listing when translating. Please refer to the section "Object Program Listing" for the form of Object Program Listing.
Inner program is not correctly output to "Call Stack". Please reproduce the same situation by using the debugging function of NetCOBOL Studio when you want to output a correct call relation.
